Linked by Thom Holwerda on Wed 9th Feb 2011 23:29 UTC
Permalink for comment 461897
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-24
Yes, worth to note however is that Google uses a JIT-compiler for Javascript rather than interpreting. The JIT-Compiler they bought (V8) is very fast and unlike most other JIT-compilers it converts directly to machine code instead of the traditional bytecode, which means they don't need a 'virtual machine' but instead runs native code.
With both the code generator and the GC being state of the art I can see why Google bought V8. As for performance relative to Java or C#, obviously Java and C# being statically typed gives them an advantage but it would still be interesting to see just how much of a difference there really is.
Given that people write quite advanced games in purely interpreted languages like Python and Lua, there's no reason that JIT-compiled Javascript won't be able to perform well for many tasks given that the really heavy lifting will be done by the underlying system using native code and hardware acceleration, with Javascript merely handling the program 'logic'.
Indeed, there's nothing inherit in ObjectiveC that would make it's performance lesser than that of C or C++, this would be a question of the code quality generated by the compiler.