3 ms·
The JVM problem was that it had applets and did not have the DOM integration of Javascript. I do often wonder if instead of Javascript in 1995 we had got WebAs
by protomyth 11y ago
The JVM problem was that it had applets and did not have the DOM integration of Javascript. I do often wonder if instead of Javascript in 1995 we had got WebAssembly and WebSockets.
- icedchai 11y agoYou could actually call into JavaScript from Applets, using something called LiveConnect. See https://docs.oracle.com/javase/tutorial/deployment/applet/invokingJavaScriptFromApplet.html https://docs.oracle.com/javase/tutorial/deployment/applet/in... Was it simply/easy? No. But, you probably wouldn't want to.. The DOM is a crappy way to build an application UI. Someday we might figure that out.
- esailija 11y agoIf you consider custom elements, how is it different from any other way of building ui?
- cheez 11y agoThe concept of the DOM is so widely considered to be useful in declaring user interfaces, that multiple languages have copied it. http://fxexperience.com/wp-content/uploads/2011/08/Introducing-FXML.pdf http://fxexperience.com/wp-content/uploads/2011/08/Introduci... https://en.wikipedia.org/wiki/Extensible_Application_Markup_Language https://en.wikipedia.org/wiki/Extensible_Application_Markup_... The HTML DOM sucks, but what other DOM is widely available and already installed on literally every machine on the planet?
- Touche 11y agoProbably the 2 minute startup time was a bigger problem for applets.