>"If JavaScript is already "fast", then why the need for something like this "to get better performance today"? This feels obtuse -- obviously JS today is fast

>"If JavaScript is already "fast", then why the need for something like this "to get better performance today"? This feels obtuse -- obviously JS today is faster than it's ever been, but we want native c performance out of it. Do you have a in-browser VM solution today that can do complex, GPU-powered full 3D on every platform? Then your VM solution is already inferior to javascript and will need significant time, money and development to even catch up to javascripts current level of "fast". (Using, of course, "game" performance as a benchmark for the vague term "fast") >"The market is speaking, and it's saying that JavaScript needs to go. What? How do you rationalize this? Every major browser supports it to their core and most are working on dramatic imporvements for their implementations. Every mobile device supports it natively. Every computer I've seen in the past decade supports it. The market is speaking? Where? Where is the market speaking? What devices are without javascript? What browsers don't support javascript? I think you are confusing the "market" for "a small subset of a-typical vocal developers".