Is Java 21 Keeping Up With Modern Programming Languages
digma.ai
In this article, we'll debunk the notion that Java is a relic of the past and showcase the language's modern features in Java 21.

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.

  • BlueBockser@programming.dev
    4·
    1 year ago

    Lombok will shrink the 200 lines of getters and setters to one or two. It has its own pitfalls of course, but IMO it’s definitely worth it.

    • huginn@feddit.it
      5·
      1 year ago

      Corporate standards.

      I’m pushing for no half measures: it’s Kotlin or bust.

      • BlueBockser@programming.dev
        1·
        1 year ago

        Definitely agree that Kotlin is so much better than Java + Lombok, but it’ll take a lot of time for all the existing Java projects or migrate to Kotlin or reach EOL. In the meantime, it’s hard to avoid the occasional Java project…

        • huginn@feddit.it
          1·
          1 year ago

          Sure but you can also just drop kotlin into any Java codebase. It’s a single line maven import and the entire company already uses Intellij

          • gravitas_deficiency@sh.itjust.worksEnglish
            3·
            1 year ago

            Oh yeah - the seamless Java/kotlin interop is pretty slick, though there are some pitfalls - nullity is one of them. Kotlin treats it explicitly, but when it’s talking to Java, it’s forced to treat it ambiguously unless you wrap stuff in Optional. And then even if you do, some Java lib that you need to plug into your project might not do that, so you’ve got to be careful about managing the interactions between their interfaces in some situations. And then there’s the unfortunate divergence that’s started to occur as newer versions of Java have brought certain features that were first available in Kotlin into Java, but the patterns and interfaces often differ subtly, so you have to worry about that too, especially with less experienced engineers on the team.

            Don’t get me wrong - it’s great, and I’ve enjoyed working with it, but if you’re doing an incremental migration, make sure you test the ever-loving shit out of it.

            Source: I did an incremental Java -> Kotlin migration on a huge project a couple jobs ago

            • huginn@feddit.it
              1·
              1 year 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.worksEnglish
                1·
                1 year 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.