Re:Why I switched to Spine.js
by theone on Monday May 21, 2012 @11:03AM
(#4003152)
The flexibility which backbone provides is a big thing for me.
Secondly, Choosing "CoffeeScript" is a turnoff me, as it require additional learning curve.
[ Parent
| on HN ]
Re:Why I switched to Spine.js
by ericclemmons on Tuesday May 22, 2012 @01:28AM
(#4006387)
It's a turnoff for me as well, but luckily the Spine.js docs easily toggle between CS and JS.
Re:Why I switched to Spine.js
by lobo_tuerto on Monday May 21, 2012 @08:30PM
(#4005655)
The curve isn't that big, and once you give it a try you won't go back. I never did. ;)
Turn off for me, too. Not to mention, I can imagine debugging being more difficult.
Re:Why I switched to Spine.js
by pooriaazimi on Monday May 21, 2012 @05:26PM
(#4005023)
There's indeed a learning curve, but because 'it's just JavaScript (c)' is CoffeeScript's motto, it doesn't take much. On the other hand, IcedCoffeeScript [1] introduces a fe extremely handy keywords that run afoul of CoffeeScript's motto.
And the debugging is just getting better, and with SourceMap, hopefully will be a non-issue in the very near future.[2]
In the long term, I think it's better to use CoffeeScript as it is a lot more readable and maintainable.
SourceMaps look very promising. I see that Chrome has support for them today. I'll take a closer look when support for CoffeeScript is simple.
http://www.html5rocks.com/en/tutorials/developertools/source...