The Supreme Court doesn't understand software
1–10 of 64 posts
Re: The Supreme Court doesn't understand software
#2I agree with the general idea of this piece, and I don't believe that software be patentable (or at least, software should be protected in a very narrow range of cases), but this argument doesn't hold up for me. For a person implementing a complex payroll system or a complicated user interface, the universal underlying mathematics are meaningless. Of all the time spent developing software, algorithm development is a tiny portion, much of which occurs in non-commercial environments anyway. It's comparable to the difference between the laws of physics and mechanical devices that operate as a consequence of those laws.
Re: The Supreme Court doesn't understand software
#3>> If a sequence of conventional mathematical operations isn't patentable, then no software should enjoy patent protection. I agree with the general idea of this piece, and I don't believe that software be patentable (or at least, software should be protected in a very narrow range of cases), but this argument doesn't hold up for me. For a person implementing a complex payroll system or a complicated user interface,…
Re: The Supreme Court doesn't understand software
#4The Knuth quotation in the article, used in support of this position, actually seems to invalidate it in my view. "Algorithms are exactly as basic to programmers as words are to writers." The key being words. The value in a piece of literature has little to do with the individual words it's made from, just as a piece of software is clearly vastly more than the sum of its algorithmic parts.
Footnote: I mean this for multiple dimensions of 'value', not simply some measure of economic worth. Information processing and transformation ability, for one.
Re: The Supreme Court doesn't understand software
#5>> If a sequence of conventional mathematical operations isn't patentable, then no software should enjoy patent protection. I agree with the general idea of this piece, and I don't believe that software be patentable (or at least, software should be protected in a very narrow range of cases), but this argument doesn't hold up for me. For a person implementing a complex payroll system or a complicated user interface,…
Re: The Supreme Court doesn't understand software
#6> In Thursday's ruling, the court rejected a patent that claimed the concept of using a computer to hedge against "counterparty risk" — the risk of making a bargain and then having the other guy not pay up. The Supreme Court complained that in the process described in the patent, "each step does no more than require a generic computer to perform generic computer functions." Such a generic patent, the court said, isn't eligible for patent protection. The problem is that this criticism can be leveled at literally any software patent. At root, software is nothing more than a sequence of mathematical operations.
The Supreme Court in Alice came to two conclusions:
1) The concept of intermediated settlement is a "fundamental economic practice" and is so ineligible for patent protection under the judicially-created exception Section 101 for "abstract ideas."
2) The "method" and "system" claims in Alice Corp.'s patent amounted to nothing more than describing how to implement intermediated settlement on a generic computer in a generic way, and did not render the otherwise unpatentable abstract idea patentable.
The purpose of (2) is to foreclose on clever drafting that tries to get around the "abstract idea" limitation by framing it in terms of a specific implementation on a computer. What Alice says is that implementing the idea in a generic computer doesn't turn an abstract idea into a concrete implementation. It does not say that an otherwise patentable idea is rendered unpatentable because the patent describes how to implement the idea in a generic computer.
Re: The Supreme Court doesn't understand software
#7Software is fundamentally no different from a physical mechanism. (Math is everything.) Software is just more tunable.
The focus should be on eliminating bad patents or patents fully. Please don't muddy the issue.
Re: The Supreme Court doesn't understand software
#8The author misses the gist of the Supreme Court's opinion in CLS Bank v. Alice: > In Thursday's ruling, the court rejected a patent that claimed the concept of using a computer to hedge against "counterparty risk" — the risk of making a bargain and then having the other guy not pay up. The Supreme Court complained that in the process described in the patent, "each step does no more than require a generic computer to…
Re: The Supreme Court doesn't understand software
#9The purpose of patents had nothing to do with compensation. It was already presumed that an inventor could sell an invention. The real purpose was to promote disclosure of how to make things. In other words to reveal what would otherwise be kept a trade secret. This fits well with the notion of "non-obvious to a person practiced in the art", which would preclude Amazons one-click. The idea was: Tell us how it's made in exchange for a monopoly for some number of years. Spreading knowledge is how you promote innovation.
Re: The Supreme Court doesn't understand software
#10The author misses the gist of the Supreme Court's opinion in CLS Bank v. Alice: > In Thursday's ruling, the court rejected a patent that claimed the concept of using a computer to hedge against "counterparty risk" — the risk of making a bargain and then having the other guy not pay up. The Supreme Court complained that in the process described in the patent, "each step does no more than require a generic computer to…
* 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."