Will Oracle Continue Funding Sun's Pet Java Projects?
When Oracle bought Sun, it got Java. If you make your living in Java development, that statement can make you cringe, smile, or shrug—depending on how well you think Sun has handled owning Java, and whether you think Oracle will do better or worse. You might even believe that the Java platform is too entrenched for this deal to have any real impact.
For its part, Oracle announced the acquisition with praise for Java ("the most important software Oracle has ever acquired") and a commitment to keep it vibrant ("continued innovation and investment in Java technology for the benefit of customers and the Java community"). And you don't have to take Oracle's word for it; the company's software products ran on the Java platform long before it decided to buy Sun.
So what's really going to change for the Java developer? Following the money may provide an answer. The Java platform has spawned countless development projects over the years with Sun providing the care and feeding—read: cash and staff—for hundreds of them. Sun spends billions of dollars in R&D every year, much of it going to Java-based innovation. (Java itself came out of the Green Project at Sun back in 1990.) The problem for Sun seems to be turning innovation into profits; being bought by Oracle may mean the end of R&D without ROI.
Oracle expects Sun to contribute over $1.5 billion to its operating profit in the first year, according to Oracle President Safra Catz. To fulfill that mandate, Oracle may start pulling staff and funding from Sun Java projects that don't immediately contribute to the bottom line or at least show promise of contributing in the near future.
Instead of worrying about Java itself, the types of questions Java developers really need to ponder are: What's the return on investment for JavaFX? Is it possible to monetize Project Looking Glass? What would the migration from Project GlassFish to Oracle WebLogic Server be like? And so on and so on for all those cool, interesting projects that aren't paying their own way. Soon, it may be the communities—alone—who keep them going.
Now—are you cringing, smiling, or shrugging?
0 TrackBacks
Listed below are links to blogs that reference this entry: Will Oracle Continue Funding Sun's Pet Java Projects?.
TrackBack URL for this entry: https://swarm.jupitermedia.com/mt-tb.cgi/7922
12 Comments
Leave a comment
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 |











My opinion is Oracle will not continue to support open source projects such as Glassfish and MySQL the way Sun did for the simple fact that they compete directly with their database and middleware (BEA) offerings. The $1.5 Billion will certainly come from eliminating redundant functions and groups, but I would also look for them to slash the R&D budgets including open source projects.
To answer your question, I am crying at the moment because we were prototyping Glassfish as a replacement for several of our Weblogic installs. We will take another look at Tomcat and JBoss though.
Glassfish and those things that are important to the Community will continue with or without Oracle...
MySQL existed before Sun bought them and will continue in some form or another long after Sun is gone... same with OpenSolaris... it's one of the good things about open source, it *survives*...
If you're worried about Glassfish, buy a support contract to lock in contractual obligation and get involved in the community more.
I am not worried about Glassfish.
Embedded Jetty + Spring and you never have to heard the word "Java EE" again.
There is no meat to this "article", well it's a blog posting more than anything. We are all wondering what Oracle is going to cut or continue to fund, but I think you are mistaken on Looking Glass. I don't believe Sun spends any money on this project anymore, hasn't for some time. The project that sort of spawned off from it is "Wonderland" which is an open source SecondLife like meeting environment. Maybe that's the one you meant?
Maybe it's about time to look to other languages. Oracle kills almost everything it touches.
I'm glad IBM didn't get it. No matter what you say about Oracle, there's at least some hope, and the ability to, as another blogger put it, to become involved in the community.
When Interwoven acquired Scriptics and scuttled TCL/TK, a similar thing happened; it went open source and was available to small dynamically growing companies (even if huge metanationals avoided TCL/TK after that).
IBM are a real killer of technology. They are also a killer of the social and economic landscape, holding tax-free lands in my home, Vermont, speculating on their value, and laying a few workers off each time the legislature makes noises about taking away some of their subsidies. (Go to the Holocaust Museum if you want to see more of IBM's real history.)
Well, you can look into using Apache Geronimo instead of Glassfish. Geronimo is the foundation for Websphere Community Edition.
Oracle cannot disenfranchise the core of Java - since it has already been open-sourced - and Oracle dropping it - will leave room for IBM to move in.
http://geronimo.apache.org/
The way Oracle does acquisitions is not all that cut and dry, I think. To be honest, it's a bit schizophrenic from an outside perspective. What is going to happen is that the Sun people are going to come in. Then for most of them there will be a period of silence where they will not really know what's going on, so no point asking them. In the meantime, there will be powerplays made higher up to see what stays (by who's going to be in charge of what) and what goes (who's leaving). Other people will leave because they won't like the culture. When they do finally make a decision, I think that it will be largely based on what they perceive to be ROI, competitive advantage and any potential liability (Oracle is super-paranoid about lawsuits, imho).
Open Source projects stay alive as long as there is a community. If somehow the community gets killed, another will rise up or get stronger to fill the gap. If you are a paying customer, Oracle will be looking to get money from you, esp. maintenance costs. Let your money talk; you want something, let them know.
Glassfish and Java has not to die. There will bee some new functions (cost) which have to return the investments Oracle had (it is capitalismus), but they are properties of the whole humane open and free science, the stone of the future if the communities believes it. Trust in Java for ever and we will maintain opportunities for the next generations.
>>Embedded Jetty + Spring and you never have to heard the word "Java EE" again.
Jetty looks good, but what does anyone need Spring for? Gosh if I force everyone to wire everything together with XML the application will be more modular!
Kind of like saying: if I force you to use Notepad to wire together a bunch of reflecto-beans you can't accidentally make your classes impossible to wire together with Notebad. I guess managers buy it, and all the Java Noobs (all 90% of them).
Do yourself a favor:
1. Dump Spring (waste of time)
2. Dump Hibernate (waste of time)
3. Dump JBoss (waste of time)
4. Dump Groovy (waste of time)
5. Dump Maven (waste of time)
Study core Java.
Brush up your C Skills, and get ready for multicore/GPU/et al.
Glassfish will be to WebLogic as
Geronimo will be to WebSphere
The "new economy" is remarkably like the old economy - it is all about the support/maintenance revenue. I'm sure they are planning on a 5%-10% roll up business that would support development of both WebLogic and GlassFish.
But if it falls below 1% and the support/maint revenue can't support the development, the axe will fall.
Hi,
Concerning:
"
Do yourself a favor:
1. Dump Spring (waste of time)
2. Dump Hibernate (waste of time)
3. Dump JBoss (waste of time)
4. Dump Groovy (waste of time)
5. Dump Maven (waste of time)
"
I totally agree. What happened to simple, powerfull, functionally rich client server applications using core Java (swing, sql classes, ...)? In stead managers choose costly, needlessy complex, functionally poor, costly to maintain browser applications????? Please managers get some insight into software design and architectures!!!!! You only need browser "applications" for websites targeted at the whole internet community not for business applications doaaah!!!
Best regards.