Oracle Asks Apache To Rethink Java Committee Exit
CWmike writes "Oracle has asked the Apache Software Foundation to reconsider its decision to quit the Java SE/EE Executive Committee, and is also acknowledging the ASF's importance to Java's future. In a message released late Thursday, an Oracle executive made conciliatory gestures to Apache. At least for now, the ASF doesn't seem eager to rejoin the committee. 'Give us a reason why the ASF should reconsider other than "please,"' ASF president Jim Jagielski said in a Twitter post on Thursday. The Java Community Process is 'dead,' Jagielski said in a blog post, also on Thursday. 'All that remains is a zombie, walking the streets of the Java ecosystem, looking for brains.'"
Answer is still no.
'All that remains is a zombie, walking the streets of the Java ecosystem, looking for brains.'
Best quote ever. Hopefully, Oracle will get the clue and realize that you have play nice, even when you own the toys. Otherwise, you play alone.
Tequila: It's not just for breakfast anymore!
Oracle has the Midas Touch. Everything they touch turns into a profitable venture--I mean, if you don't count the ones that became completely useless as a result.
I'm sure even Larry and Company realize the importance of not angering every single one of your customers. If you drive absolutely everyone off your ubiquitous application platform, and no one wants to develop for it anymore, you don't get the opportunity to lock them into your products.
Granted, every single Sun customer I've talked to (including myself) is running away from Solaris and SPARC as fast as they can. SPARC hardware was great, the OS was good for an enterprisey Unix, but everyone's scared to death of Oracle quadrupling the price for next year's service contract and making a mess of support.
When it comes to hardware and Solaris, Oracle doesn't give a damn. What they do care about is their application platforms. Almost every CS program in the country is pumping out Java coders, many enterprisey applications have been written in Java/J2EE over the past 10 years, etc. Keeping developers interested in the Java/J2EE ecosystem is important long-term. Even if they don't want to support non-Oracle apps on Java, having a critical mass of Java coders means they have someone to maintain the disasters that they have to integrate like PeopleSoft, JD Edwards and other Oracle-developed products. If people stop writing for the platform, and Oracle doesn't at least maintain the illusion of an open standard, the platform goes away, as does the lock-in opportunity.
Although, I've never seen an acquiring company come down so hard on acquired customers before. Friends have been telling stories of their Oracle reps coming in and trying to double the price of their service contracts since the takeover. The entire secondary/hobbyist market for Solaris OS and SPARC hardware is toast because you can't even get firmware updates for hardware without Oracle service contracts. Maybe someone is realizing that they need to lighten up a little?? Nah...
Was it ever a good idea for Apache to participate in Java in the first place, knowing that the exact situation that they are complaining about today existed when they started, and has existed for the entire time they've been developing?
When we're finished with this one, we can think about Open Source projects and .NET .
Bruce
Bruce Perens.
Why else would he act like he truly believes that intelligence can be eaten?
...IN YOUR FACE! Sorry, but that is very on topic, and it is not very often that I can put in your face in all caps. Good Show ASF, good show indeed
The world is how you make it
You can always run your Java stuff from WebSphere.
I am becoming gerund, destroyer of verbs.
What's the difference between God and Larry Ellison? God doesn't think he's Larry Ellison.
Seriously, Oracle is an arrogant blood sucking company with its fangs in the fortune 500 markets and government organizations. Oracle DBAs demand a high price, and make sure you can't really escape the vendor lock.
Its a house of cards, really. Oracle on a single system doesn't scale much better (if even) than PostgreSQL on a single system. Oracle's cluster solution is nice, but the expense is crazy. Only fortune 500s and governments can waste that kind of money. I don't know of any "new" business that chooses Oracle.
They are trying to kill MySQL, and while I hope it dies a quick but painful death, PostgreSQL offers far more features and equivalent performance for free. What they are doing with Java is crazy. They don't even know what they have or how to capitalize on it. This isn't like MySQL where it is a direct competitor to their cash-cow, this is a key infrastructure piece that gives them a solid foot-hold in the industry. By suing Google and the actions they are taking now, it just tips the scales a bit more toward other languages and environments and weakens their position.
But, Larry is an idiot. Periodic flashes of brilliance, followed by long periods of narcissistic retardation disorder.
1. Serve the public trust
2. Protect the innocent
3. Uphold the law
4. (HIDDEN)
Times like these make me wish IBM had bought Sun instead. At least they're a services company, so they know how that ecosystem works, and their existing investment in Java would've been better for us all...
He who has no
Can someone thats more involved in Java development give us some insite into what this means for large Java projects that are already well underway? I've got some vested interest in a few software packages based on Java and am slightly concerned about their future.
I suspect it was neither good nor bad that Apache participated. One good outcome is a ton of AL-licensed core java code implementations, the copyrights of which are not owned by Oracle, and not under their control, easily integrated into most any OSS licensed language.
One bad outcome of the many worthwhile contributions to OpenJDK is that Oracle owns them, they are copyright assigned, and clearly Oracle is not being a good actor in adoption of that code. The whole GPLv2+classpath exception, overloaded with a bevy of patent threats and outright ownership of the code, leaves something to be desired for anyone who champions reuse.
If one were to create the Joe language tomorrow, syntactically different enough from Java and dodging Oracle's patent troves, it would be trivial to adopt all of those AL .jars and extend the language immediately. Not so with the GPLv2 OpenJDK code, forking to borrow the patents is highly suspect, and the code can never be brought up even to GPLv3 and its patent assertions without the owners/copyright holders direct consent.
I sort of view this as a massive failure to the freedom of software perpetrated by Oracle, but no less by the FSF itself, and share my sympathies with all the non-employee contributors to OpenJDK who agreed to copyright assignment. Trusting a foundation such as the FSF with your copyright is one thing, but entrusting it to a for-profit to protect your code for public reuse is a bone headed move.
Of course, all assurances were made by Sun prior to the ASF embarking on Harmony (there was no FoU considerations at that time, that was injected much later in flagrant violation of the JSPA), and prior to their contributing Tomcat to the ASF, that they were moving forwards. Staying with it prior to the Oracle acquisition was questionable, but staying long enough to determine that Sun had polluted Oracle's earlier positions *against Sun* seemed sensible enough. Now that all of this has played out, and the OSS universes of Java, OpenOffice and MySQL all implode, it seems like Apache chose just the right time to exit stage right.
Agreed that .NET is interesting, once all threats of RAND are completely stripped away. MS would be wise to revisit their patent pledges at this time and address their criticisms, it could score them some serious open source credibility in this environment. Especially if they were to contrast themselves to Oracle's JVM ownership. Perhaps the Outercurve Foundation will help to win some of the necessary assurances. Clearly much of the future of computing will exist on portable and multivendor/multi-OSS project VMs.
Fine Oracle, give Apache a JCK already !
Do that and they will have a reason to care about the future of Java.
In a society that believes in nothing, fear becomes the only agenda ~ Bill Durodié
If Mono were more mature and available on non-x86 hardware, I think .Net would be giving J2EE a serious run for the money over the next few months or a couple years.
Having coded for both, I can attest that .Net is a much cleaner library design, and far quicker to learn. Most importantly, it doesn't introduce drastic architectural changes with each dot update.
I do not fail; I succeed at finding out what does not work.
Google did not deliver a JVM. They pilfered the Java syntax to compile for a different machine. No sympathy.
I do not fail; I succeed at finding out what does not work.
Tomcat is an Apache based server
should probably be rethinking that move. Sure am glad I dropped Oracle for PostgreSQL about 7 years ago... And Solaris? not even worth mentioning...
well the only thing 'closed' about the GPL in comparison to BSD licences is the Free Lunch counter (unless you give those downstream in the foodchain the same lunch menu)
It does not appear that Java can be reimplemented because of U.S. software patents, but perhaps it could be forked.
As I understand it, Oracle(Sun) holds patents on Java. However, Oracle has placed the OpenJDK under (some version of) the GPL, granting free use of their patents to anyone working in that environment.
Apache chose not to work with the OpenJDK, but reimplemented the Java standard (in a "clean room" manner?) with the Dalvik virtual machine. Thus, the patent protection of the OpenJDK does not apply. IBM also has a JRE, and I assume that they have licensing on the Oracle patents for their implementation. Apache does not.
Google Android uses a portion of the Apache reimplementation, including Dalvik. Oracle would prefer that implementers of Android pay a license fee for Java Mobile Edition (ME). ME licensing for Android is most likely the reason that Apache has been spurned.
Should Android switch from Dalvik to OpenJDK, the problem goes away. This does not seem technically feasible, as Dalvik performs better with embedded (slower) systems. App store entries would also be in trouble without the LGPL.
Some argue that Oracle has a point in preserving Java purity, but, AFAIK, this is about ME licensing.
Bruno Borges said it the most succinctly...
"There is no point helping to write specifications that you aren't allowed to implement"
http://twitter.com/#!/brunoborges/status/13058930657730560
And Brian McCallister explained the full ramifications most clearly...
http://skife.org/java/jcp/2010/12/07/the-tck-trap.html
-- The Hoss Man
Lucy Asks Charlie Brown to Kick Football...Again
I work with Oracle quite a bit and they're pretty bad.
I worked with Sun and their reps for 20 years. They were clueless in a good way. They were just regular guys who would try to help you. Yeah, the company was dysfunctional, but they actually wanted to please you. I could call them weekends and get quotes for stuff, they'd go out of their way to write special deals and do whatever it takes to get the business at a price you could afford.
Oracle, by contrast has a good cop/bad cop approach. Its a way to screw you and charge you extra, but the sales rep keeps his hands clean.
Here's how it works. You get an an account rep, who acts like a regular guy, except he's not. He'll do stuff like "give you a free guy to help you" whose job it is to count licenses, servers, and applications secretly while "helping" you. He then passes that info back to the "inside sales rep". The inside rep (who will be a mystery to you) will say stuff like "Hey, I heard you got a new bigger server with a lot of new processors, is that right?". If you say "yes", he's got you. If you say "no", he'll keep calling until you admit it.
Meanwhile as you're planning on going live, they know the dates, they call the CIO and say "Dude, you're out of compliance. You go live, you owe us another $1M->a zillion dollars". Meanwhile, their licenses is so opaque that you have no idea what you owe them, and they count different licenses different ways, and even if you're a lawyer and a DBMS expert, you can't tell if you're in compliance or not.
The only way to deal with them is refuse their help, whenever the account rep comes in, accuse him of treating him poorly and throw him out. And when the inside sales rep calls you have to say things like "New server? I have no idea. I know the CIO was talking about getting rid of Oracle or something, but I'm not sure. What did you say you do for Oracle again? New application...ha, they never tell me anything. Did you know we already have an account rep here?"
That completely screws with the inside sales rep. Then when the account rep comes calling, say things like "Hey, my budget has been cut 10%, I need you to figure out a way to cut my maintenance bill by 10% or the CIO wants to throw you guys out. I know its crazy, but he's really mad at you". Then you never hear from the account rep again.
I've said this about Oracle for years: Nothing good comes from dealing with them. The only reason, the ONLY reason they stay in businesses is because they have software OEMs who will only support either MS SQL Server or Oracle as their RDBMS. Anybody who willingly gets into bed with Oracle is a fool. If you do get into bed with them, wear a condom.
And I'm not making up a f*ck*ng thing about any of this.
I think there's a general misunderstanding about what's going on here. So let me try to clear it up (and hope I succeed). As an independent company, Sun was essentially a failing concern. Pure and simple. When Oracle purchased Sun, they purchased them for the assets that Sun happened to own (either through in-house R&D or through either shrewd or lucky acquisition - choose your poison). They did *not* purchase Sun for business strategy. I can guarantee you on that. Thus, there is a new business strategy in place with respect to capitalizing on Sun's assets.
So by this reasoning, the alienation of the OO, MySQL and Java communities is by no means a random occurrence. Oracle's new business strategy with respect to these products is what is alienating these communities. If you want to pretend that Oracle and Ellison are not behind this, either you're simply in denial, you're heavily invested in Oracle technologies, or Oracle writes your paycheque (again, choose your poison).
oh ya, to all those who saw no harm in the Sun acquisition....
Of course the GPL doesn't. Contributors to OpenJDK give Oracle their copyrights, and Oracle does whatever Oracle damned well wishes.
And if you wish to become a clueful troll (which I trust you don't)...
http://lmgtfy.com/?q=the+tck+trap
yes, it was unnecessarily hard to buy stuff from Sun due to their crap sales process
It was?
1) Look at sun.com and browse their servers
2) Call Sun Rep. and ask for quote on chosen server and configuration
3) Pass quote to purchasing department and say 'Order 2 of these'
4) Open the boxes that arrived a week later and remove the new servers
Fearing forking is so pre spork and github.
I'm not sure if "open source" and "oracle" can fit in the same sentence. I mean, English is an emergent language, and it must acquire rules that reflect the current historical trends. I don't know the man, but he seems a raving hedonist.
I have to ask: what are the odds that somewhere in the PostgreSQL-XC development cycle, the pg devs will unknowingly implement the same technique(s) that Oracle used and patented, opening pgsql-xc to oracle lawsuits?
Whenever Free/Open-Source software tries to do something that some proprietary vendor has already done, seems to me there's a relatively high probability that *something* will end up being done the same way, because it's the obvious (or only) solution to the problem at hand.
MS will never have serious open source credibility. Their transparent, openly-acknowledged goal is to persuade people that use open source today that they should use proprietary Microsoft products tomorrow. The only reason they have made all these .NET-related patent promises is that they have judged that Mono is more likely to lead to businesses migrating from Linux to Windows than the other way round.
And don't you think that's likely? Most of the businesses that use UNIX or Unix-like servers today still use Windows on their desktop. If they switched from Java to C#, Microsoft would have a pretty good case to make that it would be sensible for them to standardise on a single platform for desktop and server. And the market share of open source platforms would plummet.
The .NET patent threat is overblown, yes. But that doesn't mean Mono isn't a trap.
But that doesn't mean Mono isn't a trap.
I don't disagree, my post suggested MS could remedy these legitimate criticisms now, and gain much of the open source credibility that Oracle has been so ready to throw away. In other words, they didn't do it right the first time, although perhaps they tried. Adopting the critiques of the JCP and Oracle, it would be easy for them to show "see, we wouldn't do that, and we are updating our patent promise thusly ... to ensure that we cannot".
You are just too good at explaining things! I have found this extremely useful. Please keep us posted
what exactly do you think i mean by '(unless you give those downstream in the foodchain the same lunch menu)' ?
basically you cannot restrict downstream any more than you are restricted. How exactly is this 'closed'??