Earlier quoted context omitted.
> ECMA not Ecma Incorrect: https://ecma-international.org/about-ecma/history/
Cool: my comment is about them spelling it wrong, writing it as "emca".
Should JavaScript be split into two languages?
321–324 of 324 posts
Re: Should JavaScript be split into two languages?
#322Earlier quoted context omitted.
My guess is that none of those bytecode VMs were designed with the explicit goal of running untrusted code at global scale in a rock-solid sandbox. If anything, I expect those existing VMs to slowly be replaced by WebAssembly due to how crucial and complicated that very specific sandbox requirement is - and how useful that is once you have it working reliably. Personally I never want to run untrusted code on any of m…
From the day WebAssembly was announced: https://news.ycombinator.com/item?id=9732827 The Web is an evolving system too large and long-lived for any single company, stable consortium, or standards body capable of doing the deed to do it, so none of Java, Flash (AVM), .NET/CLR, NaCl/PNaCl, Dart, and others I have forgotten about ever had a chance to take over. JS got out first and evolved through several jumps into htt…
https://news.ycombinator.com/item?id=1905155
https://kripken.github.io/talks/2020/universal.html#/ (from Alon Zakai in 2020)
Re: Should JavaScript be split into two languages?
#323Re: Should JavaScript be split into two languages?
#324"ECMA TC39", not "Emca TC39". Also, looks like a bad markup link for TC39. Also note that it's either "co-authored by Mozilla, Apple, Moddable and Sony" or "authored by Guo along with others from Mozilla, Apple, Moddable and Sony", but directly related to that statement, that makes this "not a Google proposal" but clearly an "industry proposal" if it has Mozilla and Apple buy-in. Also, "the proposed solution is not t…