Re:Why I switched to Spine.js
by ericclemmons on Monday May 21, 2012 @11:06AM
(#4003177)
I'm glad you did the teardown because, despite the amount of people who are using any one of the MV* frameworks, few are authoritative on the differences/subtleties between.
Spine's "features", to a novice, are indistinguishable to Backbone's, which is probably what prompted the author's post.
In the world of Javascript frameworks, devs seem to pick a side based on the following:
1. Naming convention (Mootools' getStyle()+setStyle() vs. jQuery's css(), Router vs. Controller, etc.), which is admittedly personal preference.
Re:Why I switched to Spine.js
by fiznool on Tuesday May 22, 2012 @08:57AM
(#4007553)
You forgot:
4. Framework / Library size. I'm turned off by many JS MV* Libraries due to their larger size. Backbone is very small and lightweight - perfect for mobile web apps.
Spine's "features", to a novice, are indistinguishable to Backbone's, which is probably what prompted the author's post.
In the world of Javascript frameworks, devs seem to pick a side based on the following:
1. Naming convention (Mootools' getStyle()+setStyle() vs. jQuery's css(), Router vs. Controller, etc.), which is admittedly personal preference.
2. Lowest barrier-to-entry (Spine.app, TodoMVC example)
3. Debugging (see: compiled Coffeescript lineno debate, compiled SCSS/LESS debate)