4 ms·

I 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/

by jdance 7y ago

I 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 ago
WebAssembly 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 ago
    That doesn't look like production ready, nor integrated into browser developer tools.
kasperni 7y ago
Which, 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.