3 ms·
JavaScript, as I recall, was the answer to Java being crashy and slow on 50 MHz processors. Microsoft tried to make VBscript happen, but was very Microsofty wit
by notquitehuman 5y ago
JavaScript, as I recall, was the answer to Java being crashy and slow on 50 MHz processors. Microsoft tried to make VBscript happen, but was very Microsofty with the licensing, so JavaScript won by default. It’s been good enough to prevent people from successfully replacing it, but annoying enough that people keep trying.
- eqvinox 5y ago> JavaScript, as I recall, was the answer to Java being crashy and slow on 50 MHz processors. [citation needed] Having lived through that period of time, I do not recall Java applets and JavaScript ever being considered to be in the same category / trying to solve similar problems.
- mileza 5y agoHistorical records seem to contradict themselves on this matter. What I recall reading was that they were created for two different things: JavaScript was created to add basic interactivity on the page, and Java was intended to be used for more CPU-intensive work.
- garmaine 5y agoJavaScript was contemporaneously developed alongside Java, to target a different niche: https://auth0.com/blog/a-brief-history-of-javascript/ https://auth0.com/blog/a-brief-history-of-javascript/
- aasasd 5y agoJava literally runs on smart cards, including SIM cards: https://en.wikipedia.org/wiki/Java_Card https://en.wikipedia.org/wiki/Java_Card — and did so since the 90s. My guess is, applets were crashy for different reasons than CPU speed.
- dcminter 5y agoJava wasn't crashy as I recall it. Nor was it slow once the applet started. It was slow in the sense that downloading the class files (usually over a modem, sob) and firing up the JVM wedged your webpage for a good while!
- some_chap 5y ago> JavaScript, as I recall, was the answer to Java being crashy and slow on 50 MHz processors. Not in the least - The early scripting language Mocha, was first renamed to LiveScript then Netscape and Sun did a license agreement and it became JavaScript. And the idea was to make it a complementary scripting language to go with Java, with the compiled language. Purely marketing, to attempt to use the popularity of stand-alone Java for an in-browser scripting solution.