Apache Declares War On Oracle Over Java 428
jfruhlinger writes "The Apache Software Foundation, feeling increasingly marginalized as Oracle asserts its control over the Java platform, is fighting back, trying to rally fellow members of the Java Community Process to block the next version of the language if Oracle doesn't make it available under an open license amenable to Apache. Last month's Oracle-IBM pact was a blow against the ASF, which had worked with IBM in the past, but it appears that Apache isn't giving up the fight."
Unsurprising (Score:4, Interesting)
Everything I know about Oracle makes this absolutely unsurprising. It looks to me as though they're trying to cut out all the "competition" in order to ride out the recession.
Java is the new COBOL (Score:5, Interesting)
Java is the new COBOL.
During the declining years of cobol, I/we watched the participants fighting to increase their portion of the pie, regardless of how much it shrunk the pie.
Re:It's a trap (Score:5, Interesting)
The are a couple problems with this theory.
The EU demanded that Microsoft open several of their standards and protocols, or else. The EU can stop the sale of Microsoft products in the EU and levy more fines.
And Microsoft has made an open patent pledge.
http://www.microsoft.com/interop/principles/osspatentpledge.mspx [microsoft.com]
If they go back on that pledge and tell the EU they refuse to cooperate with their demands on interoperability, then the EU hammer drops again.
Microsoft isn't going to do that. It makes zero sense.
Re:its on s60 as well (Score:2, Interesting)
Re:Java is the new COBOL (Score:4, Interesting)
Re:Java is the new COBOL (Score:3, Interesting)
Let me put it this way, there are still tons of COBOL apps out in the wild. The last project I was on used a DB2 backend with a ton of COBOL stored procs. Imagine my surprise at having to learn enough COBOL to be dangerous in order to facilitate change to an application with an ASP.NET front end.
Re:It's a trap (Score:2, Interesting)
Re:Unsurprising (Score:5, Interesting)
Re:It's a trap (Score:3, Interesting)
As I just pointed out... that's exactly what they're doing by suing Android - an OS they had no hand in creating - for infringement on patents. Reading comprehension fail?
I find it difficult to see what grounds MSFT could sue a Mono user on, considering they blessed, implemented, and *released* a great deal of the source code that goes into Mono. It would be like suing your past self - "Well, one time I thought it would be cool to let other people have this stuff, so I released it to them all. But then I changed my mind, and now this court needs to take money from those people and give it to me."
It would seem that Microsoft's damages would be self-inflicted. And I'm not certain I see much legal basis for them rescinding their covenant(s) not to sue, as well. I can't imagine that "well we changed our mind" would be enough for a court to declare someone guilty of infringement, when MSFT has made a public statement that they wouldn't sue.
Blame Sun, not Oracle (Score:3, Interesting)
The policy of lying to Apache about Java was started by Sun, not Oracle.
Re:Unsurprising (Score:4, Interesting)
From a business point of view, it's genius.
I wouldn't go so far as to say genius, but certainly say it is simple forward planning. It is the simple result of: Where are we now, where do we want to be financially, in the marketplace and from a client base point of view in 3 years, what is the gap between where we are and where we want to be - and finally, how do we cover that gap.
In this case, it is clearly simple. We want to be in a stronger market position and to achieve that, we need to earn a higher market penetration. To do this we need to either buy, discredit or discontinue our competitor products. We have the money available to make a lot of purchases as well as the current market position to be able to drive a very large product towards the goals that will benefit us most.
The move from Apache is clearly a salvo from a company who can perceive this change and doesn't like where it is going as it will clearly impact THEIR goals negatively. If they can make enough of a stink/problem/thorn about it, then Oracle will have to realign their own thinking/planning to plan a slightly different path that avoids this big thorn/problem or account for the fallout and accept it as part of the bigger solution.
Re:Unsurprising (Score:2, Interesting)
I worked with a guy back in the 90s who was one of Oracle's first employees. He used to tell me how horrible it was to work there and how much of a complete asshole Larry Ellison was. Fortunately for him, being in at the beginning gave him a head start and he ended up making millions writing O'Reilly books covering Oracle Database topics.
Re:Unsurprising (Score:4, Interesting)
Not sure about the recission part, but they're definitely out to kill the competition. I fully expect the battle to get extremely bloody. Apple's sacrifice of their own Java implementation might well have been under duress, given this development.
It might be a good idea at this point to start looking at other languages. Since D is supposed to be "C# done right", it might be a language worth investigating. All you'd need is a portable virtual machine for it and you've a rival to Java that is (supposedly) superior to Java structurally. Tcl/Tk, Perl, Python and Ruby are already highly portable - although Perl largely shot itself in the foot with Perl 6 and Python did some serious self-inflicted damage with Python 3. Both should recover - after all, Python had just as much of a problem moving to Python 2 from the original form. Regardless, clearly there are potential competitors to Java if they can be mobilized.
If one or more of these can be embedded into multiple browsers (IE, Firefox, Chrome, Safari and Opera would be the obvious set and cover almost the entire browser market), Java would face some serious competition - at least at the browser end. Java applications and servlets would depend on whether the Java ABI was covered by the patents. If the ABI (in and of itself) is not IP-protected, then it would be possible to write virtual machines that run entirely differently than "native Java" VMs but which support Java objects. Bring GCJ up to Java 7 and have a backend to GCC that supports a portable virtual machine. You then have something that will handle existing Java bytecode and will allow a gradual weaking off of Java to any language GCC supports.
(Since IBM -is- permitted to contribute to GCC, this is another direction IBM might be looking into. Especially if they can get a Java bytecode frontend working for GCC. Java applications natively compiled to IBM's processors would be very appealing, especially if it didn't break any standards in the process.)
Re:Change this to an inflammatory title (Score:2, Interesting)
Yup. Sad that on slashdot I had scroll through a hundred stupid tin-foil-hat comments to find the only one worth anything. And of course I have no mod points....
Re:Oracle is Evil, C# Java (Score:3, Interesting)
Re:Oracle is Evil, C# Java (Score:3, Interesting)
Mono should be looked at like WINE, useful to port programs to, useful to get some programs to run, but shouldn't be your language of choice if you want to get cross-platform apps.
I write ObjectCloud [objectcloud.com] in C#, test on Mac with Mono, and deploy in on Ubuntu Linux with Mono. My experience with Mono is that it's fast and reliable, as long as you're sticking with the lower-level CLR APIs. IE, it's fine for servers that handle their own sockets; but it's not good for GUI applications.
Re:Oracle is Evil, C# Java (Score:4, Interesting)
GP: Mono is not portable
P: Yes it is! Here is a link to its license!
Being open source doesn't make something portable.
Absolutely correct. I have tried in vain to get Monodevelop working fully on OS X but to no avail. There are a bunch of linux specific dependencies required to have it work fully. You cannot build most of the templates on OS X let alone being able to edit a GUI inside of Monodevelop.
The current state of the OS X port is an absolute joke and show how much linux is trying to copy the "windows" way of doing things.
FFS, this is bad... (Score:4, Interesting)
All of Oracle's Java based software has components from Apache. IBM's Webshpere software has components from Apache. JBoss, Spring, Google's tools... All of them...
Re:Reminds me of some bad history (Score:4, Interesting)
This is high-stakes poker, with the winner claiming the cross-platform system as the prize. Yielding is getting dealt-in to the game.
If they play right, they can end up dumping Oracle, leaving Oracle in the dirt.
Or maybe the stakes are higher. Oracle and IBM are foes in many markets, and many of those markets now leverage Java. Whichever one is left controlling Java is also left controlling everything else.
To not yield (be dealt in), IBM would rapidly lose ground on its servlet engine (it would have no advance knowledge of how the specs are changing and no ability to ensure the specs benefit what they want to do). It could lose ground in the database arena (controlling the JDBC standard is valuable). And so on.
But if IBM gain control, by building a better Java on the sly and ensuring all the key systems use it at just the right time, then Oracle is in that boat. They now become the ones who lose control of servlets, JDBC, etc. That would wreck many of their key products.
This is a cut-throat business and these are two experts at throat-cutting rivals.
Re:Unsurprising (Score:5, Interesting)
Re:It's a trap (Score:3, Interesting)
Currently there seems to be a bit of a patent arms race between a few large compaines. Most notably Microsoft and Oracle. Both these companies have a set of patents relating to VMs etc that seem to be fundamental to how these platfoms work.
The sheer number and breadth of these patents makes is look unlikely that there is nothing in Microsoft's offerings that voilates an Oracle patent and vice versa so we've got a cold-war style Mutually-Assured-Destruction stand-off in place.
The possible problem facing smaller implementations of either Java or
Re:Unsurprising (Score:3, Interesting)
It's a bit more complicated that that really.
One of the reasons sun failed was that despite the fact that they came up with all the Java standards, the reference implementation and industry leader for most of them elsewhere. In this specific instance we're mostly talking about Tomcat as a servlet container which just destroyed anything Sun had until the very end. There was really no reason to pay either licensing or when they went open source support fees to Sun because their product implementations sucked.
Not that Oracle aren't a bunch of bastards(they are, always have been, and always will be), but Sun's relationship with the ASF was very much against their own interests, Oracle will very much be looking to put their implementation of the next JEE container as the go to standard so they can get some money out of it.
Re:Java is the new COBOL (Score:3, Interesting)
I was surprised, but I recently met a COBOL programmer younger than me. Not only is COBOL still being used, new products are being created with it.
Re:Unsurprising (Score:3, Interesting)
Re:Unsurprising (Score:5, Interesting)
Right a bunch of students with no work experience unilaterally turn down guaranteed full time positions with a established company in this economy.
Re:Unsurprising (Score:3, Interesting)
Why not, if they had other options? Given the choice between a job at Oracle or IBM, for example, I would be surprised if anyone took Oracle. If they're really at the top of their class, then they probably have a lot of options - I certainly did, although I chose to stay in academia for a bit and then work freelance so I never went through the whole 'proper job' thing.
I actually would have been quite interested in working on Solaris for Sun, but my contacts in the company put me off applying with their complaints about the poor working environment and bad management. I don't think I'd be interested in doing the same thing for Oracle. Mind you, one of my clients keeps talking about shipping a fork of OpenSolaris, so I might end up working on it after all...