Live data from Hacker News

The Supreme Court doesn't understand software

vox.com

51–60 of 64 posts

Re: The Supreme Court doesn't understand software

#51

Earlier quoted context omitted.

No, the constitution is quite clear on this point: To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries. It's clear from the historical record that this was about ensuring monetary compensation for invention, as knock-off devices were just as common then as they are now. In fact, public access to pat…

It doesn't particularly matter what the US constitution says on the matter anyway as patents were up and going long before it was written. The US constitution does not contain the idea behind patents, it contains a view of how people wanted to encapsulate existing ideas into a legal document for a new nation.

> patents were up and going long before it was written.. the US constitution does not contain the idea behind patents.

Yeah, I find it very interesting how the US constitution is often assumed the origin of patents, but the same people wouldn't assume it's the origin of other legal concepts, like a judicial system.

Re: The Supreme Court doesn't understand software

#52

Earlier quoted context omitted.

> You could say that anything at its root is simply a mathematical algorithm. Nonsense. A brick is not a mathematical algorithm. You can use mathematical algorithms to calculate things about bricks but that's not the same thing at all.

Hyperbole perhaps, but not nonsense. A photograph can be saved as a file on a computer. The file essentially just consists of instructions for displaying the photo. Does that mean photography === mathematical algorithms? Or yesterday there was a frontpage story about a guy who spent 13 years of his life building a (pretty cool) freeware game. I'm not arguing that he should be able to patent the mechanisms of the game…

> Hyperbole perhaps, but not nonsense.

It's definitely nonsense. Things with corporeal existence are clearly distinguishable from algorithms. It is unambiguously true that a brick is not an algorithm.

> A photograph can be saved as a file on a computer. The file essentially just consists of instructions for displaying the photo. Does that mean photography === mathematical algorithms?

Traditional photography is a chemical process. The shutter opens and the light causes a chemical reaction on the film. Digital photography is an electrical process. Light strikes the sensor causing electrical charges that can be measured and recorded. Both of those are physical processes. Neither of them is an algorithm, although the data either of them produce could be processed by algorithms (e.g. JPEG compression). Moreover, a camera as a product is the sort of thing you could patent. You can tell it isn't an algorithm because you can't load software into a general purpose computer and have the software cause the computer to be able to take photographs without a camera.

> I'm not arguing that he should be able to patent the mechanisms of the game, but not because it's just one big "mathematical algorithm". That's ridiculous; it's a work of art.

That's exactly why it's not patentable. For art you get a copyright, not a patent.

> To use the example from the article, any design must be described with a sequence of words. You can't patent a sequence of words, so all patents should be invalid.

This appears to be the source of the nonsense. You aren't distinguishing between the words (or algorithms) that describe a thing and the thing itself.

> To me, that's not much more of a stretch than saying that all software is simply a collection of mathematical algorithms. Perhaps literally true in a sense, but essentially meaningless.

All software is simply a collection of mathematical algorithms. That isn't meaningless, it's the reason it's impossible for any software to exist that you could load into a computer and cause it to be able to take photographs without a camera.

Re: The Supreme Court doesn't understand software

#53
post #34

Earlier quoted context omitted.

I fail to see how a program is not a mathematical algorithm.

Lets flip this around: The court considers mathematical algorithms abstract. Noting that it enables you to achieve the very practical utility of posting on this forum, is the software running your computer abstract? The obvious answer is that our definition of what is an algorithm and what is abstract differs from the court's.

The thing that allows you to post on this forum is the prior art computer hardware. The software only tells the hardware what you want it to do.

Moreover, your formulation is erroneous. Concrete things can do abstract things. The fact that a particular braking system can slow down a car does nothing to establish that "slow down a car" is not an abstract idea. It clearly is an abstract idea.

Re: The Supreme Court doesn't understand software

#54

Earlier quoted context omitted.

Hyperbole perhaps, but not nonsense. A photograph can be saved as a file on a computer. The file essentially just consists of instructions for displaying the photo. Does that mean photography === mathematical algorithms? Or yesterday there was a frontpage story about a guy who spent 13 years of his life building a (pretty cool) freeware game. I'm not arguing that he should be able to patent the mechanisms of the game…

> Hyperbole perhaps, but not nonsense. It's definitely nonsense. Things with corporeal existence are clearly distinguishable from algorithms. It is unambiguously true that a brick is not an algorithm. > A photograph can be saved as a file on a computer. The file essentially just consists of instructions for displaying the photo. Does that mean photography === mathematical algorithms? Traditional photography is a chem…

> > To use the example from the article, any design must be described with a sequence of words. You can't patent a sequence of words, so all patents should be invalid.

