Migrating a large JavaScript project from DOM spaghetti to Backbone.js

Re:Migrating a large JavaScript project from DOM spaghetti t... by vidarh on Friday November 16, 2012 @05:59AM (#4793343)

Apples and oranges. They address different areas, and so you'll combine them with different other code to fill in the gaps.

Then can even be used together (see, e.g., knockback.js which combines Knockout data binding with Backbone) to complement each other.

All you're really complaining about seems to be lack of data binding in Backbone. So you pick your preferred data binding mechanism and plug it in.

[ Parent | on HN ]

Re:Migrating a large JavaScript project from DOM spaghetti t... by hasenj on Friday November 16, 2012 @06:44AM (#4793438)

In theory they are different, but in reality people use backbone because they think it will help them reduce the bloat and mess in their code, when in fact backbone will not help with that.

[ Parent | on HN ]

Re:Migrating a large JavaScript project from DOM spaghetti t... by vidarh on Friday November 16, 2012 @06:52AM (#4793466)

Really? My experience is that it does. So is the experience of many others. Data binding was far down the list of issues I've needed to fix in the places where I've experimented with Backbone.

For data binding there's tons of alternatives that co-exists nicely with Backbone, including Knockout via Knockback, or Rivets, or any number of modules written specifically to work with Backbone - the choice of data-binding mechanism is orthogonal to the choice of using Backbone or not.

[ Parent | on HN ]

Re:Migrating a large JavaScript project from DOM spaghetti t... by colin_jack on Friday November 23, 2012 @11:47AM (#4822780)

Would be interested to hear more about what you mean here?

[ Parent | on HN ]