Re: Why are we limited to JS in browsers - would a bytecode ...
by wmf on Thursday November 11, 2010 @01:48PM
(#1894754)
As a bytecode you wouldn't use a bytecode that is targeted at handling Javascript constructs.
So now you're asking the browsers to support two different VMs; one for JS and another one. Standardizing bytecode for JS (perhaps based on the existing Nitro or JagerMonkey bytecode) would be much less work.
So now you're asking the browsers to support two different VMs; one for JS and another one. Standardizing bytecode for JS (perhaps based on the existing Nitro or JagerMonkey bytecode) would be much less work.