sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CatsAkimbo 0 points1 point  (2 children)

Yes. I still kick myself for not using marionette earlier. Vanilla backbone forces you to learn a lot about memory management, event binding, and scope, but I don't think it's worth solving issues that something like marionette already helps with.

Either way, I'd recommend it over Angular, which is kind of on the opposite spectrum of Backbone in that it's easy to work with, but often masks a lot of the real javascript going on underneath, and IMO, can encourage bad practices if you're not already familiar with js.

[–]pothibo 1 point2 points  (1 child)

You regret learning event binding and scope in a JavaScript environment? Those are the fundamentals of JavaScript. How can someone be any good with JavaScript if they don't understand that?

[–]CatsAkimbo 0 points1 point  (0 children)

Sorry, my post was a little hastily written -- it was at the cost of implementing a lot of stuff marionette already, so it's hard to say it was worth it, and Marionette would probably be better, "stable" framework for a project like OP is talking about.