Linked by Kroc Camen on Fri 2nd Apr 2010 14:01 UTC
Web 2.0 In November last year I stated that it would only be a matter of time before it happened. Also in November Joel Webber, a Google engineer had the inspiration to port Quake II to HTML5 from Jake2--a Java port of Quake II--using Google Web Toolkit; the same toolkit used for writing Google Mail | Maps | Wave in Java and compiling into JavaScript. With the help of two other Google engineers (Ray Cromwell and Stefan Haustein) in "20% time", it works! Just!
Permalink for comment 416732
To read all comments associated with this story, please click here.
RE: This is a no go
by raboof on Fri 2nd Apr 2010 23:01 UTC in reply to "This is a no go "
Member since:

Any kid who even doesn't finished the most elementary IT class yet, knows that javascript is a interpreted language ans as such, it sucks badly in terms of performance. (...) There are far better technologies such as java and silverlight.

Of course natively compiled code is much faster compared to interpreted code. However, Java and Silverlight don't contain natively compiled code either: their 'binaries' consist of bytecode that has to be run by a Virtual Machine, too.

Compiling source to bytecode beforehand might give Java and Silverlight a bit of a head-start, but after that the interpretation/JIT-compilation techniques are not all that different.

A difference is JavaScript is much more 'dynamic' than the typed Java/Silverlight code - the VM can leverage the typing information to perform optimalizations on Java/Silverlight, this is much harder with JavaScript

Reply Parent Score: 2