Like lots of the internet, a large chunk of public minecraft servers are linux, which defaults to openjdk, and usually takes extra steps to get oracle's jdk installed.
#OPENJDK VS ORACLE JDK LICENSE#
OpenJDK's license is GPLv2 with a class exception that ties to particular java libraries you can link to, even this exception allows free distribution and usage. Spigot already modifies the minecraft server code, so watching it for something that breaks without oracle's jdk is simply an extra step.
#OPENJDK VS ORACLE JDK CODE#
OpenJDK exists, is stable, and reliable, and Oracle isn't the sole contributor to the code, additionally, while a small payment to devs for there code is a good thing, 25/cpu/mo is absolutely obscene. Or, MS will also not be happy with oracle about this, but their solution will be to push for the end of java edition. (My day-job actually uses a firewall that requires a java app for management that does this). So depending on what Oracle does to the JDK behind the scenes, later versions of minecraft's server may actually break on openjdk, or MS/Mojang can do what other "java devs" have done and actually check for openjdk and then "break" the application. MS's ownership of Mojang is going to push things towards oracle probably. This one's gonna be weird for two reasons. Thank you for reading, I am interested to see what discussion this post may create and I will also be willing to try and answer any questions regarding this. I am aware that this only really applies to users running VM's rather than those using Minecraft Hosting services, as I will assume that they have already considered this issue and handled it appropriately. Does running a Minecraft server now incur extra costs that were before not an issue? Where does Spigot stand regarding this situation? What is the best option for the future? To continue with Oracle Java or move to OpenJDK? Is the Oracle EULA and T&C's being breached?
Should we, as server owners, be paying Oracle a monthly fee? I understand that the use of OpenJDK is an option however I find it hard to believe most server owners have any idea what this is and it is not an ideal solution as there are differences between the two JDKs regarding performance and other topics ( ). This suggests that all server owners should be paying $25 per CPU per month, which I'm going to guess almost all servers are not paying. This price could really add up for large servers running multiple CPUs. So, where does this put server owners and administrators, because according to Oracles website regarding the Java subscription pricing ( ), if running Java on a server, you must be paying a fee of $25 per CPU per month. Java major updates will be released every 6 months, with a LTS version being released every 3 years, which will have support for the following 8 years (new every 3, each supported for 8)
BuildTools is incompatible with Java 11 other than for 1.13 As of the new development cycle, Java SE is now a paid resource, if being run for commercial purposes Java 11 is the most recent LTS version of Java (Long term support) Java 8 is still the most commonly used for Spigot servers
#OPENJDK VS ORACLE JDK UPDATE#
So I have recently been looking at getting back into Java development for Spigot and have been confronted by the fiasco surrounding Oracles new update cycle and the carnage that it is causing.
0 kommentar(er)
