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.

  • @sizeoftheuniverse
    link
    30
    edit-2
    7 months ago

    Yes it does, the only parts where Java doesn’t shine are usually some advanced features that are nightmarish for people who are building tools and libraries:

    • The type system is so 90s and it’s kept like that for backwards compatibility.

    • Generics having type erasure is again an improvisation for the sake of backwards compatibility. It makes writing generic code in conjunction with Reflection painful.

    • The lack of control for the memory layout. I mean in most cases you dont need full control, but there are use cases where it’s literally impossible to do optimisations that are easy to do in C/C++. You must have faith in the JVM and JIT.

    • Integration with native code is cumbersome.

    Other than that Java is fine for most backend work you need to do, except probably for Real Time Processing apps where every millisecond count, but even there there are ways.

    You use Java not for the languages itself, but for the tooling and the ecosystem.

    • moonleay
      link
      fedilink
      67 months ago

      You use Java not for the languages itself, but for the tooling and the ecosystem.

      This is why I love Kotlin so much. You can use the Java ecosystem with a modern language.

    • Tom
      cake
      link
      47 months ago

      Project Panama is aimed at improving the integration with native code. Not sure when it will be “done”, but changes are coming.

    • @[email protected]
      link
      fedilink
      37 months ago

      There is also a big enterprise group who write extra verbose legacy java, vs a more modern light way to write

      • @sizeoftheuniverse
        link
        5
        edit-2
        7 months ago

        Yes, i was part of the cult in my early days as programmer. I would endlessly create abstractions over abstractions. But the whole madness started for valid reasons.

        Im the early days of Java on the web, you had servlets and JSP. Servlets were miserable to write, and JSPs were basically the java interpretation of having a PHP. Those were the days before JSON and yaml, when XML was king.

        So people wanted to abstract their way out of JSP and XML, so they created layers to isolate the nasty parts and make it easier to write actual Java code. So a few ideas emerged/frameworks: ORMs, EJBs, Struts, JSF, template frameworks, and finally Spring which was the lightweight one, if you can believe it. A lot of those ideas coming from the Java world were exported into various other languages in a selective ways.

        People experienced with various patterns and frameworks. Eventually Spring won, and then Spring started to use annotations, JSON became more popular, etc., the code became less and less verbose.

        Some Java developers never made the mental jump and are still creating huge piles of abstractions because this is what they’ve learned from their seniors.