1. There's no evidence (I'm sitting in a TC39 meeting) other than grumping from a few that we are near the point of JS painted into a corner by backward compatibility.
2. WebAssembly is happening. Dynamic language support will take a while. Together these suggest JS evolution will continue. It shall continue. /be On Wed, Jul 26, 2017 at 11:37 AM Florian Bösch <[email protected]> wrote: > On Tue, Jul 25, 2017 at 11:50 PM, Brendan Eich <[email protected]> > wrote: >> >> Core language changes are different in kind from sync touch events. It's >> very hard to plan to remove anything on a practical schedule or >> order-of-work basis. Engine maintainers likely still hate more modes, and >> users should too. New syntax as its own opt-in still wins, although this >> obligates TC39 to work on future-proofing, e.g., : after declarator name in >> declaration for type annotation syntax. >> > > There's a point at which you cannot add anything new meaningful because of > the broken things. And you can't remove the broken things because you're > committed to eternal backwards compatibility. And you can't add modes > because nobody likes them. That's just planned obsolescence. This means JS > is not a living language, or won't be much longer in any case. It's > probably best if whatever you run on the web ships its own interpreter that > runs on whatever flavor runtime (JS, asm.js or Web Assembly) is available. >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
