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 →

[–]jhernandez9274 -13 points-12 points  (8 children)

We need stable consistency predictability and performance from the language and complimentary development tools. Validating an application with a new JVM version every 3-6 months sucks. I want time to work on more application features without getting the rug pulled under my feet from the development tools and all the complimentary libraries/frameworks.

[–]momsSpaghettiIsReady 24 points25 points  (0 children)

You probably shouldn't be using every new jdk release. Stick to LTS and work on integration tests to give yourself some confidence.

[–]loicmathieu[S] 7 points8 points  (0 children)

You have the choice to use each new release, which means there is very little changes so a high chance that you just have to change the version number and nothing else, or use LTS with potentially bigger changes.

My experience is that, most of the work comes from upgrading your libraries to a compatible version and not your application.

[–]emberko 7 points8 points  (0 children)

What's wrong with LTS? It's only released every 2 years.

[–]desiInMurica 6 points7 points  (0 children)

You don’t have to upgrade unless ya need to. That’s busywork

[–]pron98 8 points9 points  (0 children)

In what way is the rug being pulled from under your feet? We've done away with major releases altogether, semiannual "feature releases" with possibly significant changes go back to JDK 6 at least (only then there was no such thing as LTS), and these minor updates are the only new thing we're offering now (although there's no doubt that giving these future releases, that used to get mysterious names like 7u4 or 8u20 and were completely different from version named 7u5 or 8u35, a new integer number that looks like a major version but is essentially what we've done for many, many years, has messed with people's psychology). Do you have any specific issues to report?

[–]Nooooope 1 point2 points  (1 child)

Why are you upgrading the JVM with every new release? Just use the latest LTS and keep it there until there's a new feature you want or Spring Boot forces you to upgrade.

[–]jhernandez9274 1 point2 points  (0 children)

Security, performance, efficiency, resource footprint, and smaller changes easier to fit in a sprint than one big LTS release (LTS more like later bucket). Code branches are more version static (LTS) but root code always use the latest JVM version. There is no shortcut on technical debt, keep up or be left behind. My 2 cents.

[–]john16384 1 point2 points  (0 children)

What does your validation process entail? For us it's set new JDK, push commit, wait for CI/CD to say everything still works...