Hacker News new | ask | show | jobs
by creshal 587 days ago
We just finished upgrading all our Java 1.2 code to Java 17, the Java 6 projects are next :)

I doubt we'll get around to the Java 8 stuff before 2030.

3 comments

Interesting, and a testimony to the stability of the jdk in a way. Did you use any automation tools for the migration I wonder?
The new code was written by a different department, so I'm a little hazy on the details, but I doubt it. It's a 25 years old line of business app, and it's in violation of every guideline, rule and law it touches, and only alive because it got grandfathered through various certifications and audits.

99% of the work was redesigning the business process it supports to be in compliance, and then write a new LOB app that takes inspiration from the old one, but works with the new process.

You might be able to use AI for the remaining 1% mind- and pointless boilerplate code Java requires for no good reason.

I expect 1.2 isn’t as bad as going from 1.4 or 8, not as many javax packages back then?
Are you hiring?
Trust me, you don't want that job :D I've been fighting to get our services to Java 21 from Java 8/11 for the last year or so, I've been partially successful but our main API (and 1/2 monolith) is still a dropwizard app on Java 11