Live data from Hacker News

The Supreme Court Should Invalidate Software Patents

blogs.forbes.com

101–110 of 119 posts

Re: The Supreme Court Should Invalidate Software Patents

#101
post #3

Software patents are a policy issue, not a constitutional question. This needs to get fixed in Congress.

I take a more practical stance: the courts have the ability to fix the situation quicker.

That's only practical in the short term. The courts already have too much power - there's no reason to give them more.

Re: The Supreme Court Should Invalidate Software Patents

#102
post #85

Earlier quoted context omitted.

However, that's not their job. The supreme Court's job is to make a decision based on the laws set on the books. They can't say, "Well, this version of the law would be better, so we'll go with that, but rather "Thus is what he law says". We need to educate Congress. Better yet, we need educated people in Congress.

I would argue that that is in practice their job, especially given the amount of ambiguity, both unavoidable and superfluous, in the legislation-as-written. I actually have a very strong dislike for Scalia because I think that his legal 'originalist' philosophy is pretty much like biblical 'literalism' - it's an interpretation that is (a) convenient to him and (b) denies the validity of all other interpretations in a…

I find originalism to be the only reasonable way to interpret the document. If the constitution doesn't say what you want it to say, then change it. Once you start changing the meaning of the words you defeat the purpose of having a written constitution.

Re: The Supreme Court Should Invalidate Software Patents

#103
post #86
post #78

As a software programmer I don't agree with this view that software patents are wrong in principle. There I said it! Software just as much as hardware can be used to "express" something new. I.e. to invent something. An patentable invention is a novel "solution to a problem which is NON-OBVIOUS to someone skilled in the art". The real issue with software patents is that they are granted far too easily. The test that…

As the article points out, software is also protected by copyright, and the article doesn't mention that it's covered by trade secret protection as well. The key difference is that patent protection applies to people who independently create something, whereas the other two protection methods don't. So when I hear engineers say they like patents, first of all I assume that they've never worked for a company that's be…

akeefer. I find it arrogant when someone assumes that disagreement means that the other person just don't understand. Ok. That aside. Let me go back to the actual issues here as I see them.

You seem to be arguing that writing software is basically a creative process which is the same as producing literature and music but software is fundamentally different in that it goes beyond aesthetics. Software is not normally used to produce an expression / statement about life / culture or someone's emotional state etc but is used to process data in such a way as to have a functional and measureable impact.

Here's a question for you. Your competitor has patented a "solution" which basically the same as yours and is now sueing you for infringement how would copyright and / or trade secrets help?"?

Here's another question. Why is a software patent special? As opposed to one based on expression of a solution to a problem in terms of, say, electronic circuitry?

Let's say that your wish is granted and software patents are made illegally but hardware patents are still legal how would we stop companies like Apple and HTC "gaming" the system by tying the software to physical devices so that they become hardware patents?

I'm not sure I have all the answers but making software patents a special case just feels wrong and is likely to have so many legal loopholes as to be worthless ?

The patent system as currently practiced is broken. That much is clear. It was supposed to be about promoting innovation and the spread of knowledge. Instead it seems to really be about granting monopolies. But until the law is changed companies have to apply for patents if only to protect themselves against attack.

We need fundamental changes to the patent system which applies to ALL patents.

Re: The Supreme Court Should Invalidate Software Patents

#104

This will never happen. Consider a mechanical timer in a washing machine. A timer that produces a novel washing cycle is certainly patentable. Consider a chain of electromechanical relays that produces the same cycle. Clearly it is just as patentable, and could be covered by a well-written version of the preceding patent. Consider the transistorized version of the preceding, with the relays replaced by transistors. P…

Your contrived chain of analogies ends in a total strawman. I think you intended the last item on your list to be pure software, but it's not. It's just an electronic version of the first item.

No one is arguing that a complete electronic timer should not be patentable. The argument is whether the software alone should be patentable.

The software by itself is NOT a timer. The timer's software is only the idea of the timer; it is the instructions, the observation of which allow the physical timer to function. There must still be a physical timer -- an assembly of physical parts that follows programmed instructions to provide a function. That entire assembly is what should be patented.

The bare idea of the timer -- the steps that the timer takes while it's working, should not be patentable. That's what the article is proposing. Nowhere in your analogies is bare software addressed.

Re: The Supreme Court Should Invalidate Software Patents

#105
post #86

Earlier quoted context omitted.

As the article points out, software is also protected by copyright, and the article doesn't mention that it's covered by trade secret protection as well. The key difference is that patent protection applies to people who independently create something, whereas the other two protection methods don't. So when I hear engineers say they like patents, first of all I assume that they've never worked for a company that's be…

akeefer. I find it arrogant when someone assumes that disagreement means that the other person just don't understand. Ok. That aside. Let me go back to the actual issues here as I see them. You seem to be arguing that writing software is basically a creative process which is the same as producing literature and music but software is fundamentally different in that it goes beyond aesthetics. Software is not normally u…

