Let’s reinvent java bytecode but… different

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

    Oh yeah how did I forget the billion dollar mistake, definitely one of the worst misfeatures of Java

    • magic_lobster_party@kbin.run
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      9 months ago

      I think having null is great in some cases where you need to represent missing value. It’s just that there’s no good way to know for sure if you need to do null checks or not. The only way around it is to do null checks everywhere, which no one wants to do because fuck that. Nowadays there’s Optional which solves some of this, but it was introduced way too late.

      If I were to redesign Java the first thing I would do is to add a nullable keyword or something.

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

        I think having null is great in some cases where you need to represent missing value.

        Option types or sum types would probably be a much less terrible choice for this, although I guess some sort of nullable keyword counts as a sum type