Let’s reinvent java bytecode but… different

  • AggressivelyPassive@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    I mean, hardly anyone complaining about Java does so because of JVM bytecode.

    I’m not sure, where the wasm hate is coming from.

    • onlinepersona@programming.devOP
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      3 months ago

      No hate, just a stupid meme. WASM has the possibility of replacing JS in the browser, however it had to reinvent the JVM 🤷 As long as it gets rid of the JS dominance in browsers, I’m all for it.

      Anti Commercial AI thingy

      CC BY-NC-SA 4.0

  • testfactor@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Do you really think the reason people hate Java is because it uses an intermediate bytecode? There’s plenty of reasons to hate Java, but that’s not one of them.

    .NET languages use intermediate bytecode and everyone’s fine with it.

    Any complaints about Java being an intermediate language are due to the fact that the JVM is a poorly implemented dumpster fire. It’s had more major vulnerabilities than effing Adobe Flash, and runs like molasses while chewing up more memory than effing Chrome. It’s not what they did, it’s that they did it badly.

    And WASM will absolutely never replace normal JS in the browser. It’s a completely different use case. It’s awesome and has a great niche, but it’s not really intended for normal web page management use cases.

  • anton@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    The main difference is that WASM is an agnostic bytecode without a gc while the jvm is opinionated in a java way. It has a gc, focus on dynamic dispatch and it has knowledge of concepts like exceptions, classes and visibility.

    All this leaking of abstractions means languages like java and kotlin are well suited, scala has hit problems and c couldn’t be compiled to java bytecode.