5 ms·
First congrats, this is hard-work. Second I implore people not to use a language where the designers think breaking changes are OK, while giving no real advanta
by camus2 9y ago
First congrats, this is hard-work. Second I implore people not to use a language where the designers think breaking changes are OK, while giving no real advantage over plain modern Javascript or the use of a linter. Worse, since CS has slighly different semantics than JS it will lead to so much confusion. Coffee Script served its purpose, now let it rest.
- creatonez 9y ago>Second I implore people not to use a language where the designers think breaking changes are OK This is a big deal when you also have to use libraries written in the same language. Python 3 being a fundamentally different language (the underlying bytecode is not backwards compatible) from Python 2 made the transition very difficult. However, this will never be a problem for a javascript transpiler. And also, the list of breaking changes really isn't too incredible. I imagine it'll be fine for most coffeescript projects to take this update quite liberally, as it shouldn't be too hard to write CoffeeScript 1.x/2.x polyglot code to transition to the new version.
- molszanski 9y agoI switched my codebase from 1 to 2 and didn't notice a single syntax issue or a failed test. So not such a big "breaking" change after all.