I’d like to think of myself as an informed prognosticator having worked for Sun for almost 9 years; but this is prognostication nonetheless. I missed my chance to say what I thought of an IBM acquisition but I’ll start by saying – I think I preferred it – it probably would’ve been a better outcome for the things I care about.
The things I care about are the people I know who still work for Sun, the Java ecosystem, and many of Sun’s Open Source projects that I directly or indirectly benefit from – specifically MySQL (this post will live in MySQL), OpenJDK and OpenOffice.
It still seems like a strange merger – sure, Sun and Oracle have a huge shared installed based – Sun Servers + Solaris + BEA + Oracle DBMS was the killer enterprise stack for a decade – that alone gives Oracle a vice-like grip on existing customers; but that’s about the past – not the future. I think someone did the analysis and realized it’s a marginally positive move – so I don’t think this is the big technology vision realized that Oracle are trying to promote.
I’m sure a lot of people at Sun and customers of Sun are glad the uncertainty has come to an end but unfortunately it hasn’t. I’m guessing that it will take until the end of the year before Oracle tells the world what they’re keeping and what they’re dropping. FWIW – here’s my informed guess :
Storage / Servers – the press-briefing made the merger sound like it was all about the hardware (servers and storage). I just don’t see Oracle as a hardware company and they have more to loose than gain by pissing HP off. I wouldn’t be at all surprised if some or all the hardware got sold off to HP, Fujitsu, etc. And I think Oracle could probably recover $3.5-4 bn of their $5bn outlay by doing so.
NetBeans – I’m not changing my mind – it’s done for. Oracle has two Java IDEs already – they don’t need a third. Oracle will pick up some great tools developers to write a migration tool but that’s about it.
OpenOffice – Oracle doesn’t like M$ but I doubt they can find a fiscally rational reason to carry the torch for Open Source and at the end of the day Oracle are doing this because it makes financial sense. I think Oracle will expect “the community” to pick up the slack.
Solaris – I think they’ll milk the legacy installed base (which is huge) but the innovation won’t continue. I think there’s an interesting opportunity for Oracle to manage the migration of the last of the Solaris holdouts to Linux. They could do this by GPLing Solaris and moving some of the Solaris features to Linux; or more likely to an Oracle proprietary OS built on Linux.
Middleware – Oracle have everything Sun has – and Oracle are by and large market leaders with large market and revenue share. Sun have one or two products that might survive and certainly some components. Oracle inherit a commitment to continue to produce the Java EE RI (and others) so Glassfish *might* survive – but Oracle have demonstrated that they don’t have appetite to maintain many products in the same market (see how quickly OC4J got killed after the BEA acquisition ?)
MySQL – I think Oracle will continue to do what Sun did somewhat accidentally – namely slowly kill it off.
Java – I’m confident that Oracle won’t fix the JCP and won’t sacrifice control for the good of the ecosystem. I also think the JCP will become a battlefield for IBM and Oracle and we’ll all be the worse for it.
OpenJDK – no-body needs two JDK’s to maintain – I think Oracle would have to move some of the monitoring / diagnostics from JRockit into a proprietary OpenJDK-based platform. JRockit has a small market share but some nice features for enterprise customers.
Cloud – not that there’s much there there but I don’t expect to see Larry eating his words.
Virtualization – I don’t really understand Oracle’s virtualization strategy other than the feeling that Larry Ellison is unlikely to entertain anything that looks like it might actually save customers money on licenses.
* NetBeans : IMHO, NetBeans is still going to flourish while existing community is big enough while JDeveloper mindshare is very little.
I imagine JDeveloper+NetBeans to merge (all IDEs are Swing-based), while NetBeans being the company-neutral stub and JDeveloper being proposed as NetBeans+Oracle stuff (like Oracle ADF – Oracle Application Development Framework).
* OpenOffice : Oracle may still let live OpenOffice to fight indirectly Microsoft.
But the Oracle business view may bring the opportunity to start a OpenOffice foundation to share development costs.
* Glassfish : Larry may be keen to keep Glassfish for the following reasons
- Oracle may keep Glassfish to fight RedHat/JBoss.
- as part of the JEE JSR expert group, Oracle still have to release a RI.
- Glassfish v3 is going to be modular,
- WebLogic and Glassfish already share some parts, like WS stack
And beyond that…
If one want to do propective, one has to take into account expected SUN released during that period, because those releases are going to impact Oracle decisions. I expect the following releases during the next months:
- NetBeans 6.7
- Glassfish v3
- JWebPane
- SSD disk (to be used jointly with Oracle database)
- OpenOffice 3.1 et 3.2
The coming period (until the end of 2009, little will change inside SUN) may give time to Oracle to see :
(1) they have an open source Java software stack that could compete with RedHat
(2) with the ex-SUN hardware, they can position themselves more than RedHat, and close to Apple (mastering both the soft/hardware stacks, on the server-side), so Oracle could compete with IBM
(3) the long awaited JWebPane could give a boost to Java on client-side, mixing Java+HTML strengths, so Oracle may want to fight Adobe
(4) OpenOffice could be leveraged by Larry in order to fight Microsoft business incomes, Microsoft being one oldest Oracle ennemy.
So, each way could give new fight (good for Larry ego) and/or new business opportunity.
Got to agree with Rich on Netbeans. It’s dead. Oracle has already stated on many occasions that JDeveloper is their strategic IDE. When they acquired BEA, their workshop IDE was the first thing to go. They threw bits and pieces of it into their give away Eclipse pack, but the product died quickly and violently.
True, Workshop never enjoyed a community like Netbeans has, but that won’t save it.
@Mitch indeed – and remember 2-3 years ago – Schwartz announced that Oracle we’re moving to Net Beans only to be followed by by an Oracle press release stating that Oracle had no intention of moving to Net Beans. Pure comedy.
- Rich