Marionette.js compared to Chaplin.js

Question

I am currently considering a large single-page web application. There will be many components, so the separation of concerns is important to me. A server is basically a REST server with some sugar, for example, sending a code template to a client.

So I need to decide which MVC Framework I want to use on the client side.

I really like backbone.js, so I want to have a great platform that relies on it.

What I came across Marionette.js and Chaplin.js.

Has anyone used one or both structures and can tell a little about them? Strengths, weaknesses, the community behind him or are they basically the same?

It should not be a discussion of which is better, just a short list of functions, so I can decide which one to use, because I do not have time to really get started with both.

Answer 1

Did not work with Marionette, but mostly Chaplin is a wise decision when:

• You need a more stubborn architecture. Useful if you need a set of rules / conventions to stand up and work in a team.
• Memory management is a problem.
• Perhaps you come from a Ruby background and feel more comfortable with Coffeescript.

In addition, if you are creating a large application, in Chaplin get ready to portray a lot of things yourself. The documentation is there , but often you find yourself "alone in the dark." The source is well commented, although it is appreciated.

Answer 2

I have experience with Marionette.js for about 1 year. Marionette.js is the best option when you have your own architecture, but you don’t know how to work with the level of views. I like the following scheme:

• The backbone network as the core for the data layer (models, collection, rest api)
• Marionette.js for the presentation level (ItemView for one object, CollectionView for a collection of objects, CompositeView (entity + collection), etc.
• data binding Reveal.js
• HBS as patterns
• Your own routing and core logic

I recommended you a brunch tool - it is a rich tool for compiling, preparing and creating your own SPA. Of course, you should see Grunt + Yo + Bower another rich tool.