8 ms·
This just reminds me of "Make the Leap from Javascript to Coffeescript" Remember where that got us? This stuff is all really cool and fun to work on, but inst
by automathematics 7y ago
This just reminds me of "Make the Leap from Javascript to Coffeescript"
Remember where that got us?
This stuff is all really cool and fun to work on, but instead maybe we should focus on changing the JS standard for the better since we always end up working in it anyways!
https://js.foundation/ https://js.foundation/
- phailhaus 7y agoYes, it got us ES6! Languages don't exist in a vacuum. They introduce new ideas, dispense with others, and all languages can learn from what works in the field and what doesn't. If you're working on a personal project, it might be a good idea to try out PureScript and learn from what it has to teach!
- automathematics 7y agoYay new ECMA standards! Classes/decorators/scope/arrow functions have made my life SO MUCH BETTER the last 5 years
- ARandomerDude 7y agoWhy not both? CoffeeScript was awesome at the time, and ahead of its time. JavaScript owes many of its new niceties to CoffeeScript. Yes, please, let's advance the state of JS. And let's push the boundaries with other languages that don't have the backwards-compatibility constraints and corporate sluggishness that JavaScript does. Then take the best features and merge them into JS.
- automathematics 7y agoYeah it was awesome! But then years later most projects are wasting engineering time to convert their whole code base which is a bummer! That's all I'm saying.
- bcheung 7y agoThe JS community is adopting more and more concepts but a lot of it has to do with the syntax. If the syntax is too verbose people just won't use it. FP is much easier when working with a language based off the lambda calculus (Haskell, Elm, PureScript, etc). Currying, partial application, and point-free composition is overly verbose in JS. JS has adopted the concepts but they are not used very often because of the messy and noisy syntax.