JS is changing, ES6 is coming. Browser vendors want changes and are on board. They're also under competitive pressure. But in what scenario is the much greater

JS is changing, ES6 is coming. Browser vendors want changes and are on board. They're also under competitive pressure. But in what scenario is the much greater work to add Pepper and PNaCl support going to prevail? You have to assume JS dies or freezes, and there's exogenous pressure for something new. Instead, we see demand for JS to evolve (Mozilla serves this, we aren't just ginning it up, believe me!). So browser vendors would have to do two big jobs: tend the web standards and evolve them, and put in a new native code runtime alongside. That is simply not going to happen outside of Google, which can afford endless impossible-to-standardize boondoggles. It is both uneconomic, and technically inferior to a more minimal evolutionary path-finding solution. /be