Java: RedHat X IBM Annoucement

10 points by seinecle 5 months ago | 6 comments
  • palmfacehn 5 months ago
    >However, today Java is at an inflection point. Customers are facing end of lifecycle and support uncertainty (such as the upcoming end of Java 8 community support and the challenging prospect of migrating countless applications to newer but substantially different versions of Java).

    I'm unaware of cases where Java 8 sources will not compile on newer JVMs.

    • exabrial 4 months ago
      I think you're correct: Compile shouldn't be an issue, it's usually things from the standard JDK being removed.

      A recent example is JAXB classes/APIs being removed from SDK into their own lib jars.

      If the legacy system uses some arcane build system I could see this being an issue.

      • java-man 5 months ago
        It's probably just the pain thart comes from modularization.
      • seinecle 5 months ago
        Am I misreading or is Redhat "selling" its Java team to IBM? Or what? Why?
        • henk53 5 months ago
          IBM already owns Red Hat, but for a few years it operated as a largely individual company still.
        • pinewurst 5 months ago
          I have to imagine the so-to-be IBMers aren’t happy. Among other things, they’re now stuck with IBM’s BS once a year 401k match.