Oi! You got a loicence for that Java, mate? More devs turn to OpenJDK to swerve Oracle fee Just 9 per cent of Java devs pay for a supported version of the Java Development Kit (JDK), according to a new survey – despite Oracle introducing a licence fee for the official Oracle JDK from April 2019. The survey by snyk, a company that specialises in tools to find vulnerabilities in code and open-source libraries, is …
"Use of Oracle's JDK has declined from 70 per cent in 2018 to 34 per cent today. "There is a 72 per cent swing from Oracle JDK to alternate OpenJDK providers"."
That decline is 100% the fault of Oracle's litigation first policy that's putting off developers who understandably fear getting snared in a Larry lawsuit. These days, Oracle's a legal firm with an IT department (and a declining one at that).
No, it was reimplemented, not ported. This was necessary in order to maintain reliability, maintainability, and performance.
The amount of code was not monumental, but it was significant. The reimplementation was performed by three engineers working for about 6 months (including QA).
"Remember when a lot of people said IDEs were a commodity and after Eclipse there was no need to develop another?"
It's still software -- Has there EVER been any such that SOMEONE didn't feel the need to design one that works "the right way" (i.e.: HIS way)?
"In Continuous Integration, Jenkins is the choice of 58 per cent of those surveyed, a huge lead over the second placed GitLab (6 per cent), while the three most popular code repositories are GitLab (35 per cent), GitHub (31 per cent) and BitBucket (25 per cent). It seems that JVM developers love GitLab more than the average developer, since GitHub is reckoned to have a bigger market share overall."
Um, where does TeamCity come? I believed (perhaps wrongly) that it ranked similarly to Jenkins? Since its also a Jetbrains product along with IntelliJ, I would expect a high usage given its interaction with IntelliJ which we know has seen a significant uptake.
if Oracle gets the SOCTUS to come down on their side in the API Copyright case against Google.
They will have rights to the API. The code behind it might be a cleanroom regen of the original SUN Java but the API will be their property.
An Oracle win could very well sound the death knell for all Java implimentations and products based on it.
I wish Oracle would just die quickly.
{A former Oracle DBA from a time before they got truly evil}
"I wish Oracle would just die quickly.
{A former Oracle DBA from a time before they got truly evil}"
This is only my view, but one of the very worst things ever to happen in the IT industry was the take over of open source-friendly Sun Microsystems by voracious (and it turns out thoroughly litigious too) Oracle.
Substitute all API terms with their ROT13 pair version, which does not breach the trademark. Writing a compiler to deal with legacy programming is trivial. For instance "java" becomes "wnin". "FileOpenReadWrite" becomes "SvyrBcraErnqJevgr". (You may need an IDE that helps with longer method names.)
IMHO java API ruling was wrong given that the API is never seen apart from java then is clearly part of the language and hence should come under the same rules as the language itself, i.e. the implementation should be protected but not the language itself.
I always wondered if the google/oracle case was setup
Of course, money from an existing resource is 'free', so it doesn't matter if that resource is decimated in the process. No incentive for Oracle not to squeeze the pips for juice.
In the mean time, we start with languages that compile to JVM, but aren't Java. Then we get a VM that isn't Java and the whole world moves away from Oracle. Kotlin, Dart and all the others are the bridge away from Java, and if something like Spring suddenly starts to support those other languages, devs will be happy to move.
In the mean time, we start with languages that compile to JVM, but aren't Java. Then we get a VM that isn't Java and the whole world moves away from Oracle
Unfortunately, a big attraction of JVM-targeted languages* is that they can use Java runtime libraries. The bare language is of limited use. If Oracle succeeds in establishing that its API is proprietary, then using library routines, even in a re-engineered version, is going to cost.
* Some, at least. Not sure about Scala.
Very true, but then you get efforts like Flutter and slowly the libs get replaced as well. Again, if Spring provide top level support, then the reasons to stick with Java are eroded.
It's hard to overstate the value of the Java libs - you can get Java to do just about anything thanks to the vast, well supported and consistent APIs they provide. But... nothing is forever and there is always an incentive to build a 'free(er)' version if there is someone attempting to gate-keep.
"In the mean time, we start with languages that compile to JVM, but aren't Java."
I don't wish to give Oracle ideas, but once they've got the Java APIs nailed down (which given the makeup of SCOTUS seems at least somewhat likely,) if they then follow that up with the bytecodes supported by the JVM, then anything else using the JVM is also in deep ... stuff.
"Of those who do pay for JDK support, which is around 9 per cent of the survey participants, a whopping 55 per cent get it from Oracle"
so.. 9% of 2000 developers, of which 55% pay Oracle.. which equates to 99 developers.
not sure that 4.9% paying for subscriptions corresponds with "whopping"
I'd have said that was "paltry"
check the post https://headcrashing.wordpress.com/2019/05/03/negotiations-failed-how-oracle-killed-java-ee/ about the 'negotiations' between Oracle & Eclipse about moving the javax.* classes over; Oracle only wanted Oracle or Oracle-approved JDKs to be permitted, which would have broken neutrality from Eclipse and might have jeopardized their non-profit status. Pretty obviously concerned about alternate suppliers such as IBM, Azul, etc.
The vote went completely against Oracle's proposal (theirs the only vote in favor), and the process requires unanimity so the only option was what will probably be labeled as "The Great Renaming". Any mods to javax.* now require renaming to avoid legal fireworks. EJB, JAX-RS, JPA will all have to change as well. Forklift upgrade coming.
With the shift to lighter frameworks like Spring, Oracle has successfully executed a footgun maneuver to alienate dev's from bothering with EE going forward.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
