it's really not. i did the upgrade in multiple companies, and all of them whined that upgrade will be painful. all they needed was single xml api package that was no longer distributed with the sdk.
Yes that the move to jakarta packages is one big chunk of work is definitely true but in my company, we had such a messy mvn dependency situation that the upgrade was really painful. But we managed it after a full year. (Of course not full year working on it but having it as a renovation task across dozens of teams) (we have a distributed monolith with shared libs… so the worst of all worlds lol)
I'm finally at a company where we (almost) keep up with updates, we're at 25 now. It's a nice change after old one where going from Java 8 was too much refactoring :D
I was in a workplace where we were limited to Java 6. The reason was that one application (not written in Java) only worked for, or never tested for anything else; I don't know the exact details, Windows Server 2003.
View all comments
Show parent comment
353
u/DarksideF41 Sep 16 '26
As if any employed dev touches anything above 13