My personal opinion is much as it has been from day one: > I'm not about to start using it for real projects, > it's really just a thought experiment

My personal opinion is much as it has been from day one: > I'm not about to start using it for real projects, > it's really just a thought experiment about how nice > JavaScript could be with an alternative syntax. (Source: https://news.ycombinator.com/item?id=1014225 https://news.ycombinator.com/item?id=1014225) I've used it a bit for fun, but never for work. And I think that the future of JavaScript is probably always going to be JavaScript — until a web language comes along that's so compelling it's just obvious that it will be the right direction, and then the question won't even have to be asked. CoffeeScript, as a concept, was mostly finished back in the 2010-2011 days, as a layer on top of ES3. CoffeeScript 2, while a great step forward in terms of practicality for folks who want to use it with ES6 features like classes and modules — is also a step backwards for the notion of CoffeeScript: For example, we don't have to formalize classes anymore because JavaScript has them now, and unfortunately JavaScript has done them in a very static way that's not at all the direction CS would have taken. Ditto modules. As an open source project, it will continue to work just as well as it always did. But I definitely don't foresee a return to general relevance, ever.