It's possible that we need reform for other types of patents as well. I don't know enough about patent abuses in other fields to say. But in software at least, it seems like the system is clearly broken. Invalidating all software patents would be a drastic step, but it also might be the cleanest and most direct way out of the current morass. Of course, many companies would try to redefine their software patents as some other type of patent, perhaps by linking them to the hardware, as you suggested. There would need to be some legal jousting until precedents had been set to determine the outlines of how the law would be applied. That's what the courts are for. However, it seems quite likely that the resulting system would be less biased against innovation, more transparent, and less wasteful than the current system.

Re: The Supreme Court Should Invalidate Software Patents

#106
post #99
post #77

Earlier quoted context omitted.

Regarding my initial point, I think software falls under copyright solely because its written - I don't know if that's the argument now, but I imagine that was at least the initial reason for granting copyrights. Personally, I can find no meaningful difference between designing software and designing a mechanical device. For that reason, I don't like that argument. Your main point is interesting, but I'm not sure if…

"Regarding my initial point, I think software falls under copyright solely because its written" No. That's a degree of misconception that I can't fix in an HN post. Copyright has little to nothing to do with the medium in which an expression is fixed. And with all due respect, the rest of your post is so muddled w.r.t. what copyrights really are that it's hard to even address what's there. (I truly mean "with all due…

What I meant was, "it's fixed somehow". I assume the original reasoning for why code is copyrightable is that when I write, say, a book, that is copyrightable. Code is written down just like a book is, so it follows that copyright will apply. I'm not saying that's the legal reasoning. I'm saying that was probably the initial gut-reaction to why copyright should apply to code, and the legal reasoning came afterwards.

I have spent time with the various forms of IP, and I feel I have a pretty good grasp of what copyright is. I can't correct any misconceptions unless you point them out - although I have a feeling it's more that I did a poor job of expressing myself.

Attempt the second: with non-software inventions, you can have a copyright on the documents that explain how to build the invention. You can have a patent on the invention itself. Software can be both copyrighted and patented. You object to this because it's the only instance we have of something that can be both copyrighted and patented - it's a unique exception. I responded to this objection by pointing out that software is also unique in that what you use to describe exactly how to make the invention is the invention itself.

Re: The Supreme Court Should Invalidate Software Patents

#107
post #102
post #85

Earlier quoted context omitted.

I would argue that that is in practice their job, especially given the amount of ambiguity, both unavoidable and superfluous, in the legislation-as-written. I actually have a very strong dislike for Scalia because I think that his legal 'originalist' philosophy is pretty much like biblical 'literalism' - it's an interpretation that is (a) convenient to him and (b) denies the validity of all other interpretations in a…

I find originalism to be the only reasonable way to interpret the document. If the constitution doesn't say what you want it to say, then change it. Once you start changing the meaning of the words you defeat the purpose of having a written constitution.

Don't look now, but language, culture, and technology all change. Change right out from under the most carefully-written of legislation, in fact. Adapting to the now is what I think is the "only reasonable way" to come at the document - and has the advantage of admitting that it's an interpretation, instead of attempting to sneakily de-legitimatize all other interpretations.

But you go ahead and ask James Madison what he thinks about LulzSec.

Re: The Supreme Court Should Invalidate Software Patents

#108
post #107
post #102

Earlier quoted context omitted.

I find originalism to be the only reasonable way to interpret the document. If the constitution doesn't say what you want it to say, then change it. Once you start changing the meaning of the words you defeat the purpose of having a written constitution.

Don't look now, but language, culture, and technology all change. Change right out from under the most carefully-written of legislation, in fact. Adapting to the now is what I think is the "only reasonable way" to come at the document - and has the advantage of admitting that it's an interpretation, instead of attempting to sneakily de-legitimatize all other interpretations. But you go ahead and ask James Madison wha…

>Don't look now, but language, culture, and technology all change. Change right out from under the most carefully-written of legislation, in fact.

Yes, and so what? There's a huge gulf between legislation, which is meant to be crafted for the needs of the day and can be easily modified, and a constitution, which is a blueprint for how the government functions. Human nature hasn't changed in the last 300 years. Not one bit.

>Adapting to the now is what I think is the "only reasonable way" to come at the document - and has the advantage of admitting that it's an interpretation, instead of attempting to sneakily de-legitimatize all other interpretations.

The other interpretations are illegitimate - there's nothing sneaky about it. They're nothing more than cruft added by people who didn't have the votes to actually change the document. "Adapting to the now" is precisely the purpose of legislation and also the reason the constitution places boundaries on that legislation.

Re: The Supreme Court Should Invalidate Software Patents

#109
post #86

Earlier quoted context omitted.

As the article points out, software is also protected by copyright, and the article doesn't mention that it's covered by trade secret protection as well. The key difference is that patent protection applies to people who independently create something, whereas the other two protection methods don't. So when I hear engineers say they like patents, first of all I assume that they've never worked for a company that's be…

akeefer. I find it arrogant when someone assumes that disagreement means that the other person just don't understand. Ok. That aside. Let me go back to the actual issues here as I see them. You seem to be arguing that writing software is basically a creative process which is the same as producing literature and music but software is fundamentally different in that it goes beyond aesthetics. Software is not normally u…

I apologize if I came off as arrogant; this particular issue gets my hackles up a bit, and it frustrates me when I hear engineers espouse a dogma that I feel like isn't in their best interest. I think pretty much any engineer who's been affected by patents has been affected negatively by them; there are very few engineers with direct positive experiences where "thankfully I had a patent, or else someone would have stolen my work," and many more "someone else is trying to profit from my independent work" stories. (The positive experiences around having patents usually relate to being able to use them to defend yourself). But I realize I was uncharitable there, and that you have a reasonable basis for your beliefs; my apologies.

As to your first question, in a world without software patents, that wouldn't happen exactly as you describe it. What copyright and trade secrets protect you against is outright theft; that's actually a large part of what patents are supposed to protect you against (i.e. you invent something and I just copy it). In physical devices, copying is easier than in software, since the number of elements involved is relatively fewer and because things are easily amenable to disassembly, and there are few "implementation details" that are hidden from an initial set of observations. In software, "copying" something these days generally means re-implementing something that has the same effect, but the implementation techniques could be radically different. As a result, in software as it is now, patents don't prevent theft by "copying" the actual implementation, they effectively prevent re-implementation of the same features, even if that implementation is radically different than the original. (Witness pretty much any software lawsuit in the news in the last six months). So again, copyright and trade secret protections protect you against outright theft of your work: someone stealing your code and re-using it without your permission, or stealing your internal documentation about how things work, or even reading your proprietary source and using it to guide a new implementation. They don't prevent someone from "copying" your software by implementing their own program that does the same thing. If someone does that, and they independently (with no help from you) go ahead and rebuild your system, why should you get to profit from that? If you have a pizza place and another pizza place opens next door and copies your menu, you don't get to sue them for patent infringement: you make sure your pizza is better, or your cost base is lower, and you compete on the merits. That's how pretty much every other business on the planet works: if someone comes out with a similar product, that's life, and it's your job to be better. Imagine how ineffective our markets would be if that weren't the case.

Secondly, software patents are "special" because patents in general are special: they're a constitutionally mandated pragmatic tradeoff that grants people temporary monopoly rights in exchange for the greater public good. (Note that in Europe patent rights accrue from a theory of "natural rights" effectively, but in the US it's 100% pragmatic in base). So if, pragmatically, software patents do more harm than good, they shouldn't be there, end of story. The benefits of patents are supposed to be two-fold: to give people an incentive to create things, and to give them an incentive to disclose their creations without fear of copying. The latter point is more or less totally moot with software: lawyers advise their clients not to research patents for fear of knowingly infringing something, and on top of that the patents themselves are incomprehensible. So that benefit is basically a 0 with software patents, with perhaps a 0.001% exception for significant algorithmic patents around compression or cryptography. The incentive to create benefit is also pretty difficult to justify; lots of small software development shops have exactly 0 patents, outright theft is prevented by copyright and trade secret protections, and these days most companies use patents entirely to avoid being sued themselves or in an anti-competitive fashion. I believe it would be tough to make the argument that less innovation would happen without patents, given the huge number of open source and independent developer projects that are threatened by patents. So software patents are "special" because they fail the pragmatic test: the ROI on them is intensely negative, patents (in the US at least) are only supposed to exist as a way to benefit society, therefor software patents shouldn't exist.

