By design of the first MVP iteration.
http://webassembly.org/roadmap/ and http://webassembly.org/docs/future-features/
GC (which is the main major feature required for JavaScript) is in progress, https://github.com/WebAssembly/design/issues/1079
So, your article is FUD in it's purest undistilled form.
As I mentioned in another conversation, if you feel you can contribute to Wasm and make it solve the problems we are solving here, this is great, by all means, please do so.
In the meantime, we are going to continue trying to solve some of the performance problems of the web using the techniques discussed in the blog entry because we are convinced that they are going to work better.
Are you saying this comment is false?
> I am not aware of any project that achieves compilation of JavaScript to wasm
I.e., Javascript to WASM is on the roadmap and something we can use in the next few years? Or am I misunderstanding the situation?
The article is just reiterating an argument that Mozilla and Facebook made. If you’re saying Mozilla and Facebook are spreading Fear Uncertainty and Doubt with their proposal for a binary JS AST, then you may do so, but please realize that they probably had good reasons to start such a project.
EDIT: Even though I disagree with the parent, it is making some good points (specifically, that WebASM is going to add a GC), so flagging it to death doesn’t seem to be the right thing to do.
I'd like to see why it is good, given efforts with WebAsembly