&gt; we should [...]<p>No, again, you&#x27;re reforming &quot;I would like...&quot; into &quot;we should&quot;. There&#x27;s no <i>should</i> about it.<p>JavaScript is nowadays quite a nice language. ES2015 and the way forward gives us a language that could happily go for another 20 years with few issues.<p>WebAssembly doesn&#x27;t solve the problem btw - most of the things people hate on JS about (that aren&#x27;t just dumb &quot;I don&#x27;t like loose typing or understand prototypical inheritance&quot; complaints anyhow) are to do with how it integrates with the key web feature: <i>the DOM</i>.<p>DOM is where everything goes to hell on the web and it&#x27;s going to be just as much of a mess in C&#x2F;Rust&#x2F;Haskell&#x2F;Clojure&#x2F;brainfuck as it is in JavaScript.<p>Also your comment about Babel is just strange. The reason to use Babel is to support older parsers that only understand ES5 syntax. That&#x27;s never going to go away. We&#x27;ll be dealing with older parsers for 10 years after WebAssembly launches - so guess what? Now your toolchain got longer, more complex, and you <i>still have to output JavaScript anyhow</i>.<p>Yaaaaaay.<p>Or, you know, you could learn JavaScript properly and realize that it&#x27;s a completely useful and great language that is just as good as whatever your pet favorite is when applied to the tasks at hand.