3 ms·

Lots of people are so confused by all this. From Java 11 onwards the "Oracle JVM" is exactly the same as the "OpenJDK JVM". The only difference is that one has

Lots of people are so confused by all this. From Java 11 onwards the "Oracle JVM" is exactly the same as the "OpenJDK JVM". The only difference is that one has the Oracle name on it and if you buy it, has long term commercial support. It's actually the other way around to what you think. Earlier versions had proprietary features you had to pay for. Now there are no proprietary features anymore. The only thing you pay for is support.

brown9-2 8y ago
The “free” Oracle JDK is also coming with a license that limits its usage, which is what the parent poster is referring to.
- repolfx 8y ago
  Yes but my point is (and I do think their branding is dumb here), there's no difference between Oracle JDK and OpenJDK anymore except the name. Simple rule: if it has "Oracle" in the front now, you have to pay to use it in production. If it has "Open" you don't.
Nursie 8y ago
> The only difference is that one has the Oracle name on it and if you buy it, has long term commercial support. And that you need to pay for it if you want to deploy the "Oracle" version. It's not optional paid support. I am aware Oracle produce both, and that the OpenJDK build is every bit as 'official', I have no problem with this. Please don't call me confused, my original statement is still true - Oracle branded JVMs will no longer be free for production use.
- yourapostasy 8y ago
  > ...Oracle branded JVMs will no longer be free for production use. I was confused by the indignation in this thread. A JetBrains blog post [1] seems to say that if you have been coasting on OpenJDK in production, as long as you don't plan to use any OracleJDK-specific features now or in the future, and as long as you use Java 11 in all your implementations, then the license change is not a material difference to you. Not supporting older Java specs for free sounds reasonable to me, is there something wrong with that posture that someone can care to enlighten me upon? [1] https://blog.jetbrains.com/idea/2018/09/using-java-11-in-production-important-things-to-know/ https://blog.jetbrains.com/idea/2018/09/using-java-11-in-pro...
  - Nursie 8y ago
    I'm honestly not sure either. I'm just noting the change in licensing. As I mentioned in the other fork of this thread we're going to move from Oracle 8 to OpenJDK 11 soon, and that's great. No problem at all. Literally all I've tried to say is that there is a license change on the Oracle branded version, and you need to take note of it if you have been using the Oracle branded version and were going to continue. This is not really a complaint! I'm not sure why this seems to be controversial.

brown9-2 8y ago

The “free” Oracle JDK is also coming with a license that limits its usage, which is what the parent poster is referring to.

repolfx 8y ago
Yes but my point is (and I do think their branding is dumb here), there's no difference between Oracle JDK and OpenJDK anymore except the name. Simple rule: if it has "Oracle" in the front now, you have to pay to use it in production. If it has "Open" you don't.

Nursie 8y ago

> The only difference is that one has the Oracle name on it and if you buy it, has long term commercial support. And that you need to pay for it if you want to deploy the "Oracle" version. It's not optional paid support. I am aware Oracle produce both, and that the OpenJDK build is every bit as 'official', I have no problem with this. Please don't call me confused, my original statement is still true - Oracle branded JVMs will no longer be free for production use.

yourapostasy 8y ago
> ...Oracle branded JVMs will no longer be free for production use. I was confused by the indignation in this thread. A JetBrains blog post [1] seems to say that if you have been coasting on OpenJDK in production, as long as you don't plan to use any OracleJDK-specific features now or in the future, and as long as you use Java 11 in all your implementations, then the license change is not a material difference to you. Not supporting older Java specs for free sounds reasonable to me, is there something wrong with that posture that someone can care to enlighten me upon? [1] https://blog.jetbrains.com/idea/2018/09/using-java-11-in-production-important-things-to-know/ https://blog.jetbrains.com/idea/2018/09/using-java-11-in-pro...
- Nursie 8y ago
  I'm honestly not sure either. I'm just noting the change in licensing. As I mentioned in the other fork of this thread we're going to move from Oracle 8 to OpenJDK 11 soon, and that's great. No problem at all. Literally all I've tried to say is that there is a license change on the Oracle branded version, and you need to take note of it if you have been using the Oracle branded version and were going to continue. This is not really a complaint! I'm not sure why this seems to be controversial.