News for hackers. Stuff that matters.
Re: Why are we limited to JS in browsers - would a bytecode ... by pcarmichael on Thursday November 11, 2010 @09:55AM (#1893968)
One difference is in compiler optimizations. For a given language, compilers can often make inferences based on the code and the semantics of the language, allowing for very targeted optimizations. If you go from LanguageFoo -> Javascript -> bytecode, then you may be limiting the range of optimizations possible (because Javascript may not be able to infer the same things about the code, be it because of program structure, language semantics, etc.)
Re: Why are we limited to JS in browsers - would a bytecode ... by m0th87 on Thursday November 11, 2010 @10:17AM (#1894033)
The same holds true with bytecodes. e.g. TCO on the JVM: http://stackoverflow.com/questions/105834/does-the-jvm-preve...
Re: Why are we limited to JS in browsers - would a bytecode ... by robhu on Thursday November 11, 2010 @11:38AM (#1894264)
Why not make the 'byte code' the LLVM IF ? That way you leverage all the stuff from the LLVM project for making it go fast.

The main thing to do then is just to have a front end for your favourite language the outputs LLVM IF.

Re: Why are we limited to JS in browsers - would a bytecode ... by wmf on Thursday November 11, 2010 @01:49PM (#1894757)
Google's working on that: http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf

(Edit: I see that several other people already mentioned PNaCl further down in the thread. A hazard of HN's sorting, I guess.)

Re: Why are we limited to JS in browsers - would a bytecode ... by dkersten on Tuesday November 23, 2010 @12:45PM (#1934590)
LLVM bitcode is processor specific. Not sure where, but I saw that mentioned in the LLVM docs.