[speg]

Is WebAssembly going to solve anything though? Most of what I've read about it is that it will be an accessory to JavaScript. Things like databases, video encoding, 3D rendering, etc.. Will we really be interfacing with the DOM APIs in C?

Even if that is how it plays out, we'll still have a dozen frameworks to decided between, at least one for every language that targets WebAssembly.

[sargas]

Agreed. WebAssembly won't make the JS framework landspace stop from changing. But it maybe he meant to say that with WebAssembly, other languages will be able to be used in the browser, so maybe JS will see less rapid changes.

[sedeki]

As I understand it, we'll have access to the DOM and the various APIs (WebWorkers, etc)...

Of course we won't write apps in some very low level language. But I am guessing that the consensus will converge pretty fast on what (small number of) alternatives we'll use, since we are doing it right this time (I'm hinting at JS).

No, JS won't die. We have fast interpreters now, we can run it on our servers and there is a bunch of people who like it a lot.

Also, there is the issue of backwards compatability.

[vectorpush]

Yeah. I suspect we'll see things get even more complex as an explosion of old and new languages begin to target wasm, but at the same time we'll probably get better solutions since we won't need to rely on transpilers and hacks to work around the limitations of JavaScript as a language.