6 ms·
The JDK would promptly be forked from the last-covered commit, presumably by a coalition of Amazon, Azul, IBM, Red Hat, SAP, Google, Microsoft (amazing times we
by jacques_chester 8y ago
The JDK would promptly be forked from the last-covered commit, presumably by a coalition of Amazon, Azul, IBM, Red Hat, SAP, Google, Microsoft (amazing times we live in) and Pivotal amongst others.
What enterprise customers want is certainty. Given the choice between "Java by Oracle" and "Basically still Java by Literally Every Other Enterprise Software Vendor", they will pick the latter in a heartbeat.
It would be chaotic and disruptive, but once the dust settled Oracle would (again) be holding the fizzle instead of the bang. That's how we got Jenkins out of Hudson, which has an unrivalled penetration of enterprise.
Disclosure: I work for Pivotal, we sponsor Spring and have a deep interest in the evolution of the OpenJDK. This is of course personal speculation.
- fiddlerwoaroof 8y agoWouldn't this run into the issues behind the Google-Oracle lawsuit around the Android runtime?
- jacques_chester 8y agoPossibly, though it would kill Oracle's Java business even more thoroughly. If their business strategy is more nuanced than "cut your own throat in the hope someone else's is behind it", then political jiggery-pokery like Java EE is probably about as far as they would want to go.