Hacker News Reader

>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.

It's probably just the pain thart comes from modularization.

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.

Am I misreading or is Redhat "selling" its Java team to IBM? Or what? Why?

IBM already owns Red Hat, but for a few years it operated as a largely individual company still.

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.

Java: RedHat X IBM Annoucement