最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

javascript - Backbone.Marionette vs Backbone-Boilerplate - Stack Overflow

programmeradmin5浏览0评论

I'm new to Backbone and trying to decide how to approach development.

At the moment I'm wondering when people would use backbone.marionette over backbone-boilerplate?

From what I can tell Marionette is a lot more prescriptive, but is this the way that most people approach development here?

I'm new to Backbone and trying to decide how to approach development.

At the moment I'm wondering when people would use backbone.marionette over backbone-boilerplate?

From what I can tell Marionette is a lot more prescriptive, but is this the way that most people approach development here?

Share Improve this question asked May 9, 2012 at 4:54 vdh_antvdh_ant 13.2k13 gold badges68 silver badges87 bronze badges 1
  • I would change this question to Marionette vs LayoutManager or something like that... – HP. Commented Dec 26, 2012 at 7:38
Add a comment  | 

1 Answer 1

Reset to default 24

Marionette automates a lot of housekeeping work with respect to views that I believe Backbone should've included in the first place. Marionette is actively maintained and found it to be extremely useful and flexible for my project.

backbone-boilerplate, from what I see, is more of a way to organize your code into modules but doesn't touch Backbone views.

You should be able to use boilerplate for code organization, and Marionette for more-easily-manageable views. I believe they address complementing issues.

Marionette recently added an AMD version so it is now compatible with RequireJS out of the box.

发布评论

评论列表(0)

  1. 暂无评论