Some thoughts on software patents and the Supreme Court

Register or Login to like
Register or Login to like

When the Supreme Court heard oral argument in the Bilski case a few weeks ago, I was fortunate enough to be in attendance at their courtroom in Washington, D.C. I'd previously worked on a brief for Red Hat arguing that the Court should address the harm that software patents cause to innovation. Even so, I had my doubts as to whether the Court would fully appreciate the serious problem of software patents, and recognized that it might limit its attention to business method patents and try to avoid the software patents issue.

After hearing the argument, I felt confident that some of the problems with software patents have not escaped the Court's notice. Several justices' questions suggested a high degree of skepticism regarding the value of overly abstract patents. The justices hammered on Michael Jakes, counsel representing Bilski, with questions on whether he thought a variety of abstract ideas could be patented, including a method for teaching antitrust law, using actuarial tables in the insurance business, an alphabet used to form words, and training horses. Mr. Jakes thought all such things were patentable, but the justices' body language indicated they did not at all agree. I actually felt a little sorry for Mr. Jakes.

In several questions, the justices appeared to recognize that it simply isn't always the case that patents foster innovation. Justice Breyer, for one, noted that patents raise prices and can slow the pace of progress. Justice Sotomayor observed that patents limit the free flow of information by requiring licensing. Similarly, Justice Scalia noted that patents block the public from using ideas.

It was particularly encouraging to hear the justices questioning Malcolm Stewart, representing the PTO, on his position that programming a computer with new software caused it to be a new machine. Chief Justice Roberts specifically challenged this view, comparing simply adding a computer to a process to adding a typewriter to type something out. Justice Stevens also took issue with Mr. Stewart on this point, saying the computer was not a new computer, but an old computer with a new program. Justice Breyer seemed to agree when he expressed doubt that just having a set of instructions for a computer could make a new machine.

Of course, none of the justices' remarks are equivalent to an opinion of the Court, and its possible that the direction of the Court's thinking could turn in other directions before an opinion is issued. It seems clear, though, that certain fundamental problems with business method and software patents are on the Court's radar. While there are still many people who mistakenly believe that patents always serve innovation, the Supreme Court does not seem inclined to accept such a view without qualification. That's encouraging.

Rob Tiller is vice president and assistant general counsel for Red Hat, where he manages patent, trademark, and copyright matters. He is a frequent speaker and writer on open source legal issues. Before coming to Red Hat, he was a partner with the law firm of Helms, Mulliss & Wicker, PLLC, where he specialized in commercial and IP litigation.


In this 30 minute mp3 interview, John Carmack from id Software explains exactly this problem, and how it hurts everybody doing creative things.

We'll give it a listen.

As far as you know, would it be OK to re-post this as it's own, stand alone post?



It truly is an interesting interview, as id Software have released all its games as Open Source for the past 15 years, and John's take and view on software patents are just so right and well put.

Both the interviewer and John have a very sane take on software patents, so I am sure they wouldn't mind spreading the word. But I am not the copyright holder.

The MP3 comes from

and in that, you will need to fast forward to ~65 minutes. The one I linked to have I cropped just the interview out using mp3splt, so no re-encoding.

If you need to get in contact with John Carmack, you can write to him at johnc -email-

If you contact him, you can be sure he will reply, as you will hear in the interview, he would probably do anything to make they go away.

Looking forward to see, what you can put together.


Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.