Hand-written asm.js code is not going to be the norm, for the forseeable future, for a variety of reasons. The rules for the grammar are difficult and tedious to manually write. The fact that everything runs in a massive array, so you've got a lot of memory management to write, is going to be a problem. The existence of numbers like 1384465 and 4980736 is what makes that particularly hard to read. Most asm.js code on the web is going to be incomprehensible; the examples you can read are the exceptions, for didactic purposes, not the rule.
Wow. No, it absolutely is not. I have no idea what you could possibly mean by "not entirely" compiled.
>The rules for the grammar are difficult and tedious to manually write.
There's nothing difficult about the syntax. It's a subset of javascript.
> The fact that everything runs in a massive array, so you've got a lot of memory management to write, is going to be a problem.
No more difficult than managing memory in C.
> The existence of numbers like 1384465 and 4980736 is what makes that particularly hard to read.
The lack of meaning for those numbers is what makes it hard to read. It wouldn't matter if 1384465 were 2 or "a". It's been minified, so the meaning has been stripped away. I agree that it is hard to read, but it's not a result of using asm.js, it's a result of minification and auto-generating code. There's nothing inherently illegible about asm.js.
> Most asm.js code on the web is going to be incomprehensible; the examples you can read are the exceptions, for didactic purposes, not the rule.
Sure, just like most javascript on the web is incomprehensible, by virtue of being minified or auto-generated.
That Gist - what is visible from "View Source" after beautification - is not compiled asm.js code. It is not the result of any compilation. It is the result of minification. Most minified code is as illegible as that.