In this article, we’ll debunk the notion that Java is a relic of the past and showcase the language’s modern features, thriving ecosystem, and unwavering presence in enterprise and open-source communities.

  • huginn
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    Yeah it can be slightly hairy because Java does a terrible job with nullability. I’ve also done an incremental migration of an android codebase to Kotlin.

    Personally I think being forced to declare the nullability of a field is something backend developers should do more of. It helps eliminate some of the foot guns that otherwise get built into the code base.

    I’m a bit of a kotlin fanboy though, I’ll admit.

    • gravitas_deficiency@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 months ago

      I 100% agree that explicit nullity is categorically better, and the vast majority of the entire software engineering field does too. The problem lies in the fact that explicit nullity was added in 2014 with Java 8, nearly two decades after Java 1 shipped in 1996. That’s a hell of a lot of technical inertia to overcome.

      • huginn
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Yeah especially whether Java “runs on 1 billion devices” 😂

        The question is why a new codebase in greenfield is still using basic Java 11 on a new 2023 project.