Had a quick look through, looks interesting.
Some thoughts<p>* Only 32-bit address space (although they do say "Future version of WebAssembly might provide memory instructions with 64 bit address ranges")<p>* Webassembly is pretty low level. Just 4 basic types (integers, floats). No C-style structures even. This is lower level than e.g. LLVM IR, and lower level than the Java VM.<p>* No garbage collection support.<p>I hope Webassembly can be used from not just Javascript, but something like C++, directly.
The asp.net team is already hard at work on the Blazor project a web UI framework using C#/Razor and HTML.
<a href="https://github.com/aspnet/Blazor" rel="nofollow">https://github.com/aspnet/Blazor</a>
I really love the idea of WebAssembly but am super intimidated by it. Being a junior frontend dev it seems like a really powerful piece of tech that could go in a million directions in the future.<p>My big hangup is understanding a low level use case for it. I've console.logged in wasm but only knowing javascript I don't know where to go from here. Is the idea that you can utilize packages in any language then rebuild it in js?
I hope this is the future of the web.<p>If the DOM gets accessible from wasm, we'll finally be able to avoid using javascript entirely.<p>It's crazy how much time and effort are necessary to finally be able to make a piece of software work on any computer, without having to make different high level graphical API work together.<p>The cherry on top would be to have both the dom AND websockets.
Is anyone else afraid that this will enable a "Tower of Babel" effect where the coming sheer profusion of languages will fragment web programming into dozens of competing, mutually-incomprehensible linguistic camps.<p>Javascript sucks, but at least it's the web's lingua franca.