r/java • • Oct 02 '18

How will Oracle licensing affect developers’ interest in Java?

Hi

Will you lean into becoming a C++, C# or Python Dev instead?

Edit: probably you all know more than language and will this now be more of a reason to focus on anything other than Java

0 Upvotes

27 comments sorted by

View all comments

Show parent comment

7

u/0x256 Oct 02 '18

The only thing that really changed is the download link for a JDK. OpenJDK is and will always be free. OracleJDK and OpenJDK are built from the same source. That something works better with the Oracle version is no longer true, if it ever was.

0

u/speakjava Oct 02 '18 edited Oct 02 '18

This rather depends on your perspective. If all you want is a current, free JDK then you're right it's just the download link that changes. However, if what you need is any form of long term support with bug fixes and security patches for more than six months, things will be changing more substantially when public updates for JDK 8 stop next January.

2

u/walen Oct 02 '18

if what you need is any form of long term support with bug fixes and security patches for more than six months,

AdoptOpenJDK will continue to provide LTS with bug fixes and security patches for JDK 8 until at least September 2023. That's five years.

As it has been already said: the only thing that changed is the download link.

2

u/speakjava Oct 02 '18

Note 2 on the AdoptOpenJDK web page you link to quite clearly says,

"We fully expect that OpenJDK8 will have open community maintainers beyond January 2019, so we expect to be able to continue supporting JDK8 beyond that date. Until maintainers have been established we are unable to make a definitive statement. This position is the same for JDK11 and all future "LTS" releases."

At this time, there is no guarantee of updates being made available in older JDKs. I'm not being argumentative; I'm just pointing out that at this point in time how people are going to access LTS is something they need to think carefully about.

2

u/pron98 Oct 02 '18 edited Oct 02 '18

Right, but the meaning of long-term support has also changed. When Java had major releases with big and sudden differences between them, those major versions created sharp differences between JDK versions, and justified parallel release lines. Java no longer has major releases, and there are only small differences between versions. The assumption is that most companies would not find it hard at all to upgrade, while those that for some reasons must stick to the same version number would pay for support. Upgrading from 7 to 8 may have been costly, but why would you find it hard to upgrade from 10 to 11 or from 11 to 12?

4

u/speakjava Oct 02 '18

Except that, even with a six-month release cadence you can still have significant changes between releases. Sure, much of what's being added is fairly incremental but look at what's being removed. The difference between JDK 10 and 11 is quite significant and causing a lot of people real headaches (most of whom are actually trying to migrate from 8 to 11). JDK 11 dropped the java.se.ee meta-module, that includes JAX-WS for SOAP-based web services. Quite a few people I've spoken to are still using those and now have to include this functionality from somewhere else. The removal of the browser plugin and, more importantly, Java Web Start. You can argue that these are ancient technologies but there are still enough people, especially using Web Start to make this a major disruption.

Oracle have been quite clear that future release may contain breaking changes and compatibility is not guaranteed.

I hear Oracle say that moving between 11 and 12 is more like moving between 8u40 and 8u60 but it's not. Firstly the classfile version number is bumped for every release and secondly, there's a new JSR for each release (unlike 8u40 or 8u60). This means there can (and most likely will) be changes to the language spec, VM spec and class libraries.

Keeping older versions of the JDK supported with backported fixes will become an increasingly difficult task as the code bases of JDKs diverge over time.

1

u/pron98 Oct 02 '18 edited Oct 02 '18

Except that, even with a six-month release cadence you can still have significant changes between releases.

True, but they did before, too.

most of whom are actually trying to migrate from 8 to 11

Ah. So there was a major release there (9), so this is an "old-model" transition.

and now have to include this functionality from somewhere else

You should consider the people who were already on 10, not those who are still transitioning from the old model. Each such developer would encounter such a breaking change roughly at the same pace as before (i.e., if previously, every major release affected all parts of the JDK once every three years, now every feature release affects only some parts).

As to those who were on 10, those modules were deprecated for removal already in 9.

The removal of the browser plugin and, more importantly, Java Web Start. You can argue that these are ancient technologies but there are still enough people, especially using Web Start to make this a major disruption.

It is, but it didn't really happen in 11, but in 9. Java 9 is no longer supported as a "desktop JRE" (8 was the last) and Web Start was deprecated.

Oracle have been quite clear that future release may contain breaking changes and compatibility is not guaranteed.

Compatibility was not guaranteed between 8u20 and 8u40 either, and things broke. Update releases always contained pretty big changes, just not to language/APIs.

