Re: Why are we limited to JS in browsers - would a bytecode ...
by InclinedPlane on Thursday November 11, 2010 @02:58PM
(#1895007)
x86 is a perfect comparative example. An architecture that is a patch on a patch on a patch (add several more layers here until you're tired) going back to the 8086 a kajillion years ago (a processor which was less sophisticated and powerful than an arduino). Intel tried to kill the architecture (replacing it with IA64) but AMD patched it yet again and the result was successful.
Nobody sane would design an architecture like x86 (or event x86-64) from the ground up today. Yet here we are.
Re: Why are we limited to JS in browsers - would a bytecode ...
by Zaak on Thursday November 11, 2010 @03:37PM
(#1895139)
We build our computer systems the way we build our cities: over time, without a plan, on top of ruins.
-- Ellen Ullman
Re: Why are we limited to JS in browsers - would a bytecode ...
by Tuna-Fish on Thursday November 11, 2010 @04:17PM
(#1895296)
I would just like to point out that IA64 wasn't really a significant step up. VLIW is a good idea for DSPs and GPUs and whatnot, but for the kind of dynamic, branchy code that we all know and love, IA-64 was quite probably the only somewhat modern CPU arch that was actually worse than x86.
Re: Why are we limited to JS in browsers - would a bytecode ...
by InclinedPlane on Thursday November 11, 2010 @04:28PM
(#1895342)
I'm not so sure about that. Modern IA64 compilers and systems are actually pretty damned decent. Though the fact that they are still only comparable to a monstrous, teetering pile of hacks and kludges (x86) is not much of a recommendation.
Meanwhile Brendan was doing the work of ten engineers and three customer support people, and paying attention to things that mattered to web authors, like mixing JS code into HTML, instant loading, integration with the rest of the browser, and working with other browser vendors to make JS an open standard.
So now JS is the x86 assembler of the web - not as pretty as it might be, but it gets the job done (GWT is the most hilarious case in point). It would be a classic case of worse is better except that Java only looked better from the bottom up. Meanwhile JS turned out to be pretty awesome. Good luck trying to displace it.
SWF was the other interesting bytecode contender, but I don't know much about the history there. Microsoft's x86 virtualization tech was also pretty cool but they couldn't make it stick alone.