3 ms·
I don't disagree that we're moving further and further away from the documents with links model, but that ship has long past sailed. It wasn't just ActiveX, it
by falcolas 9y ago
I don't disagree that we're moving further and further away from the documents with links model, but that ship has long past sailed. It wasn't just ActiveX, it was Flash. And Java. And Silverlight. And EME. And JavaScript (which, despite the presence of "Script" in the name is not just a scripting language).
Web browsers are currently (to take a reductionist view) just VMs with the ability to also view traditional HTML pages. Java had the right idea with its run-anywhere code and the JVM; it was just a bit too early to the party, and didn't have an HTML viewer to get its foot in the door.
- tannhaeuser 9y ago> Java [...] was just a bit too early to the party, and didn't have an HTML viewer to get its foot in the door. Well, it kindof had one ([1], [2], [3]). Rhino JS (still used all over the place; for example by Google's closure compiler) originated from that time. [1]: https://en.wikipedia.org/wiki/HotJava https://en.wikipedia.org/wiki/HotJava [2]: http://jazilla.sourceforge.net/pmwiki.php http://jazilla.sourceforge.net/pmwiki.php [3]: https://docs.oracle.com/javase/7/docs/api/javax/swing/JEditorPane.html https://docs.oracle.com/javase/7/docs/api/javax/swing/JEdito...
- j45 9y agoOh, swing.
- baybal2 9y agoJava is a bad language, bad design, and bad execution. Having more of Java in JavaScript is bad. Turning browser into a VM is just a recipe to bring pretty much every problem inherent to VMs to web development