Problem: Javascript has almost no standard library. --> Why is this a problem? What does he mean by standard library? Like, "strings", regexes and hashes? Not n

Problem: Javascript has almost no standard library. --> Why is this a problem? What does he mean by standard library? Like, "strings", regexes and hashes? Not needed. Problem: Javascript won't run outside the browser. --> Fixed. Problem: The DOM is too slow for video games. --> Fixed. Problem: Javascript is single-thread by design. --> Why is this a bad thing? Problem: Javascript is too slow for video games. --> [Citation needed] Problem: Javascript has no packaging or a linker to tie these packages together. --> Linker's not needed, and there are many package managers that work pretty good. Also, since the beginning of javascript you could always <script src=""> whatever you need, pretty cool actually. Problem: Callback Hell. --> This "problem" only bothers bad/lazy/naive coders. Problem: asm.js is basically unwritable by humans. --> Nope, and also, you may not need to write asm.js at all. Problem: Prototypal inheritance is just pants-on-head stupid. --> Clearly a joke to try to use this as an argument. Problem: Web resources need to be minified and zipped for performance. --> Yeaaaaah right, because Javascript == Web. Problem: Machine generated output is more difficult to debug. --> As compared to... another machine generated output from a compiled language? Yeah right... Problem: Async is still a nightmare, huh? --> Same as callback hell. Problem: Balloning project size and complexity. --> [Citation needed] Problem: Javascript still doesn't do everything. --> Is this guy serious? Does he thinks this is a valid argument for anything? Problem: Output runs very slowly on mobile devices. --> [Citation needed] The guy's just a lazy coder. His favorite language would be one where he could just do: "include <what_my_boss_wants>; run();". Good luck waiting for that one.