3 ms·
Does this help the JS engines? Instead of _knowing_ the developers intent and optimizing for it, it has to infer what the transpiler outputted and optimize for
by dested 8y ago
Does this help the JS engines? Instead of _knowing_ the developers intent and optimizing for it, it has to infer what the transpiler outputted and optimize for that. One seems harder than the other.
- dflat 8y agoThe 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.
- scottmf 8y agoReasonML has JSX. It just translates to function calls which do whatever you want. It’ll probably never happen but it’d be cool to see native JSX in JS.
- cpeterso 8y ago> This stuff hasn't been battle tested in the field long enough. There is a circular dependency: TC39 wants new language changes to be prototyped and proven in compiled-to-JS languages but the transpiler developers don't want to implement language changes that are not already on the standards track.