Advanced

Initial Thoughts on Oracle vs Google Patent Lawsuit

Posted by KernelShepard on · 73 comments
Miguel de Icaza's web log
Mail this story
Print this story

Today Oracle sued Google over Java patents and copyrights that they claim Google's Android OS infringes. The lawsuit claims that Google knowingly infringed on those patents, and that the continued distribution of Google's Android is harming Oracle's Java Business.

Full Story

  Nav
» Read more about: Story Type: Editorial; Groups: Oracle, Sun

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (73)

Predictable Schadenfreude

24 earlier comments in the full thread.

@Sander,

Yes, I do. Especially when people sing its praises to the point that they believe it's a suitable replacement or C, C++, or Java. It's not.

Do you have to keep defending the indefensible faults of Python? It's getting quite old.

@jezuch,

You miss the point. It doesn't matter that it's a hardware issue - I KNOW that. Do you know when that hardware issue first surfaced? I do. It's how the phrase "1.0 + 1.0 = 1.999999999 for very large values of 1" got so popular in the IT world. Hint: 80387 co-processor. [url=http://books.google.com/books?id=pj0EAAAAMBAJ&pg=PA5&lpg=PA5&dq=80387 coprocessor bug&source=bl&ots=1969QiEaxp&sig=-P_N6cZpUSwJXKu2X0o67Qxb7VA&hl=en&ei=p_drTPGDB8H78AaQhfTLDA&sa=X&oi=book_result&ct=result&resnum=5&ved=0CCUQ6AEwBA#v=onepage&q=80387 coprocessor bug&f=false]http://books.google.com/books?id=pj0EAAAAMBAJ&pg=PA5&lpg=PA5...[/url]

What point have you missed? It doesn't MATTER that it's a hardware issue - the point is that the Python compiler doesn't correct for the KNOWN issue when other compilers and interpreters do - without any special handling.
> the Python compiler doesn't correct for the KNOWN issue when other compilers and interpreters do - without any special handling.

Actually, according to the link and quote I provided above, Python now does the same correction when displaying on the screen.
@bigg -

Patching the display is not a fix, because in data processing most data gets stored - not just displayed. If the underlying value is stored incorrectly, which is what this indicates, the data is bad.

>>> y = 2.0 - 3.1 >>> print y -1.1 >>> y -1.1000000000000001 >>>

NOT acceptable.

This "fix" is as dishonest as the doctored videotape that MS introduced in court during the anti-trust trial.

But you already knew that when you posted the link and quote.
> I do. It's how the phrase "1.0 + 1.0 = 1.999999999 for very large values of 1" got so popular in the IT world. Hint: 80387 co-processor.

Then you don't know. The problem is inherent in floating point arithmetic, which depends on storing values in logarithmic format. As such, it predates the 80387 by quite a bit. Any language which uses floating point arithmetic will have the problem, whether you can see it or not.
Hello, BigNum, BigInt, and BigRat.
@jdixon - then you don't know. There was no such bug with the 80287 math co-processor - meaning the problem is NOT inherent in Floating Point Arithmetic.

When Intel first released the Pentium, it didn't think the issue was a real problem, but "fixed" it anyways (probably due to all the bad publicity and falling share price.) First in 1994 and then in 1996.

If it was truly a problem with Floating Point Arithmetic, as you assert, then the problem would have appeared with the 287 co-processor and never have been fixed in later processors.
> Any language which uses floating point arithmetic will have the problem, whether you can see it or not.

Obviously not, so it looks like we are in fact beating a dead horse.
> Obviously not, so it looks like we are in fact beating a dead horse.

Bigg, the conversion from integer format to logarithmic format and back is always inexact. This has been known since the days the computations were done by people using logarithmic tables, long before computers as we know them existed.
> Bigg, the conversion from integer format to logarithmic format and back is always inexact. This has been known since the days the computations were done by people using logarithmic tables, long before computers as we know them existed.

