Linked by Thom Holwerda on Wed 9th Feb 2011 23:29 UTC
Hardware, Embedded Systems And, of course, just as I decide to leave the live blogging to play a game of Left 4 Dead 2, HP drops the big bombshell right at the end of their press event: webOS is coming to PCs!
Thread beginning with comment 461839
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Laurence
by twitterfire on Thu 10th Feb 2011 18:42 UTC in reply to "Comment by Laurence"
twitterfire
Member since:
2008-09-11

Not to mention the fact that JS (compiled or not) will never out perform Objective C / .NET


Android apps are Java based, not JS (javascript) based.

Java apps are compiled, not interpreted. The loss of speed is from JVM - the virtual machine which runs the interpreted code. .NET is also compiled and runs also in a virtual machine.

Speed wise, I saw C and C++ apps running faster than Objective C.

Reply Parent Score: 2

RE[2]: Comment by Laurence
by konrad on Thu 10th Feb 2011 19:43 in reply to "RE: Comment by Laurence"
konrad Member since:
2006-01-06

Speed wise, I saw C and C++ apps running faster than Objective C.


That could be because of Obj-C Message Dispatcher.

Edited 2011-02-10 19:45 UTC

Reply Parent Score: 1

RE[2]: Comment by Laurence
by Laurence on Thu 10th Feb 2011 22:46 in reply to "RE: Comment by Laurence"
Laurence Member since:
2007-03-26

"Not to mention the fact that JS (compiled or not) will never out perform Objective C / .NET


Android apps are Java based, not JS (javascript) based.
"
I know but Android has f--k all to do with this thread. However WebOS (which is the platform we're discussing) /DOES/ use JS.

Java apps are compiled, not interpreted.

Actually they're both. They're compiled to byte code that then gets interpreted by the Java Virtual Machine

.NET is also compiled and runs also in a virtual machine.

Yes, .NET is also byte code. Thanks for pointing out something we all ready knew.

Speed wise, I saw C and C++ apps running faster than Objective C.

That would be down to shoddy programming then as your point is as nonsensical as arguing that C apps run faster than C++.

Edited 2011-02-10 22:48 UTC

Reply Parent Score: 2

RE[3]: Comment by Laurence
by Valhalla on Fri 11th Feb 2011 06:03 in reply to "RE[2]: Comment by Laurence"
Valhalla Member since:
2006-01-24

However WebOS (which is the platform we're discussing) /DOES/ use JS.

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'.

That would be down to shoddy programming then as your point is as nonsensical as arguing that C apps run faster than C++.

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.

Reply Parent Score: 3