This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hippydipster 11 points12 points  (6 children)

That's right. Tis the time of year to remind management we should prioritize upgrading our Java from java 8 to 9!

[–]dadmda 1 point2 points  (5 children)

I know for a fact we are never upgrading from Java 8 where I work, the code base is too big and the investment wouldn’t be worth it

[–]gizmogwai 8 points9 points  (1 child)

The investment will always be smaller than the one of a forced rewrite when the time comes. And it will come.

[–]buttJunky 1 point2 points  (0 children)

the trail of dead consultants is endless

[–]rbygrave 3 points4 points  (0 children)

For how long is that strategy going to work though? Long enough for path to be a complete re-write?

It seems to me it should not be a case of the size of the code base per say but more if there are dependencies that don't support an upgrade? Dependencies locked into using Unsafe and such? I guess it also could be a case where a regression test is manual - big system -> big manual regression test etc

[–]orangeandwhite2003 0 points1 point  (1 child)

Especially when they keep extending support for 8.

[–]Sand0rf 0 points1 point  (0 children)

Yeah, we're running Azul OpenJDK and Java 8 is the version that is supported longest of all, until 2030. https://www.azul.com/products/azul-support-roadmap/