I agree, I was actually saying that Darren will never want to see that because he doesn't like Python.

I stay away from Perl because of the syntax, but this is an interesting example:

#!/usr/local/bin/perl $b = 0.725/2; printf "0.725/2 is %.30gn", $_ for $b;

Upon running this program, what do you know, I got the following output: 0.725/2 is 0.36249999999999999

OMFG!!! Perl can't do arithmetic correctly!!! It's not a real language!!!

In Python, with a more, shall we say, reasonable syntax, I get

>>> 0.725/2 0.36249999999999999
Oh, and in case anyone should want to read about floating point numbers in Perl, here is a pretty well written one:

http://answers.oreilly.com/topic/415-how-to-round-floating-p...

Note especially:

Quoting:Whether visible or not, rounding of some sort is virtually unavoidable when working with floating-point numbers. Carefully defined standards (namely, IEEE 754, the standard for binary floating-point arithmetic) coupled with reasonable defaults within Perl often manage to eliminate or at least hide these round-off errors.


Which, of course, is exactly what Python does.

So now let's see what Darren had to say about Python's fix:

Quoting:@bigg -

Patching the display is not a fix, because in data processing most data gets stored - not just displayed. If the underlying value is stored incorrectly, which is what this indicates, the data is bad.

>>> y = 2.0 - 3.1 >>> print y -1.1 >>> y -1.1000000000000001 >>>

NOT acceptable.

This "fix" is as dishonest as the doctored videotape that MS introduced in court during the anti-trust trial.

But you already knew that when you posted the link and quote.
> I agree, I was actually saying...

OK. I misunderstood. I apologize.
Quoting:You miss the point. It doesn't matter that it's a hardware issue - I KNOW that. Do you know when that hardware issue first surfaced? I do. It's how the phrase "1.0 + 1.0 = 1.999999999 for very large values of 1" got so popular in the IT world. Hint: 80387 co-processor.


That's only a proof that you still don't get it. We're not talking about a hardware bug. We're talking about a precisely, deliberately crafted standard. Crafted by people much, much smarter than you or me.

I've got a surprise for you: 3.1 does NOT have an exact floating point representation.

