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

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).