4 ms·
JVM was supposed to be this. Gosling said publicly that JVM is more important than Java. . Many things went wrong. Microsoft was actively sabotaging JVM. They
by nabla9 7y ago
JVM was supposed to be this. Gosling said publicly that JVM is more important than Java. .
Many things went wrong. Microsoft was actively sabotaging JVM. They implemented very fast JVM for Explorer and their operating system that intentionally broke the JVM 1.1 standard. See Sun vs Microsoft 1997. Microsoft lost and paid damages. .NET was created to do more damage.
- jdance 7y agoI like the JVM and have done lots of code for it, but the java download&install / setting up PATH / non native gui-look / no exe-files / should i get se/ee/jre/sdk etc etc must be a big contributing factor to its lack of being more popular (client side). A lot of the experience has been clumsy, ugly and unintuitive from the start
- pjmlp 7y agoWebAssembly developer experience is also not the most friendly one, with its mix of toolchains, specially if one is on Windows. Oh, and debugging is still at printf level style and reading raw bytecodes.
- callahad 7y ago> debugging is still at printf level style and reading raw bytecodes Wasmtime has had support for source-level debugging via lldb or gdb for a few months https://hacks.mozilla.org/2019/09/debugging-webassembly-outside-of-the-browser/ https://hacks.mozilla.org/2019/09/debugging-webassembly-outs...
- pjmlp 7y agoThat doesn't look like production ready, nor integrated into browser developer tools.
- kasperni 7y agoWhich, is also why that method for delivering applications has been deprecated for a couple of years. Now, the prefered way to ship a Java application is to bundle the runtime and the application into a single installer similar to, for example, Electron apps.
- hinkley 7y agoYou can blaze a trail that others literally follow, or you can blaze a trail that others figuratively follow. The JVM is definitely more important than Java. But it might not be the most important VM, let alone the most important thing in software. And other languages/platforms emulating that plan doesn't diminish the JVM, except numerically.
- int_19h 7y agoJVM bytecode semantics were all about Java - it forces the Java object model on you, for example. It was never designed to allow a diverse ecosystem of languages.
- kasperni 7y agoYet, we still a lot more new languages on the Java platform. Then say .NET which was designed to be polyglot.
- int_19h 7y agoIf you look at those languages closely, they are usually high-level enough that they can be mapped reasonably well to the JVM object model, or else the language itself is intentionally designed around its limitations (e.g. Scala). But something like C++ doesn't really compile to Java bytecode well. .NET CIL is much better in that regard precisely because it was designed to be low-level enough to compile C to it - it has stuff like raw pointers and pointer arithmetic, stack-allocated arrays, unions etc. The reason why not many languages bothered is longstanding lack of cross-platform support - Mono was around for a while, sure, but it was not the official implementation, and nobody knew whether it'd still be there next year. Today that's not really an issue anymore, but by now wasm is a better choice.
- DonHopkins 7y agoYeah, Microsoft actively sabotaged JVM by developing CLR. Those monsters!