HNHacker News
TopNewBestAskShowJobs

dflat

19 karma · joined May 18, 2018

submissionscomments
dflat··on What Does “One JS” Mean in a World of Transpilers?
The yearly ES release cadence seems to be adding sugar for its own sake. This stuff hasn't been battle tested in the field long enough. Look at how many times class field and decorator proposals have changed over the years.

JSX by comparison seems much more stable than the class and decorator proposals, although arguably its features are much better optimized by a transpiler rather than a native JS engine.

dflat··on What Does “One JS” Mean in a World of Transpilers?
The ECMAScript stage 3 proposals related to decorators and class private and static fields need a lot more time to bake - maybe a few years. The whole # or -> thing seems fundamentally wrong. The standards process needs to slow down until better ideas emerge from the JS community and the Babel ecosystem.

I do like the idea presented of having a transpiler track and a JS engine track. Keep the ES spec for the JS engines simpler and hoist all the syntactical sugar onto the transpilers.