3 ms·
Great write-up. As far as backbone goes, we've had success using marionette.js to standardize the way we write front-end components and implement common types
by capkutay 12y ago
Great write-up.
As far as backbone goes, we've had success using marionette.js to standardize the way we write front-end components and implement common types of view patterns. Curious to see if anyone else has found it to be useful.
- zdavis1645 12y agoWe've had the same experience. It adds just enough convention on top of Backbone to prevent your application from turning into a ball of mud, while at the same time remaining small enough where you can hold the whole framework (Backbone + Marionette) in your head. I find Backbone + Marionette much simpler, and much easier to reason about than Angular, but keeping it this way still requires developer discipline. Avoid hacks, avoid event soup (which Marionette maybe makes a bit too easy), and follow general object oriented design patterns, and it's not that hard to build a maintainable, scalable Backbone/Marionette app.
- nevalau 12y agoWe are also using backbone + marionette combo successfully and still very happy to do so.
- kalms 12y agoSame thing here. We're a pretty large agency, and it powers all of our SPA's and hybrid apps; even with a normal request based approach, Backbone/Marionette handles all UI beyond routing and initial render. It's a definite boon to our development proces, and it has made our solutions easier to maintain. Can't ever see us go back from this approach.
- techpeace 12y agoWe've had great success with Marionette, specifically by leveraging concepts from the http://backbonerails.com http://backbonerails.com architecture.