Re:The cost of transpiling ES2015 in 2016
by endemic on Monday February 08, 2016 @01:00PM
(#11059700)
I've started going back to straight ES5 for my side projects. It removes the annoying "compile" step, which I find pretty dumb for an interpreted language. For deployment, of course, I concat and minify. But the speed with which I can iterate using vanilla Javascript is refreshing in this day and age.
[ Parent
| on HN ]
Re:The cost of transpiling ES2015 in 2016
by mbrock on Monday February 08, 2016 @01:15PM
(#11059809)
I would be interested in a compilation step if it gives me something like PureScript, that is, real, serious benefits from the compiler: algebraic data types, type checking, type classes, and so on.
But ES2015 is just a bunch of syntax sugar. Nice syntax sugar, but still. Okay, async/await is significantly useful... but you still have to understand how the promises work under the hood... and I can live with raw promise coding.