3 ms·
The VM may or may not compare, from some abstract standpoint, but: 1. the startup time and upfront memory usage of V8 and other JS VMs is incomparably lower (b
by etatoby 8y ago
The VM may or may not compare, from some abstract standpoint, but:
1. the startup time and upfront memory usage of V8 and other JS VMs is incomparably lower (better) than that of HotSpot; and
2. Java in the browser was relegated to gray opaque squares, while JS / Wasm has control of the entire viewport and all browsers APIs.
Those two points alone make it a clear winner. Not to mention the horrible security track of Java, probably due to the complexity of its implementation.
- specialist 8y ago#1 Java's poor startup time used to be a problem. Even back in the day, the correct answer was Sun's HotJava, running applets within a native Java runtime, which was killed in the crib to appease NetScape. You've heard the cliche about how sufficiently complicated 'C' programs recreate LISP, only poorly? 20 years recreating WORM applets. 20 years recreating grid computing and software agents (now pimped as 'serverless'). Imagine the world today if Sun had had some saavy championing their own tech. #2 Canvas. The inevitable omega point will be tunneling X-Windows thru the HTTP, HTML, CSS, JavaScript (WASM) obfuscation & error injection gauntlet.