Oracle Releases Java Development Kits for OS X as Work on Java SE 7 for Mac Continues
Back in late 2010, Apple announced that it would cease supporting Java for OS X, with Steve Jobs noting that Apple was always a version behind that being distributed by Sun/Oracle, which handled Java for all other platforms.
Context & Ripple Effects
This closes an 18-month handoff that began when Steve Jobs confirmed in his comments on Apple's Java discontinuation in October 2010 that Apple would stop maintaining its own lagging OS X port and leave Java to Sun/Oracle, which already shipped it everywhere else. A month later, Oracle and Apple formalized the arrangement with the OpenJDK project for Mac OS X, making Mac Java an open-source effort rather than a proprietary Apple deliverable.
The timing matters because Mac Java had just become a live security liability: two weeks earlier, Apple pushed out a Java update to remove the Flashback malware, underscoring what happens when the Mac's Java lags the rest of the ecosystem. Oracle shipping developer kits directly for OS X moves the version gap Jobs described from complaint to fix-in-progress, with Java SE 7 for Mac still under development.
First-order effects
- Mac developers gain Oracle-distributed Java Development Kits for OS X, ending their dependence on Apple's perpetually outdated builds and giving them a supported toolchain aligned with the rest of the Java world.
- Apple formally exits the Java maintainer role it inherited from its own ports, shifting responsibility for OS X Java updates and patches onto Oracle's release cycle.
Second-order effects
- Oracle's patch cadence now governs Java on the Mac, so security fixes arrive on Oracle's schedule rather than waiting on an Apple intermediary — the exact lag that left Mac users exposed during the Flashback episode.
- Other platform owners watching the handoff face pressure over their own bundled runtimes: if Apple won't fork Java, neither will they, and the economics of maintaining divergent ports weaken.
Third-order effects
- Cross-platform runtimes are consolidating around single upstream stewards with open-source projects like OpenJDK as the delivery vehicle, turning 'which vendor ships your language runtime' into 'which vendor you trust to ship it on time'.
- If Oracle sustains the stewardship, the Mac becomes just another first-class target in the Java ecosystem; if its attention drifts, platform owners may need to fund or fork runtimes themselves — the unresolved tension at the heart of this handoff.
The trend: Platform owners are exiting bespoke maintenance of cross-platform runtimes and ceding distribution to their upstream stewards, with OpenJDK emerging as the point where OS X Java converges with every other platform.