Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Permalink for comment 553979
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 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
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
More Features »
Sponsored Links



Member since:
2005-11-29
Its a neat trick, but how far will it get you? How long before you run out of obvious optimizations? How long before you run into the brick wall that is the language itself?
It just doesn't make sense. JS will always be worse off because it performs a lot at run time, that is done at compile time (with much more diligence) in other languages.
There simply isn't a comparison between the performance of a JS JIT compiler and what a good optimizing compiler or even C#'s JIT can do.
It is true that JS has geniuses working behind it (esp. the V8 team) but JS as it stands now isn't ready, and I'm not sure it'll ever even become good enough.