The Case For Oracle

An anonymous reader writes "In a lucid writeup, InfoWorld's Neil McAllister takes a different angle on the Oracle-Google lawsuit, giving an explanation why Oracle was right to sue Google. McAllister argues that Google is splintering the Java platform, just like Microsoft was doing back in the 90s, and should be held up to the same standards. He further cites Google's Josh Bloch calling for Oracle to take a lead role in steering Java, concluding that Bloch maybe 'should have been more careful what he wished for.'"

Comments

Re:I think Google should solve this the easy way

[tomhudson]

Wouldnt hurt them one bit. You don't have to continue to enable someone who is suing you. While they're at it, maybe they can get Oracle to confess as to what they're really afraid of - a generalized implementation of map-reduce that would render Oracle database products redundant.

Oracle is killing Java. And that's a "GOOD THING!" Maybe people will be forced to learn a real programming language instead of Java's interpreted training wheels crap.

Re:What the hell is he talking about?

[tomhudson]

Android doesn't run Java.

I have to admit: as someone who eats, sleeps and breathes Java,

There's your problem - you're stuck with the modern equivalent of BASIC. It has caused +5 damage points.

Seriously, Java is a dead end and Oracle is doing us all a favor by making it politically correct to point out that:

1. It's a piece of shit, and ALWAYS has been;
2. It's performance sucks
3. It's implementations suck even more
4. It's frameworks just compound the problem
5. It's fugly-ugly
6. Swing doesn't
7. It's really an interpreted language masquerading as a "compiled" language
8. Java developers NEED training wheels because they can't do something as simple as manage memory

Obsolete! When's the last time you saw a Java applet? This was the technology that was supposed to change the web and make it interactive. It died! It was supposed to be on thin clients everywhere. It died there too. It's crap. Get over it and learn c - if you still can after the brain damage Java seems to inflict on "programmers".

Re:MOD PARENT UP PLEASE

[tomhudson]

... and every other language just happens to be dependent on? c. Aw. No c, no java. No c, no perl. No c, no python. No c, no php. No c, no Windows, linux, unix, bsd, osx.

You've already limited your target audience by using java. When's the last time you saw a java ("it's going to change the way we use the internet") applet. Java died on the web years ago, it's rarely used on the desktop for anything significant for most users, you could kill off openoffice tomorrow and do the world a favor (other odt-capable editors are much faster and less buggy because they're written in c).

If you wanted to work with the most PEOPLE possible, you'd avoid java. You can't use it without a license on smartphones (ask Oracle), whereas you can deploy flash apps (as one example of a crap language that actually lets you do something quick-and-dirty) on desktops, smartphones (except iOS crap), and game consoles.

Or you can write something in c and actually have something that people will use because it's a lot faster at runtime than java.

Java has never been a cross-platform implementation, and never will be if OraKILL has their say, which is okay - let them kill it completely and maybe something better will come along. The only advantage java had over c was a fairly complete set of (really crappy) graphic and (half decent) networking libraries that were relatively easy to use, and that advantage is disappearing.