5 ms·
Same, the JS cool-kids swore up-and-down that CoffeeScript was the future and we'd be fools to not jump on. It's another reminder that no-one knows the future.
by s_kilk 9y ago
Same, the JS cool-kids swore up-and-down that CoffeeScript was the future and we'd be fools to not jump on.
It's another reminder that no-one knows the future.
- treehau5 9y agoCoffeeScript always felt forced onto me during the height of 37Signal's influence of software development trends at the time. At the only rails shop I ever worked at it was heavily resisted. It was at the same time I was reading more and more of Resig blogs and books (Secrets of the JavaScript ninja) and I really began to learn and grok just plain normal JavaScript. I said to myself, "you know, this really isn't that bad" Haven't looked back since. I hate the direction ES is going.
- mercer 9y agoWhat do you dislike about ES' direction? The increase in language features in general, or more specific things?
- treehau5 9y agoIncrease in features yes and the continual succumbing to developers who just can't seem to think outside the strict OO paradigm. Prototypical inheritance is really not that hard to understand. I would rather see JavaScript fix the existing functionality, such as sometimes the prototype chain not being correctly established when instantiating a new object.
- draw_down 9y agoMmm, from my view it was driven more by Rubyists who disliked that JS was much uglier than their chosen language. JS devs just write JS, because they know it already.
- alanh 9y agoIt was the future… so many CoffeeScript niceties (spread operators, destructured assignment, class syntax, ARROW FUNCTIONS) were subsequently mainlined into ES6.