Assuming you want to stay on the latest, using OpenJDK means upgrading major versions every 6 months. And unlike Java of old breaking changes are a real possibility. And if you care about security updates you will get them later, even when on the latest as Oracle had a policy that security fixes get put in OracleJDK first before being back ported to OpenJDK at some point. That and OpenJDK provides zero liability if there are issues, unlike OracleJDK.
Depending on how you use Java this change can be anywhere from a minor speed bump to being catastrophic. You have some small Java services? You likely aren't affected by breaking changes and aren't worried so much about security updates, so you can make the transition to an Open runtime and upgrade when you want. Have critical parts of your solution running Java in the cloud? Staying on the latest version is going to involve more maintenance than you are used to but you don't have much choice. Have Java programs that run on actual users machines? You sir or madam, are screwed.
On the OpenJDK 11 LTS front, Red Hat recently announced their plan to be a leader in making that a reality. Time will tell how well that will work out.
Oracle trying to monetise Java isn't surprising - I mean were talking about Oracle. But if this gamble of theirs doesn't make them the 💰 they expect what will that mean to their Java contribution? As far as I'm aware, Oracle is still the biggest contributor to OpenJDK via their work on OracleJDK.
Depending on how this goes we could be seeing a fragmentation if the language. And without a large backer can Java continue to grow and thrive? Or does it start to enter a sort of maintenance mode?
The biggest concern I have about Java's future now is how many people are going to still seriously consider Java for new projects now? This could be the killing blow that turns Java usage from a C type language to a Cobol type language.
Very true, It might turn into a language of an bygone era. But if the community is not gonna leave java it might just run successfully depending on factors like you said (fragmentation and support).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Assuming you want to stay on the latest, using OpenJDK means upgrading major versions every 6 months. And unlike Java of old breaking changes are a real possibility. And if you care about security updates you will get them later, even when on the latest as Oracle had a policy that security fixes get put in OracleJDK first before being back ported to OpenJDK at some point. That and OpenJDK provides zero liability if there are issues, unlike OracleJDK.
Depending on how you use Java this change can be anywhere from a minor speed bump to being catastrophic. You have some small Java services? You likely aren't affected by breaking changes and aren't worried so much about security updates, so you can make the transition to an Open runtime and upgrade when you want. Have critical parts of your solution running Java in the cloud? Staying on the latest version is going to involve more maintenance than you are used to but you don't have much choice. Have Java programs that run on actual users machines? You sir or madam, are screwed.
On the OpenJDK 11 LTS front, Red Hat recently announced their plan to be a leader in making that a reality. Time will tell how well that will work out.
Oracle trying to monetise Java isn't surprising - I mean were talking about Oracle. But if this gamble of theirs doesn't make them the 💰 they expect what will that mean to their Java contribution? As far as I'm aware, Oracle is still the biggest contributor to OpenJDK via their work on OracleJDK.
Depending on how this goes we could be seeing a fragmentation if the language. And without a large backer can Java continue to grow and thrive? Or does it start to enter a sort of maintenance mode?
The biggest concern I have about Java's future now is how many people are going to still seriously consider Java for new projects now? This could be the killing blow that turns Java usage from a C type language to a Cobol type language.
Very true, It might turn into a language of an bygone era. But if the community is not gonna leave java it might just run successfully depending on factors like you said (fragmentation and support).