Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Permalink for comment 553982
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 David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Linked by Thom Holwerda on 04/14/13 18:22 UTC, submitted by MOS6510
More Features »
Sponsored Links



Member since:
2007-09-22
Javascript is now about twice as slow as C in most cases. Where other scripting languages like Perl are more than a 100-times slower than C.
Where something like Java might be 1.3 or in certain cases faster than C (a JIT compiler can optimise stuff at runtime which normally a C-compiler would not build that into the compiled binary).
Javascript is basically the fastest scripting language right now. Faster than Lua for example, but Lua can still be faster because it is easier to exchange data with existing C-code. Lua is also a lot more memory efficient.
So yes, Javascript never was the best choice, but when did you ever see the best technology win ? Take VHS Betamax as an example. The "problem" is, Javascript is widespread and "good enough".
Also supposedly FirefoxOS uses less memory than Android because there are a whole lot less layers involved. So FirefoxOS might actually win from Android "native" apps on a lot of devices.
I read somewhere a few years ago that in servers memory usage as much power as the CPU. CPU's have become much more efficient. So that would mean Javascript could have similar power demands than Android/Java.