Let’s reinvent java bytecode but… different

  • testfactor@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 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.

  • AggressivelyPassive@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    6 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
      ·
      6 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

  • magic_lobster_party@kbin.run
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    Java is disliked because it’s designed around flawed OOP principles developed in the 80s and 90s. The code easily turn into a mess if you adhere to these principles, because they’re flawed. If you avoid using these principles, you will still get a mess, because that’s not how Java is supposed to be used.

    • hydroptic@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      edit-2
      6 months ago

      Java was such a fractal of stupid design choices in its early years, and a lot of it is still there. OOP except when it’s not (int vs Integer, [] arrays but also List et al), no unsigned number types, initially no way to do closures or pass methods around so everything had to be wrapped in super verbose bullshit, initially absolutely dogshit multiparadigm support and very noun-oriented, initally no generics either meaning everything’s an Object, when it did get generics they had to do type erasure for backwards compatibility, etc etc etc