Again, there already are special cases, in that things like book plots or fashion designs aren't patentable; it's up to the legislature and the courts to draw the line on patentability, and they've chosen to say that mathemetic formulas aren't patentable, plot devices aren't patentable (but people try), but that genomes are (which is intensely controversial and the line is fuzzy), as are hardware devices, pharmaceuticals, and now (as of the last 15 years) business methods and software. The line gets drawn and re-drawn all the time. Why not draw it in a way that accrues the most benefit to the public? That's the constitutionally-mandated reason for there being a line at all.

So I don't disagree about general patent reform, but I do disagree that software isn't a special case: it is (along with business method patents) because it's an area where patents are doing the most harm, have almost no benefit to outweigh that harm, and where independent invention is the rule rather than the exception.

Re: The Supreme Court Should Invalidate Software Patents

#110
post #83
post #67

Earlier quoted context omitted.

In many cases the any court (in almost any country influenced by the French law) interprets the laws and confirms if the 'new laws' is consistent with the 'old laws/ more basic laws' and not in violation with the basic premise of the constitutions. Of course this is a over-simplification but this is at the most basic the function of the courts.

But I believe the US uses Common Law (English) and not Civil law (France and many other places) system for these matters. So judge can in the US (btw IANAL) decide if a law is valid or not based on constitutionality and previous laws.

This is absolutely correct and is an important distinction and I do confess that my statements were not very precise from that regards. However, I had a long discussion with a law professor at Berkeley where she did agree that the US Common Law is highly influenced by the French Civil Law, though many law academic in US will take an exception at the statement. Also, IANAL either but am taking a few law courses here.
Post reply on HN