> This appears to be the source of the nonsense. You aren't distinguishing between the words (or algorithms) that describe a thing and the thing itself.

That's exactly my point. By saying that software isn't patentable because it is simply a collection of mathematical algorithms, you aren't distinguishing between the algorithms that describe the thing and the thing itself. Software is literally a collection of data and algorithms, yes, just like a digital photograph. (Although you could stretch further and define data as simply a single-purpose algorithm.) And legally a "collection of algorithms" cannot be patented. But in reality, much like the photograph, there is a great deal more to software than that; there is thought and creativity involved in "collecting" those algorithms. Saying software is a collection of algorithms is akin to saying a book is a collection of words. Literally true, but missing the bigger picture.

And yes, I understand the difference between patent and copyright. I was simply giving an example of something else - a digital photo - that is exactly like software: a collection of data and algorithms. Does that mean that exactly the same laws should apply to software as to digital photographs (and everything else that is simply a collection of data and math)? Of course not, because these things are fundamentally different, and are each more than the sum of their parts.

Re: The Supreme Court doesn't understand software

#55

Earlier quoted context omitted.

I see that it's a vox.com article. I'm betting it's a Timothy B Lee article. * checks * Yep, Timothy B Lee. He's the Rush Limbaugh of Hacker News, telling us exactly what we want to hear, and the incredibly bad things that are possible, where "possible" means "doesn't defy the laws of physics."

I hadn't thought about TBL that way before. Do you have other examples to help make that point? I'm curious...

http://www.washingtonpost.com/blogs/the-switch/wp/2014/02/23...

"The change represents a fundamental shift in power in the Internet economy that threatens to undermine the competitive market structure that have served Internet users so well for the past two decades"

http://www.washingtonpost.com/blogs/the-switch/wp/2013/12/06...

"But then, in the 1990s, a patent-friendly appeals court handed down a series of decisions that opened the door to patents on software. That triggered a wave of patenting that has drowned the technology industry in litigation."

http://www.forbes.com/sites/timothylee/2013/01/17/aaron-swar...

"If Ortiz thought Swartz only deserved to spend 6 months in jail, why did she charge him with crimes carrying a maximum penalty of 50 years? It’s a common way of gaining leverage during plea bargaining. Had Swartz chosen to plead not guilty, the offer of six months in jail would have evaporated. Upon conviction, prosecutors likely would have sought the maximum penalty available under the law. And while the judge would have been unlikely to sentence him to the full 50 years, it’s not hard to imagine him being sentenced to 10 years."

I get that all these things resonate deeply with hackers. But Rush Limbaugh's broadcasts resonate deeply with his audience, too.

Re: The Supreme Court doesn't understand software

#56

Earlier quoted context omitted.

> Hyperbole perhaps, but not nonsense. It's definitely nonsense. Things with corporeal existence are clearly distinguishable from algorithms. It is unambiguously true that a brick is not an algorithm. > A photograph can be saved as a file on a computer. The file essentially just consists of instructions for displaying the photo. Does that mean photography === mathematical algorithms? Traditional photography is a chem…

> > To use the example from the article, any design must be described with a sequence of words. You can't patent a sequence of words, so all patents should be invalid. > This appears to be the source of the nonsense. You aren't distinguishing between the words (or algorithms) that describe a thing and the thing itself. That's exactly my point. By saying that software isn't patentable because it is simply a collection…

> By saying that software isn't patentable because it is simply a collection of mathematical algorithms, you aren't distinguishing between the algorithms that describe the thing and the thing itself.

With software there is no separate thing. The software is the only thing. If there was a separate thing you could identify it.

You can clearly distinguish between, for example, a physics text describing how bricks are affected by gravity, and an actual brick that you can pick up in your hand. The physics text is not patentable completely regardless of how creative it is or how much work went into producing it. The brick may be patentable, e.g. if you make it out of some novel weather-resistant material.

The problem with software patents is that people making texts and not bricks are being accused of infringing patents.

> But in reality, much like the photograph, there is a great deal more to software than that; there is thought and creativity involved in "collecting" those algorithms.

Now you're talking about how the software is produced. The end product is still an algorithm. Are you suggesting that if I write a computer program that can produce other computer programs, the programs produced that way should not be able to infringe any patents because they were created deterministically without any human thought or creativity? Patents have no requirement of creativity. Again, the protection for creative works is copyright, and it applies to software as well as it does to photographs and books.

More to the point, analogizing software to several other things that are all indisputably not patentable is a very poor way of arguing that software should be patentable.

Re: The Supreme Court doesn't understand software

#57

Earlier quoted context omitted.

