raincole parent
Thanks god. The days people kept inventing new JS frameworks or even dialects (coffeescript, remember?) every three months couldn't be gone fast enough.
> Thanks god. The days people kept inventing new JS frameworks or even dialects (coffeescript, remember?) every three months couldn't be gone fast enough.
Coffeescript helped Javascript to evolve the right way, so in retrospect, it was absolutely a good thing. It's like people here don't remember the days of ES3 or ES5...
And the days? Remember Typescript right now? Typescript is not Javascript.
One of the guiding principles of typescript is that its semantics should be consistent with ES. This was not the case for coffeescript. I think TS is doing it the right way.
Coffeescript was great though, because at the time Javascript was growing fast but the language was developing slowly or not at all. There was also Atscript for a little while which added annotations because Typescript didn't want to add them; they eventually budged and Atscript was dead. Then there was a fork of Node because Node at the time was still tightly controlled by Joyent, whereas its fork (io.js or js.io or something) was an open governance model. It was eventually merged back into node.
TL;DR sometimes you need to make an alternative to get the original to move.
Shoutout to CoffeeScript!