• OpenPassageways@lemmy.zip
    link
    fedilink
    arrow-up
    3
    ·
    2 hours ago

    I think it was 5 to 6 that was a really tough one for me because we had an in-house state management library that broke with the major breaking changes to RxJS. After that was pretty much no issue all the way from 6 to 17.

    • Sinuousity@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 hour ago

      Confusing syntax to replace confusing syntax, library dependencies that let you do nothing you couldn’t do without them. Generic solutions are always the best for specific problems, right?

  • abbadon420@lemm.ee
    link
    fedilink
    arrow-up
    13
    ·
    5 hours ago

    Java is also a lot of fun in this regard. They’ve actually dropped support for java 8 about 2.5 years ago. But Oracle has added a “premium subscription” that gives companies another decade or so of extra support to delay updating their code even further. https://endoflife.date/oracle-jdk

    • MHanak@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      4 hours ago

      Isn’t java generally backwards compatible? I switch java versions willy nilly in my (small) projects and never really noticed any problems when upgrading the version

      • abbadon420@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        3 hours ago

        Yes sure, but not forwards compatible. That means if you need to fix a bug or add a feature in a project that is build on java 8, you cannot use language features from later versions. They are pretty important features at that, like a workable Http client, modules, container compatibility, records and enhanced switch statements. It is not fun to work like that, it’s what makes good programmers want to become chicken farmers.

    • elvith@feddit.org
      link
      fedilink
      arrow-up
      4
      ·
      4 hours ago

      Worse yet. They switched licensing and costs several times and companies should prepare to get hit with new licensing fees:

      When they introduced Java 17 (a LTS version), they published it under the NTFC license. This means, this version is usable for free, but only until the next LTS version has been out for a year.

      On Sep 19th 2023, Java 21 was released another LTS version. That means, that Java 17 just switched from the NTFC license to the OTNLA license a few days ago - which means, Java 17 is supported until 2029 but you now need a paid license to use it.

      Hope everyone upgraded to Java 21 or newer in time.

  • bleistift2@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 hours ago

    If only their “automatic” updater worked without throwing errors on every migration…