What to do if java charges

Recently, news about JDK starting to charge has been flying all over the place. Various messages are mixed in, and some Java engineers or companies that use Java application development are inevitably worried. The following is what former Oracle chief engineer Yang Xiaofeng said on this topic. analyze.

Recently, there have been constant rumors about Java charging. I didn’t want to comment on this. After all, some responsible media have already clarified it many times, and my own position is not neutral. , and, if you read those articles carefully, you will find that the first sentence is often self-contradictory.

However, there are still some friends in the enterprise who are constantly asking, including a former colleague who once worked in the Java group, whether there are really any legal risks in using Java in the future? Will Java still develop in the future? It seems that the chaos caused by the rumors is beyond imagination.

In view of this, let’s be clear, Java is still free! And regarding everyone’s main questions, I would like to share my personal views:

First, “My company wants to use new versions such as JDK 11, but does not want to pay, what should I do?”

Enterprise users still have reliable ways to obtain free JDK. They can use GPL-licensed OpenJDK released by Oracle and others, or use OpenJDK products released by the AdoptionOpenJDK community, etc., or even capable users build it from the source code themselves!

Second, "I don't want to upgrade JDK. Can I still use the current JDK 8?"

Of course you can! This is normal software EOL. OracleJDK 8 just stopped free updates after being supported for nearly 5 years. Note the "update". Users who continue to use JDK8 are no different from users who are currently stuck on JDK 6 and 7. To facilitate understanding, you can compare it with customers who are still using Windows 7 or XP. They are only unable to obtain security updates, but they will not lose the right to use them. This depends on the user's own judgment and choice.

Third, "What if you still want to get the JDK 8 update?"

This depends on what JDK you are using, please consult us accordingly It's the manufacturer's strategy. Most enterprise users should be using Oracle JDK, so they need to subscribe to Oracle JDK support services before they can update. Of course, individual users can continue to update for free until December 2020. Users of other vendors such as Azul, Redhat, IBM, etc. also need to confirm the relevant roadmaps. For JDK 8 users, this is the only situation where they may need to pay.

Fourth, "Java is GPL licensed. Do I want to open source applications developed in Java?"

No, this is pure nonsense, Java The developed application has nothing to do with OpenJDK's GPL authorization!

More than one friend has expressed concerns about Java GPL v2 CPE protocol authorization. The source seems to be the recent promotional selling point of an open source project. This can only be admired for its imagination and values. Even GPL can be an attack. Point, I really have mastered the core competitiveness~

OpenJDK’s GPL authorization will only restrict manufacturers that produce and release JDK products based on OpenJDK source code, not applications developed by Java. It is simply impossible for most users It is a JDK manufacturer, so there is no need to worry. Moreover, Java is not open source only today. There are many open source projects licensed under GPL, such as Linux, which is also one of the most common and popular licensing options in the industry.

Okay, let’s not dwell on this issue anymore. Serious IT decision-makers may have always thought this was a joke. Maybe you will be curious,

Why has Java caused such a stir recently? So confused?

Personally, I think this is the combined impact of historical reasons and the ongoing changes in the OpenJDK community, and some domestic self-media only care about attracting attention:

Chapter 1. JDK! = Oracle JDK

For a long time, because Oracle has provided a nearly "free" JDK, most Java users, especially individuals and small and medium-sized enterprises, have had the illusion that "JDK = Oracle JDK "Although IBM, Azul, Redhat, etc. all have their own JDK products released to the public, there are also many enterprise users. This deep and natural dependence has caused huge discomfort at the end of the free support period of JDK 8.

Secondly, JDK 8 and others have been so successful that it will take a while for subsequent JDKs to be adopted.

A common practice of OpenJDK is that after many years of free support, the Oracle JDK version enters EOL (End of Life) and then gives up leadership, and the community takes over and leads subsequent updates. .

However, after nearly 5 years of development, JDK 8 is still very popular. Users are not ready and do not have enough motivation to upgrade JDK, not to mention many users who are still using JDK 6 and 7. , this may be a problem faced by all basic software.

Third, the power center of OpenJDK is shifting to the community!

Java is gradually adopting a faster iteration cycle (one major version every six months), more open product features (Oracle has open sourced ZGC, AppCDS, JFR, etc.) and more active community collaboration (for example, The ProjectSkara project will switch the OpenJDK code library to github), etc.

Although it is likely to be a benefit in the long run, it inevitably brings confusion, because developers need long-term confidence in the Java ecosystem, and enterprise IT decision-makers need a predictable Java roadmap, which often comes from the core The long-term dominance of manufacturers, "What freelancers actually like most is five insurances and one housing fund!".

Okay, finally it is clear again that Java is still free, OpenJDK is becoming more open and active, Java/JVM has a clear development roadmap, time will tell everything. To paraphrase the official announcement, Java developers and IT decision-makers can take "reassurance":-)

The above is the detailed content of What to do if java charges. For more information, please follow other related articles on the PHP Chinese website!