Python 2.6.6rc1+ (r266rc1:83691, Aug 5 2010, 17:07:04) [GCC 4.4.5 20100728 (prerelease)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> 3.1 3.1000000000000001

Python is just honest with you.
> Python is just honest with you.

Precisely. Darren has just provided a case study in why hiding things is the wrong strategy. He has apparently been using Perl for years, and didn't know anything about the inexact nature of floating point arithmetic, because Perl always gave the "right" answer.
Quoting:Come on, even C gets it right:


Probably, everyone is already aware, but this noob just found out:

#include < stdio.h > int main(){ float a = 2.0, b = 3.9; printf("%10.30fn", a - b ); }

gives:

-1.900000095367431640625000000000

which clearly shows C-float is more off than Python, and worse, like bigg just stated, is hiding it (if one doesn't set precision). Come on, even a cheap TI83 is more precise than this!

Which is why, if I want to do math, I use a calculator designed to do math (TI89, I think it has something like "arbitrary precision" because it provides the exact answer to 2^2000 without rounding, and such).

Reminds me of 'right tool for the job'.
@hans: If you define a to be double rather than float, you'll get the same answer as Python. The greater the precision, the slower your program will run, so for serious number crunching double precision is usually sufficient. (And if you do GPU computing with CUDA, you want to use single precision if at all possible, as double precision on my older card is 5-10x slower than single precision.)
> Which is why, if I want to do math, I use a calculator designed to do math

One would have to use something like GNU MP (I think has bindings for python/perl...) or Java's BigInteger/BigDecimal for arbitrary precision arithmetic.
Yes, but those are slower. I have only used arbitrary precision libraries when dealing with money (don't want any chance of rounding errors) and when dealing with IPv6 (128-bit, which converts nicely to decimal but is often too big. Floats are only 32-bit and doubles usually 64-bit).
Quoting:when dealing with money (don't want any chance of rounding errors


I'm not familiar with the requirements of banking software, but isn't fixed-point arithmetic [usually?] good enough for that? Or do you really need to store those thousandths of a cent?
@jezuch: Sometimes the amounts can get big enough that fixed-point arithmetic doesn't work. In 32-bit you only get a range of +/- 21 million with two decimal places. If you want four decimal places (i.e. when computing interest) you only get a range of +/- 210 thousand. Hardly enough for a mortgage. Using 64-bits is much better. You get +/- 9.2 trillion with four decimal places. But not all platforms have support for 64-bit integers yet.

PHP is one such platform. Whenever I need to deal with monetary values in PHP, I use the BCMath extension.

Poor Miguel: Still dreaming to work for Microsoft

9 earlier comments in the full thread.

> So tell me, how many software patents did / does Bell labs have on C?

At that time, software was generally (and correctly, IMO) considered not to be patentable.
That was the point I tried to make:

Bell Labs was less owner of C than Oracle of Java, because one could use C without paying patent licenses to Bell Labs. Though I'm not sure because I wasn't born back then, but I think that's the difference.
> C was based on B ... whatever happened to A?

http://en.wikipedia.org/wiki/BCPL The design, and philosophy, of BCPL strongly influenced B, which in turn influenced C
Interestingly, the Microsoft CP allows anyone to extend .NET/C#, but the JCP does not (hence the lawsuit against Google over Dalvik). Miguel is right that .NET is more free than Java. That doesn't mean it's 100% safe from lawsuits, obviously, but it does counter what a lot of people who have been vocally against Mono have been arguing for years.

Jeremy Allison and a number of other people argued that Miguel should have taken Java and extended it to his needs instead of cloning .NET. Well, now we see why it was a very good thing that Miguel did not do so.
So is it safe to say Java is now officially dead? Looks like Microsoft has won again.
Quoting:but it does counter what a lot of people who have been vocally against Mono have been arguing for years.


Depends on who you're asking:

At the very same time, it doesn't counter, but confirm the opinion to stay away from patented proprietary frameworks, like Java and .NET.

Consider the case people warn you for crocodiles, and you are bitten by a snake . Pointing out the people who warned you for crocodiles were wrong as it's now officialy proven snakes are more dangerous, is not going to create a shield against crocodiles. To be safe from crocodiles and snakes, the best remedy is to stay away from them.
> stay away from patented proprietary frameworks

Unfortunately that is not likely to be enough. Even Fortran, which showed up in the 1950's, is at risk of patent attacks. As the language evolves and new features are added, there is the possibility that any specific implementation will violate some patents. Maybe COBOL is sufficiently stale that it doesn't matter, but I don't see the world giving up .NET and Java to move to COBOL.
So we're back to "The US patent system is broken to the point of absurdity"
TC, it's not just the patent system. The majority of the US legal system is broken to the point of absurdity. The cynic in me would opine that's what you can expect when you let lawyers write the laws, but I'll not expound further for fear of TOS violations.
> So we're back to "The US patent system is broken to the point of absurdity"

It seems we get there a lot.

> The cynic in me would opine that's what you can expect when you let lawyers write the laws

I would argue that this is what happens when you have an issue that puts most voters to sleep combined with a lot of money on only one side.
bigg: Yeah, forgot to note any C-software might just as easily 'step' on patents. Bummer.

So the 'language' C is more free than .NET (because it's less "owned"), and .NET may be more free then Java, but in the end it doesn't matter because you will step on a patent-mine anyhow.

TC: Not only in the US. The countries with absurd laws recently cooperated to force their absurdities upon the countries with same IP-regimes too, so soon this will be a worldwide problem. Then, it will be less obvious to notice how absurd it is.

I see it like this: If the whole world was like Angola, nobody would notice how full of mines that country is.

The one who invents a patent-mineguzzler http://www.google.com/imgres?imgurl=http://www.nolandmines.c... earns a patent, in my opinion.
> The one who invents a patent-mineguzzle

Patent the business "process" of patenting obvious software practices (or buying up the rights to existing same) and suing anyone who might even conceivably violate them. I doubt it's been done, and it's not like prior art is any barrier.
@hans,

I'm not so worried about patents as I am about copyrights - patents have a very limited lifespan compared to the ever-extending lifespan of copyrights. And in case you haven't noticed, copyright infringement has become easier and easier to demonstrate (see "non-literal copying") such that you can't build a structure that looks like another building without the original building designer's permission.

I think the biggest reason you haven't seen much action, regarding copyrights and patents, in the courts from Bell Labs is that until 1983, AT&T (Bell Labs parent) was forbidden, under terms of the "1956 Consent Decree", from selling computer IP, such as C, or UNIX, as "products".

http://www.technologyforall.com/TechForAll/legalHistory.html
I'd have to read the part of "non literal copying".

But here's why I'd disagree:

You can write a book, and publish it, sell it, and if you've written it yourself, you can almost be certain it doesn't infringe on existing copyright. However, if you write a program, publish it and sell it, you can almost be certain it infringes patents.

So, in my opinion, patents do stifle creating new programs, while copyright doesn't stifle writing new books.
Books, music, and art all borrown from each other. Concepts, ideas, images, techniques, composition, phrases, riffs, colors, etc....I don't see why software should be any different. Just different ways of doing similar things.
But if I write a story about a girl wizard named Parry Hotter, who has a 3/4-inch bolt on her forehead, and it is not obviously some kind of parody or satire (or adult... whatever), can J. K. Rowling's legal reps come after me? Yes.

Will they come after me? Only if it goes into a second printing, probably.
First printing most likely. The Rowling estate is quite vigorous in defending the Harry Potter brand.
Straight from the horse's mouth: http://www.copyright.gov/help/faq/faq-protect.html#what_prot...

The second to last FAQ is particularly troubling: Does copyright protect architecture? Yes. Architectural works became subject to copyright protection on December 1, 1990. The copyright law defines “architectural work” as “the design of a building embodied in any tangible medium of expression, including a building, architectural plans, or drawings.” Copyright protection extends to any architectural work created on or after December 1, 1990. Also, any architectural works that were unconstructed and embodied in unpublished plans or drawings on that date and were constructed by December 31, 2002, are eligible for protection. Architectural designs embodied in buildings constructed prior to December 1, 1990, are not eligible for copyright protection. See Circular 41, Copyright Claims in Architectural Works

Copyright protection for "non-literal elements" is a well-established principle for all copyrightable work - not just something that SCO dreamed up recently. This is why J.K. Rowling prevailed in her lawsuit against the Russians who changed the names & places, but kept the general plot.

But regarding software specifically, here's a bit more info that explains the concerns with copyright (and why I feel that the ever-extending nature of copyrights is more dangerous than patents): http://www.theiplawblog.com/archives/-copyright-law-is-that-...

(Specifically, the 4th and 5th paragraphs are germane to the topic of protection of "non-literal" elements.)
Come on, if you write a child book from scratch and make it up yourself, there's about 0.00000000000000 chance (except when using Python) you will be sued by J.K. Rowling, because the chances of "accidental copyright collision" is about "the same float". So the risk of your inspiration infringing on current IP is negligable.

With patents, such clearly is not the case.

I agree copyright extension may be dangerous, but it's no hindrance to publishing and selling ones own inspiration. The patent system is though.

And let me ask you something: If you write a piece of software, copyright it, and then I reverse engineer it, recompile and sell it, should it all the suddenly not be copyright infringement?

Because that's probably the reason architectural works are subject to copyright. I once worked at a company which designed plastic parts, and it's always dissatisfying if you develop something (meaning lots of efforts, far beyond researching and designing only!) and then somebody else 'measures' your part and starts selling it without paying for the development you did.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post