Lets flip this around: The court considers mathematical algorithms abstract. Noting that it enables you to achieve the very practical utility of posting on this forum, is the software running your computer abstract? The obvious answer is that our definition of what is an algorithm and what is abstract differs from the court's.

The thing that allows you to post on this forum is the prior art computer hardware. The software only tells the hardware what you want it to do. Moreover, your formulation is erroneous. Concrete things can do abstract things. The fact that a particular braking system can slow down a car does nothing to establish that "slow down a car" is not an abstract idea. It clearly is an abstract idea.

> The thing that allows you to post on this forum is the prior art computer hardware. The software only tells the hardware what you want it to do.

The software "only" tells the hardware what you want it do? That is the most important thing! Without software the hardware does absolutely squat.

Here's another way to think about this: imagine you invented the lever. The thing that allows you to move heavy objects you could not before, is the prior art of a log and a rock. The beam-and-fulcrum arrangement "only" tells the rock and log what to do.

> Moreover, your formulation is erroneous. Concrete things can do abstract things.

Non sequitur. Anything can be abstracted to an arbitrary degree. A very specific type of a screw with a very exact shape made of a very specific alloy can be abstractly defined as a "fastening component." That does not mean nothing is patentable.

> The fact that a particular braking system can slow down a car does nothing to establish that "slow down a car" is not an abstract idea. It clearly is an abstract idea.

Yes, but it's clearly not an abstract mathematical algorithm, which is what my parent post was questioning. Parent was wondering how software consisting of algorithms that are "abstract" can be patented. My point was precisely that the "abstract" that the court has in mind is very different from the "abstract" that we have in mind when talking about algorithms. "Slow down a car" is a different type of abstract from "E = MC^2", even though they are both abstract.

Re: The Supreme Court doesn't understand software

#58
post #26

Earlier quoted context omitted.

No, the constitution is quite clear on this point: To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries. It's clear from the historical record that this was about ensuring monetary compensation for invention, as knock-off devices were just as common then as they are now. In fact, public access to pat…

That exact quote disagrees with you and agrees with the parent comment, though. The purpose is "To promote the Progress of Science and useful Arts" . This is achieved by "securing for limited Times..the exclusive Right" . Monopoly and financial compensation are not the aim of constitutional patent law, merely the means to an end. Knock-off devices were common then as they are now, and in the absence of patent law, th…

They are a means to an end, absolutely. I wasn't try to imply that the constitution recognized Intellectual Property as a kind of property that people have some kind of inherent right to. In fact, I believe the opposite, but realize I may have implied that's what I believe, and that's what these responses are reacting to.

However, it's that end that's being examined here, not the means. My point was that by granting a limited-time monopoly on an invention, Congress can advance the state of "Science and useful Arts". It can be argued what is meant by "promote". As I noted, the historical context makes it pretty clear that it's meant as an incentive to invent, not necessarily public documentation of inventions, which really came later. This is exactly what is said in the article: "The idea behind patents is to create a financial incentive to promote innovation: patents ensure that the inventor of a new idea can get compensated for it, rather than seeing her idea immediately ripped off by copycats".

Regardless, what absolutely is missing from that clause in the constitution is any requirement at all that there be a public disclosure of the invention. That's what I was saying the constitution was clear on. Any assertion of public disclosure being the purpose is an interpolation, because the constitution has absolutely no requirement that that take place. All patents could be secretly filed away, for all it cares.

Re: The Supreme Court doesn't understand software

#59
post #51

Earlier quoted context omitted.

It doesn't particularly matter what the US constitution says on the matter anyway as patents were up and going long before it was written. The US constitution does not contain the idea behind patents, it contains a view of how people wanted to encapsulate existing ideas into a legal document for a new nation.

> patents were up and going long before it was written.. the US constitution does not contain the idea behind patents. Yeah, I find it very interesting how the US constitution is often assumed the origin of patents, but the same people wouldn't assume it's the origin of other legal concepts, like a judicial system.

No one assumed that, but it is a good distillation of what our legal system bases its notion of patents on. Common law is often used as the basis for precedent in the US, but usually not in cases when the constitution gives explicit goals and the means to achieve those goals, as it did with patents and copyright.

Re: The Supreme Court doesn't understand software

#60
post #27

Earlier quoted context omitted.

I think the sentence is pretty clear. It's using a limited-time monopoly in order to promote the progress of science and the useful arts. There is nothing here about promoting "disclosure of how to make things". That notion doesn't even make sense when it comes to "authors". What historical evidence is there that the "real purpose was to promote disclosure of how to make things"?

What exactly is the state of the Sciences and Useful Arts, except the accumulated knowledge of how things work, and how things are made?

"Progress" is also new inventions. There is no requirement for public disclosure anywhere in that clause. As I said, that came later.
Post reply on HN