Here's a good post about why Javascript is not performant and probably won't be for a very long time. http://sealedabstract.com/rants/why-mobile-web-apps-are-sl

Here's a good post about why Javascript is not performant and probably won't be for a very long time. http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ http://sealedabstract.com/rants/why-mobile-web-apps-are-slow... The reason this matters is that we are inherently limiting ourselves to JavaScript's characteristics. We definitionally cannot get better than JavaScript since it is our standard. If we could get all the player involved to agree to a new Bytecode standard, we could get better performance, and better standards. We might not have to even use a new standard. JVM's bytecode could work. .NET even. Sure, as time goes by, byte code would need improvement. It would need additions or corrections. This is just the fact of a human world. To say we shouldn't do something else because of the fact that change exists, again, limits us. Look at what we've got with real bytecode targets. Scala, Clojure, F#, C# and VB.NET to name but a few. They each target a specific family, and they perform well. As a result of targeting a more robust bytecode, they out perform JavaScript. While I agree that we shouldn't throw out JavaScript anytime soon, I would like to see a more efficient interchange and structure for web projects. The Web and its browsers appear to be the future. Let's try to do better than a hacked language made 25 years ago by a defunct company.