GraalVM is itself an open-source project that is licensed under the exact same license as OpenJDK [1]. Feel free to download it and build it yourself to be extra sure [2]. All the FUD around this stuff and Oracle is a bit comical. It's all... right there.
But it's not "all" there - some things are reserved for the enterprise edition. So if people start adopting it now in the hope that its remaining technical limitations will eventually be adressed, we might discover that the improvements only apply to the EE version, while the open source version is kept more or less where it is to encourage people to pay up.
This is true of every freemium project, from Gitlab to all the commercial Linux distros that sell support+prop extensions on the side. Given that GraalVM is a virtual machine there's strong incentive to push it far and wide. History suggests that VMs that are free and widely available survive and thrive (eg Java and .NET) while VMs that are expensive and/or difficult to redistribute die (eg Smalltalk). Oracle's incentives here, seeing as they want languages and library developers and ultimately application developers to actually deploy on GraalVM, is to go "far and wide" and not deep and narrow when it comes to their customers.
> its remaining technical limitations will eventually be adressed
It's not clear there are any technical limitations that separate CE and EE. Supposedly EE is faster but I don't think anybody has proven this with real benchmarks. All of this is clearly documented in https://www.graalvm.org/docs/faq/.
The native binary produced by Graal CE does not support runtime optimizations - that is EE only. As such, native binaries will start faster, but run slower.
This is true of many, many open source projects and has always been true. My first Linux was SuSE. Had to pay for it. The source was there but if you wanted Linux in an easy to use form, not so much. It was no big deal to pay because I knew it was funding the open source work. My first smartphone was an Android phone. I've paid for them, sometimes mostly to get software upgrades, because the pure open source builds were not as good. I buy a Mac even though I mostly use open source apps available for Linux and even though parts of macOS are themselves open source, because I want the extra proprietary features.
In the end most open source software I use is ultimately funded by better paid-for versions that people opt in to. The sky doesn't fall.
It's not like they did a hostile take over, sued Google for API, and dump their failing project to apache or anything. Or refused to give TCK to apache harmony project. Or hell even tons of anecdote of Oracle buying out services just to bilk people with more money until it rot. Or have a clause for anybody using Oracle DB cannot benchmark.
I feel people easily forget or act as if past actions/history isn't a metric to judge a company by. You can't predict the future with your feeling you can only do it via past data/actions. That or is it tribalism dogma that their bread and butter tech is being harshly criticize?
Google helped sink Sun with their Java fork and they could have bought Sun if they really cared about it.
The only company besides Oracle that cared about Sun assets was IBM, and I very much doubt they would not have done the same thing to Google. After all, Sun would have liked to do it if the bank account had any money left.
There was a limbo period where Sun, circa 2004-2007, had a defacto opposition to any consideration of any Java being open source until OpenJDK came along. I asked the question of senior figures in 2005 and they laughed it off. ONly to then be forced to adapt when Redhat et al wanted an FLOSS java. Thus OpenJDK got a licensing exception.
Ultimately the dev kit for android is a clean room implementation (submitters made legal commitments to that fact). The question pivots on how you feel abut the IP of the java language and the library interfaces being used by someone else.
With the caveat that Android is an incomplete implementation of Java libraries and JVM capabilities, thus not only it increased the bleeding on Sun's finances, to this day it is impossible to pick random Maven Central packages and be sure they actually run on Android.
A scenario that is only going to get worse as Java keeps improving.
I remember exactly what Sun Microsystem did it breached and been waving a carrot in front of Apache about TCK. What's stopping Oracle from giving TCK now? Also that's exactly not the whole truth you're presenting.
> Unfortunately, Sun breached the JSPA in 2006 by licensing the Java SE Compatibility Kit under terms inconsistent with its prior representations to ASF and its obligations under the JSPA, and incompatible with ASF's development of Apache Harmony. ASF urged Sun to honor its agreements, but after Sun persisted in its breach for a year, ASF withdrew from the JCP. At the time, Oracle supported ASF's position that Sun was in breach of the JSPA. But after acquiring Sun, Oracle adopted Sun's policy, disregarding the limits of the JSPA that formed the basis for ASF's participation in the JSP and acceptance of the various TCK licenses.
> Some people easily forget or act as if past actions/history aren't a metric, while others forget who actually did them in first place.
Choosing a video to support half a truth or a part of timeline doesn't mean anything.
> The heart of the issue is that Apache can't certify that its open source Java implementation—called Harmony—conforms with the Java language standards because Oracle refuses to supply the necessary test suites under a suitably open license. Oracle's position on the issue falls afoul of JCP policies, which stipulate that standards and other relevant materials must be freely redistributable and made available under terms that are conducive to enabling third-party open source implementations.
You're deflecting any and all of Oracle's action toward Google should have bought it and well Sun did it first. That's a terrible argument to counter my point of Oracle past actions being terrible toward open source. The "google should have bought Java" is such a hand wave especially when Google did a clean room implementation of Java and involve the issue of if API is copyrightable (https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google...).
Google did such a good job implementating Java that to this day there are still compatibility issues with standard Java, the library is incomplete and not all features of a standard JVM are available in ART.
They just broke Java the same way as Microsoft tried first, but since its the "Do no evil" company it gets a free pass.
Had it been other company and the Google support team would have another opinion.
I care about companies that care about Java, not those that fork the eco-system.
There are several companies playing by the rules, selling JVM implementations since the Sun days, none of them ever had issues either with Sun or Oracle.
Again the main point of my post was the FUD about Oracle and opensource is not base on nothing. Oracle's past actions toward open source shows this. You're welcome to disagree with counter argument, I would like to learn and be wrong if I am wrong (or missing something).
But I failed to see how your personal opinion on fork on java and ecosystem have to do with my original post on Oracle's FUD and past action against open source.
If none of your cases you've bought in this argument/debate is toward this topic then I think you're pushing a narrative and being dogmatic toward Java. I have no beef against the language but I am wary of Oracle. I'm merely refuting/adding toward the comment of the post I'm replying to.
Fair enough, although had IBM bought Sun instead, as no other company cared to do an offer, I doubt that they wouldn't have done exactly the same thing towards Google.
[1] https://www.graalvm.org/docs/faq/
[2] https://github.com/oracle/graal