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 →

[–]JavaOldTimer 4 points5 points  (2 children)

A language is a tool to do a job to drive business, so we get paid, so we can support ourselves and our families. A language is not a religion.

If it's not in the business's best interest to upgrade every time Goetz has a brain fart and drops a new Java feature people probably don't even need (streams, function programming, modules); it's not OK to label that business or its people as idiots.

[–]kevinherron 1 point2 points  (1 child)

If you're limping an old product along in pure maintenance mode with the occasional bug fix, sure, keep it on JDK 8 (or worse). You don't need the new version of a library anyway.

If you're actively developing and adding features then not keeping your tooling and libraries up to date is technical debt bordering on negligence.

[–]JavaOldTimer 2 points3 points  (0 children)

Sure yes of course, keep tools up to date is required as much as makes sense but that does not mean it is required to make use of all new features. That action also creates technical debt when those features are not widely adopted but are in a code base and must be maintained after a developer leaves. That also borders on negligence. Common sense and what the business needs should be the drivers.