3 ms·

That's interesting the author brought up marionette[0]. Marionette nudges developers to make all their views modular, reusable components. Also, instead of havi

That's interesting the author brought up marionette[0]. Marionette nudges developers to make all their views modular, reusable components. Also, instead of having a vanilla dispatcher object, they've added some more inter-app communication protocols[1]. I've had a decent experience so far. Has anyone else used marionette? 0: http://marionettejs.com/ http://marionettejs.com/ 1: http://marionettejs.com/docs/marionette.application.html#the-application-channel http://marionettejs.com/docs/marionette.application.html#the...

ben336 12y ago
I've really enjoyed Marionette as a more (but still not very) opinionated approach to Backbone development. You mentioned the messenger protocols, definitely checkout Backbone.Radio [1], it's being created to replace Wreqr, the current event implementation and has a much cleaner API. The plans seem to be to bundle it with Marionette 3.0 when it gets there, but its usable with the current version. [1]: https://github.com/marionettejs/backbone.radio https://github.com/marionettejs/backbone.radio
- thejameskyle 12y ago
  Backbone.Radio is awesome (Bias Disclaimer: I helped write it with James Smith). It's definitely going to replace Wreqr in Marionette 3.0, and we'll be integrating with it much more. There is also a lot of other cool things coming in 3.0. We're very focused on the architectural pieces and theres some really great ideas there. See: https://github.com/marionettejs/backbone.marionette/issues/1796 https://github.com/marionettejs/backbone.marionette/issues/1...
wuliwong 12y ago
We use Marionette in production at work. I enjoy it. I've supported existing Marionette applications and have also built a pretty complex calendar app using Marionette from scratch. Marionette seems to match up with my "intuition" as to how things should work. The ability to effortless swap modules and views in and out of regions is great. I'm not sure if that is hardwired into other Javascript MVC libraries and frameworks but if it isn't, I doubt I would like them. I've had some other experience, I built a beta site for a startup using regular Backbone. I've also built a pretty complex site using Batman.js but it never got to see the light of day. Other than that, I've just toyed with Angular and Ember.
andyl 12y ago
We've used marionette - wanted to like it but found the learning curve too difficult. Switched to React - much simpler learning curve with good performance.
- thejameskyle 12y ago
  Hi, Marionette core member here. I'd be interested in hearing about any trouble you've had while working with Marionette. Side note: We're really rapidly re-writing our documentation right now (yay alliteration) so people can expect to see a lot of big improvements there.
  - capkutay 12y ago
    Hey quick request! You guys have one heavily-referenced example for your CompositeView. However, I believe some of the things in that tutorial are since deprecated (such as appendHtml): http://lostechies.com/derickbailey/2012/04/05/composite-views-tree-structures-tables-and-more/ http://lostechies.com/derickbailey/2012/04/05/composite-view... The current documentation on composite view actually references that article. Other than that, great work!
mtrpcic 12y ago
We use Marionette at work (and at my previous job as well), and I've got to say, I really like it. I've been a fan of Backbone for a long time, and Marionette just added a few more components to make it a lot more powerful. The app event system is easy to use, regions make view rendering and event delegation super easy, and the built-in support for collection views is great.
findjashua 12y ago
At work, we're moving from Backbone to Marionette. While it does make some really good choices from design/architecture standpoint (modules, messaging via radio), you still have to deal with the most painful part of building user interfaces - updating views on model updates. I'd recommend using it with a data-binding library if possible.
johnthedebs 12y ago
I spent the time to learn Marionette, and while it improved my Backbone code enormously, I found there was a pretty steep learning curve to using it correctly. And even so, I found doing certain things was often overly difficult or confusing. Recently, I switched a small project from Backbone/Marionette to React and I haven't looked back. The learning curve for React is tiny compared to Backbone/Marionette, and it is so much easier to 1. reason about and 2. recompose. Not to mention much better performance! It's clearly still maturing, but to me React feels like a big leap ahead of Backbone/Marionette.
jonkho 12y ago
I also think Marionette is awesome and enforces modularity. The author mentions, "View A handling events from View B and vice-versa" which makes me think that he's may not be following the adage of "signal up/invoke down"; He may be just wiring up listeners in an adhoc manner and not establishing clear ancestor/child relationships with his views.