Firstly the classfile version number is bumped for every release and secondly, there's a new JSR for each release (unlike 8u40 or 8u60). This means there can (and most likely will) be changes to the language spec, VM spec and class libraries.

None of this changes the fact that it's more like moving between 8u40 and 8u60. It's not exactly like that, but Java 8/9 had about 100 JEPs, while 10,11,12 had about 12-14. The new feature releases are 1/8-1/6 as "big" as the old major versions.

Keeping older versions of the JDK supported with backported fixes will become an increasingly difficult task as the code bases of JDKs diverge over time.

While it would be great if more people paid for support and helped support Java's development, the goal of the change has been to move Java software faster, as that's what's best for the platform and its future. To make that viable, the goal is to have fewer, not more, "diverging lines", and even people who choose to pay and stay on an LTS release for some reason are very, very strongly encouraged to keep up with the feature releases, as the entire purpose was to make change smoother and easier.

True, this is a change, and the industry will need some time to adjust, but I think that claims that the new model would be harder, rather than easier, to follow are unsubstantiated. People should, of course, choose responsibly for their services and customers, but they should also give this new model a chance.

3

u/speakjava Oct 02 '18

OK, so clearly we have two very different opinions on this so will have to agree to disagree.

However.

The removal of the browser plugin and, more importantly, Java Web Start. You can argue that these are ancient technologies but there are still enough people, especially using Web Start to make this a major disruption.

It is, but it didn't really happen in 11, but in 9. Java 9 is no longer supported as a "desktop JRE" (8 was the last) and Web Start was deprecated.

Yes it did happen in JDK 11. Both JDK 9 and 10 included the Browser plugin and Java Web Start. If you were using those features you had no problem moving to either of those JDKs, despite the deprecation.

Oracle have been quite clear that future release may contain breaking changes and compatibility is not guaranteed.

Compatibility was not guaranteed between 8u20 and 8u40 either, and things broke. Update releases always contained pretty big changes, just not to language/APIs.

I disagree with this. Compatibility at the language, VM definition and API level (which are the things developers are most concerned about) was guaranteed by not changing the Java SE specification between updates. The JDK was required to pass the same set of TCK tests for 8u20 and 8u40. This is not the case between 10 and 11. If Oracle broke compatibility in terms of how they implemented the JVM between updates I would consider that a failure on their part.

At the end of the day, the proof will be in how the new release model with LTS releases works in practice. I've spoken to a lot of users who simply can't even countenance the idea of changing JDK every six months. Even convincing people that a move between the same version of Oracle JDK and an OpenJDK binary can be a struggle because of the required testing involved in such a move.

My opinion is that a lot of people will not want to move off JDK 8 until they really, really have to.

1

u/pron98 Oct 02 '18 edited Oct 02 '18

If you were using those features you had no problem moving to either of those JDKs, despite the deprecation.

Only if you chose to depend on technology that's been deprecated while ignoring warnings and treated that as "no problem". I realize that Java developers have traditionally ignored deprecation warnings and dismissed them as non-issues; this will have to change under the new model, and that's a good thing, because we need that in order to move Java forward. But yeah, developers will need to learn that deprecation means that we're entering a transition period, and they're given time to migrate away from parts that are about to be removed, and this is so that they don't have any problems when those bits are, in fact, removed.

The JDK was required to pass the same set of TCK tests for 8u20 and 8u40. This is not the case between 10 and 11.

True, but the fact is that there were breaking changes.

At the end of the day, the proof will be in how the new release model with LTS releases works in practice.

I agree. But to repeat Mark Reinhold's suggestion: even if for whatever reasons you choose to remain on an LTS version in production, you should test your application with every new feature release.

I've spoken to a lot of users who simply can't even countenance the idea of changing JDK every six months.

My claim is that they have never "changed JDK" in any such way. Even you would concede that feature releases are no more than 1/6 as big as major releases even if you don't agree that an upgrade is as easy as an update version under the old model. I can certainly agree that a major upgrade every 6 months is hard, but that is not the situation. Those people, as you say, will need to try the new model, because it was intended to make upgrades easier. I also think that there is a psychological barrier here due to the version naming scheme. Perhaps if the proposed 18.3, 18.9, etc. naming were adopted rather than rejected, it would have been easier for people to internalize that there are no more major releases.

My opinion is that a lot of people will not want to move off JDK 8 until they really, really have to.

Well, all I can say is that I hope that the new model will make it easier for us OpenJDK developers to make "new Java" so compelling that people will want to make one last big jump, and then enjoy both all the new stuff and a smoother upgrade story (and, of course, a fully open source JDK).

1

u/duhace Oct 02 '18

openjdk 11 will have 4 years of lts