>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

>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.