11–20 of 25 posts
There's absolutely no reason to pay for Oracle's JDK unless you want Oracle's support.
It was probably intentional, but Oracle really fucked up the marketing on this change and as a result a bunch of FUD has been spread throughout the Java ecosystem.
Just use OpenJDK, Azul, Corretto, etc... There's absolutely no reason to pay for Oracle's JDK unless you want Oracle's support. It was probably intentional, but Oracle really fucked up the marketing on this change and as a result a bunch of FUD has been spread throughout the Java ecosystem.
It's probably cheaper to just use OpenJDK.
Not here, we've migrated to OpenJDK binaries maintained by Red Hat and Azul (depending on OS). They're still FOSS so it hasn't affected us, yet at least. I have never seen an issue from switching Java SE->OpenJDK. We did the whole company in one day without outages. I'm convinced that incompatiblies don't exist in practice.
Earlier quoted context omitted.
The past two companies I've worked for are forcing teams to move to OpenJDK and one was far more diligent about conducting audits for this than they were for GDPR.
I'm mostly ignoring it, myself. If it becomes a problem I'll switch.
Earlier quoted context omitted.
I'm mostly ignoring it, myself. If it becomes a problem I'll switch.
If it becomes a problem it will be too late to not pay Oracle huge fees/fines for using it against the license. Oracle is known for their license enforcement, it might even bankrupt your company.