Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Permalink for comment 553920
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-11-29
It depends a lot on what you're doing, for applications with a heavy computational factor it most certainly won't (though matching Java/C# is not impossible in JavaScript). For applications leveraging the runtime more it can be every bit as fast as a native application from the user perspective.
You just don't know enough about the executing code to do meaningful code optimization, and are running under time constraints as the code gen is happening in real time. This is in contrast to the case with C#, especially as moondevil mentioned, where compilation is done offload and gratuitous optimizations can be applied.
It is improving and some of the latest optimization frameworks being introduced @Mozilla are specifically geared towards actual web apps rather than regular web pages (the IonMonkey JIT for example).
Mozilla being on its Nth JavaScript engine doesn't really impress me as much as it once did.