ben336 12y ago

I've really enjoyed Marionette as a more (but still not very) opinionated approach to Backbone development. You mentioned the messenger protocols, definitely checkout Backbone.Radio [1], it's being created to replace Wreqr, the current event implementation and has a much cleaner API. The plans seem to be to bundle it with Marionette 3.0 when it gets there, but its usable with the current version. [1]: https://github.com/marionettejs/backbone.radio https://github.com/marionettejs/backbone.radio

thejameskyle 12y ago
Backbone.Radio is awesome (Bias Disclaimer: I helped write it with James Smith). It's definitely going to replace Wreqr in Marionette 3.0, and we'll be integrating with it much more. There is also a lot of other cool things coming in 3.0. We're very focused on the architectural pieces and theres some really great ideas there. See: https://github.com/marionettejs/backbone.marionette/issues/1796 https://github.com/marionettejs/backbone.marionette/issues/1...

wuliwong 12y ago

We use Marionette in production at work. I enjoy it. I've supported existing Marionette applications and have also built a pretty complex calendar app using Marionette from scratch. Marionette seems to match up with my "intuition" as to how things should work. The ability to effortless swap modules and views in and out of regions is great. I'm not sure if that is hardwired into other Javascript MVC libraries and frameworks but if it isn't, I doubt I would like them. I've had some other experience, I built a beta site for a startup using regular Backbone. I've also built a pretty complex site using Batman.js but it never got to see the light of day. Other than that, I've just toyed with Angular and Ember.

andyl 12y ago

We've used marionette - wanted to like it but found the learning curve too difficult. Switched to React - much simpler learning curve with good performance.

thejameskyle 12y ago
Hi, Marionette core member here. I'd be interested in hearing about any trouble you've had while working with Marionette. Side note: We're really rapidly re-writing our documentation right now (yay alliteration) so people can expect to see a lot of big improvements there.
- capkutay 12y ago
  Hey quick request! You guys have one heavily-referenced example for your CompositeView. However, I believe some of the things in that tutorial are since deprecated (such as appendHtml): http://lostechies.com/derickbailey/2012/04/05/composite-views-tree-structures-tables-and-more/ http://lostechies.com/derickbailey/2012/04/05/composite-view... The current documentation on composite view actually references that article. Other than that, great work!

mtrpcic 12y ago

We use Marionette at work (and at my previous job as well), and I've got to say, I really like it. I've been a fan of Backbone for a long time, and Marionette just added a few more components to make it a lot more powerful. The app event system is easy to use, regions make view rendering and event delegation super easy, and the built-in support for collection views is great.

findjashua 12y ago

At work, we're moving from Backbone to Marionette. While it does make some really good choices from design/architecture standpoint (modules, messaging via radio), you still have to deal with the most painful part of building user interfaces - updating views on model updates. I'd recommend using it with a data-binding library if possible.

johnthedebs 12y ago

I spent the time to learn Marionette, and while it improved my Backbone code enormously, I found there was a pretty steep learning curve to using it correctly. And even so, I found doing certain things was often overly difficult or confusing. Recently, I switched a small project from Backbone/Marionette to React and I haven't looked back. The learning curve for React is tiny compared to Backbone/Marionette, and it is so much easier to 1. reason about and 2. recompose. Not to mention much better performance! It's clearly still maturing, but to me React feels like a big leap ahead of Backbone/Marionette.

jonkho 12y ago

I also think Marionette is awesome and enforces modularity. The author mentions, "View A handling events from View B and vice-versa" which makes me think that he's may not be following the adage of "signal up/invoke down"; He may be just wiring up listeners in an adhoc manner and not establishing clear ancestor/child relationships with his views.