News for hackers. Stuff that matters.
Re:Migrating a large JavaScript project from DOM spaghetti t... by timc3 on Thursday November 15, 2012 @06:20PM (#4791384)
So what do you suggest?
Re:Migrating a large JavaScript project from DOM spaghetti t... by riprock on Thursday November 15, 2012 @09:15PM (#4792076)
I haven't used Backbone.js, but from what I've read there are extensions like Backbone.Marionette for better view and memory management.

https://github.com/marionettejs/backbone.marionette

Re:Migrating a large JavaScript project from DOM spaghetti t... by randall on Thursday November 15, 2012 @09:23PM (#4792095)
As obviously stated in other threads... I've moved to Angular. Their 'digest all the changes and update the dom once' makes a lot of sense... and it has basically inverse opinion from Backbone. (Backbone has lots of opinion about data / saving, while Angular has more opinion about binding and logic.)
Re:Migrating a large JavaScript project from DOM spaghetti t... by lapusta on Friday November 16, 2012 @04:55AM (#4793200)
Backbone is an opinionated software, so it's hard to say if binding would be ever included.

For developers I suggest to try some of plugins, which are listed on GitHub wiki in the binding section and also take a look at Knockout/Ember/Angular so at least you would know what other frameworks offer.

Re:Migrating a large JavaScript project from DOM spaghetti t... by eta_carinae on Thursday November 15, 2012 @09:26PM (#4792106)
Ember.js?