We all know how this story ended last time. And yet, here we are watching it all over again and most of us are powerless to do much about it. For all the superficial openness of the modern Web, the reality is that it is now utterly controlled by a small group of browser developers, a small group of centralised content hosts, and a small group of curators, several of which overlap with each other but almost none of which have goals that necessarily align with those of either the average web surfer or the average small content producer.
If the group is small, it's mainly because the job is very difficult. All browsers are a big mess and it takes time to be productive.
The idea of asm.js is one of Alon Zakai. He explains on his blog all the experiments he made before concluding with that.
A quote from the oldest post I know about emscripten:
"I want the speed of native code on the web - because I want to run things like game engines there - but I don't want Java, or NaCl, or some plugin. I want to use standard, platform-agnostic web technologies."
http://mozakai.blogspot.fr/2010/07/experiments-with-static-j...
Maybe Servo?
The more comprehensible browser codebase I know is Dillo.
I liked a lot Java Applets. It was fantastic to be able to draw pixels or use a toolkit in a web browser at that time.
I gave up Java near after the dispute between Sun and Microsoft about J++. Java was far less interesting for me without that feature.
It didn't get much traction because nobody really wants to program in Java on the client if there are alternatives.
Java is not the best (though it's better than JavaScript, and android contradicts your claim), but JVM bytecode as a target is great.
WebAssembly will have several actual competing implementations, not to mention that it's a drastically smaller addition to the existing Web platform.