Everything You Need to Know About Oracle v. Google

onthebottom

Never Been Justly Banned
Jan 10, 2002
40,880
197
63
Hooterville
www.scubadiving.com
It will be fun to see how this plays out... Oracle tends to fight fights it can win, ask SAP......

OTB

Everything You Need to Know About Oracle v. Google

Oracle’s lawsuit against Google alleging that Android contains copyrighted code from Java has garnered a lot of attention lately. Here’s the situation so far: background on the issues, the salient discussions, what’s next, and some final commentary on how it all relates to Apple.

Background

Oracle has filed a lawsuit against Google (and recently amended it) alleging that parts of Google’s Android OS were directly copied from Java class libraries. The complaint also says that Google’s Android code contains APIs that are derivatives of copyrighted Java API packages. For a description of the original lawsuit, see the report by James Niccolai at IDG/Infoworld on 28 Oct 2010. Back in August, 2010, TMO published “Exploring Oracle’s Lawsuit Against Google,” which provides additional background, especially on the patent issues.

http://www.macobserver.com/tmo/article/everything_you_need_to_know_about_oracle_v._google/

.........


Lessons

Apple was not in great shape when Steve Jobs resumed control of the company in 1998. Even so, Mr. Jobs’s genius was to buy the company valuable time with the iMac, even if it did have the legacy Mac OS. The time Mr. Jobs bought the company with a Jonathan Ive designed iMac gave Apple engineers the precious time they needed to build Mac OS X and its development tools. Years later, in 2006, Apple had the tools and OS it needed to built the iPhone and iOS.

Today, companies are still being taken by surprise by the collective work and sweat-equity Apple put into Mac OS X, Cocoa, Xcode and iOS. That groundwork has enabled Apple to move forward at a much faster pace than competitors, an alarming pace, that, today, frightens both Apple’s competitors and tech writers in opposing camps.

Google, however, has hardly been fighting for its very life. The company is flush with cash. Google could have taken its time and developed a brand new mobile OS from scratch and license it any way it pleased. That might have taken five years. Partners in that OS would have full confidence in Google’s intellectual property. It appears, however, and this is just a guess, Google got anxious, overly eager to compete, didn’t invoke a lot of adult supervision via in-house attorneys, and rushed Android to market. In the end, that may be one reason why Eric Schmidt lost his job.
 
Or the real lesson is that you can't arbitrarily mix GPL and Apache licenced code, and put the in a public repository. That's a no-no. A big no-no.

Since Oracle bought Sun they've been trying to squeeze every nickel out of the Sun properties to the point where there's a decent chance they'll actually destroy and devalue every major Sun property. I can say that from direct experience. This is likely 'settlement bait' because Google was clearly caught in a licencing snafu.

(As far as Android being rushed to market, while not a Linuxey Linux, and being way too locked down and being too 'cloud centric' for me personally, under the GUI there's a pretty standard Linux with GNU Tools for embedded type systems. That is a very mature ecosystem, and GUIs mature rapidly when they lack complexity. Just poke around the 'update blob' for any android device.)
 

This is likely 'settlement bait' because Google was clearly caught in a licencing snafu.

Hmm... or not so caught. :) I did think it was weird that a company so acquainted with Open Source and Free Software licencing would would screw the pooch on that, but it is very easy to do...

And I stand by the notion that Oracle really is going to destroy or devalue every Sun property with their idiocy. They really are that bad.