2 ms·
> why a compact, concise, standardized bytecode format isn't being pursued Two reasons: 1. Backwards compatibility. 2. We've had such a thing since the 199
by csense 14y ago
> why a compact, concise, standardized bytecode format isn't being pursued
Two reasons:
1. Backwards compatibility.
2. We've had such a thing since the 1990's. It's called Java. Nobody likes it and nobody uses it [1], so that's a good enough reason.
[1] Nobody uses Java in the browser, that is. When was the last time you remember seeing a Java applet?
- astrodust 14y agoI would figure that we'd learned a lot of lessons from Java, and Java was never truly integrated with the browser, always glommed in via some clumsy plug-in architecture. If JavaScript was a plugin it would be just as annoying and useless as an "applet".