Paul Graham on Patents
volts writes "The always interesting Paul Graham has a new essay, 'Are Software Patents Evil?'. "A few weeks ago I found to my surprise that I'd been granted four patents. This was all the more surprising because I'd only applied for three...""
Its funny. The founding fathers of the USA wanted to have a patent system to protect the little guy. The little inventor that creates a new and novel item. That way a big bad company cannot steal it from him, and he never makes a dime. Now it seems that it is just used by slimy lawyers to use patents as part of an extortion scheme to shake down big companies. Alternatively a way for big companies to keep anyone from ever entering their territory. The sad part is I think it will only get worse - not better.
They are.
It does not take a long essay to answer this.
And BTW, Paul Graham is wrong when he says, "if you are against software patents, you are against all patents".
All patents have the potential for evil. But software patents are guaranteed to do evil.
Question: why are there so few new software standards coming out and why do they take so much longer to produce? Answer: because every new software standard is a recipe for patent ambush. Implemented, use it, or use products based on it, and you will, if you make money, be sued.
Yes, software patents are evil because in the name of promoting innovation in a field, they actively destroy it.
My blog
One thing I do feel pretty certain of is that if you're against software patents, you're against patents in general.
Wrong. Hardware patents are necessary to commercialize new products and keep innovation. Some medicine patents are also necessary, but I believe there are cases where patent licences should be greanted for only a little time - like cures for cancer, AIDS, or the avian flu.
But patents for software or business methods are an aberration.
I will only address one point of the optimistic idealism I saw in several parts of the article, there are others:
"A company that sues competitors for patent infringement is like a a defender who has been beaten so thoroughly that he turns to plead with the referee."
This point is made in the context of other statements that indicate this is the main reason that a company starts suing for patent infringement. The reality is there are companies that have no developers at all, just lawyers, whose sole purpose is to seek out and buy patents and pressure other companies for licensing fees. There are other companies/people who do nothing but try to think of patentable ideas to lay claim to, and never intend to build a product; only to extort license fees from others.
There are other examples of what the author would like to believe that gloss over the terrible realities of software patents; despite the many good points he does make.
Robert Oschler - RobotsRule.com
If software were really no different from physical systems, 99% of software patents would be invalid because they consist solely of obvious (indeed, pre-existing) inventions with the words "using a computer".
How is the one-click patent not invalidated by the prior art of millions of human shopping experiences in which a customer says "One of those please", or a vending machine in which every item has its own button? Nobody would allow a patent on a type of vending machine based on how many times you have to push a button.
And if a one-push vending machine would not be patentable, why is a one-push webpage?
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
I get the impression that the "founding fathers of the USA" were pretty good blokes with the best of intentions. Certainly very different from the politicians in power in the US today.
I think their patent system was a mistake, though. Patents are a mistake simply because large companies have so much legal power compared to individuals that it is almost impossible for an individual to win a case against a large company. This was probably a difficult thing to imagine when patents were invented, since really big companies wouldn't have existed back then, and the legal system was probably also quite different. There was probably no such thing as "expensive lawyers".
"I have a porkchop, you have a porkchop. I have a veal, you have a veal".
A very simple discussion point
Copryright is more applicable to software than Patents.
Feel free to discuss it, but I do not beleive that any person or group, has yet or will disprove the above statement.
I'm willing to engage in this discussion, furthermore I'm also willing to keep an open mind.
Graham has engineers disease: he believes that being an accomplished engineer makes him qualified to speak authoritatively on art, law, science, film... He probably caught it from ESR.
Anyway, I heartily recommend you read this fine demolition of Graham's opinions on painting before giving this dilletante blowhard any of your copious free time.
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
"Are patents evil?"
EFF: "Yes."
Microsoft: "No."
Smart Person: "Depends..."
Silence is golden... and duct tape is silver.
He couldn't be more wrong.
Software is instructions to hardware. Instructions should not be patentable. Hardware should be patentable - though there may not be a business case to make it worthwhile.
The otehr day I had to give directions to a picnic to a group of soccer players. There's really only one reasonable way to get from where they were to where they'd be going. What if someone had patented the description of how to get from Point A to Point B, that is how to get some hardware from one state to another? Does anyone think it logical that I would have to pay a royalty for telling this bunch of 13-yr olds (well, their parents) directions to get to their picnic? No? Then why are a set of directions to a collection of hardware patentable?
The directions could have included a toll road - or an alternative existed to take a more crowded road instead. Here is a pay-for-the-patented-hardware concept that makes sense. Using the toll road costs money but saves time. Using the public road is cheaper in money, but costs traffic congestion. But either way, the directions to use either road are free for any to use. And for what it's worth - the public road has many services along it that make money. The toll road, built privately by private financing, saves a few minutes. Of course, in this case, the private financiers have taken a bath. They envisioned charging a bunch for the access rights to their frontage property to service providers - but few people use their overpriced path. A better business case could be made that the toll road owners should remove the tolls and collect a royalty from the service providers that would then invest in locating on their frontage road, but hey I'm not an investor in that endeavor so who'd listen to me.
There used to be services (maybe still are) before mapquest and friends that provided directions for trip planning - you paid $10 to AAA and they told you the "best" way to get from point A to point B. No one would have thought of patenting those directions, and you were not paying for a royalty for their use - your payment was for the work someone did (at sometime) to figure out a route - but you're free to look at a map and make some phone calls to the various state traffic agencies to find construction delay zones, etc. and work out your own route.
Say you planned, some years ago, to drive from Chicago to Los Angeles. Say you glanced at a map of the time and decided to "get on Route 66 headed west and stay on it till you see the ocean." Besides a trip with about 1000 burger joints, you now have some directions. Now say you asked your friend his idea of a good route for the trip, and he'd recently done that trip by contacting AAA, giving 'em $10 and they worked out a trip plan for him based on some criteria, and he got back: "get on Route 66 headed west and stay on it till you see the ocean." Do you owe $10 to AAA for those directions? What if they (like software) were patented?
Software patents are a bad idea. They impede progress. They tell (possibly justifiably patentable) hardware how to get from condition A to condition B. If those same directions would work on someone else's nonpatented hardware, then they should be free to be used.
My first reaction to the (lengthy) article was simply, "it is a breath of fresh air to read something thoughtful and insightful on software patents." As part of full disclosure here, I should mention that I have one (6,865,655) and participated in the arcane and sometime frustrating process. That said, the author's point that "fixing" the system might not be the right thing to do, either gave me pause. He might have a point.
After participating in several start-ups, I can also attest that the number of patents held directly affects your valuation. The author alludes to this, "A patent seems to change the balance. It gives the acquirer an excuse to admit they couldn't copy what you're doing. It may also help them to grasp what's special about your technology." Right or wrong, it is one of the external measurements made by business today of a start-up's worth.
Software is the most complicated thing man has ever created. It isn't surprising that the Patent Office struggles. The question is, as software professionals, will we choose to help or just stand by like "art critics"? Software engineers usually see a bad system and want to immediately "chuck it", re-write it, and go again. We can't do that here. We need to do the thing we all hate most: on-going maintenance. We could help if we engage and participate. Perhaps more thoughtful discourse like this will help us get started. My 2-cents.
It's a very good article -- and while I've not yet finished reading it, I loved this quote;
:-)
"...the USPTO in effect slept with Amazon on the first date."
As a side note, if any USPTO examiners who are assigned to one of the several applications I have pending are reading this; I will still respect you in the morning -- no really, I will.
Ian Ameline
Actually, there is a good distinction you can draw between software patents and conventional patents that is strong enough that you can't automatically infer that being against software patents means you are against all patents: Software patents are the only things I know of where the patented objects are also covered under copyright law.
I go more into depth about this elsewhere, but the short answer is that we shouldn't be surprised that patents, balanced for one type of use, and copyrights, balanced for another, make no sense when both are covering the same thing, since they were never designed to do that.
Obviousness is a real problem too, of course, but that's more a practical problem, one that could be corrected by more aggressive denials by the PTO. This is a fundamental conflict.
Calculating (a+b)*(a-b) is better (in terms of rounding errors with fixed point arithmetic) than (a*a)-(b*b). Knowledge or application?
Suppose I was the first to notice this fact. Should I be granted a patent on calculating differences of squares this way? I have a gut feeling that this would be patenting math. And I don't see much difference between this and any other patent on algorithms. Maybe there are software patents that aren't patents on algorithms (for example GUI stuff), but again, the distinction is blurry.
Ok, this is still on the "gut feeling" level, but I think that with the software patents banning them is just simply the lesser evil than allowing them. I think that there is rather a continuum than a sharp distinction between "knowledge" and "application", and that software is close enough to "knowledge" to make it unpatentable.
To stretch it a bit: if you are for software patents, you are for patenting math.
And he thinks that Microsoft would be deterred by a boycott?
Bruce
Bruce Perens.
I am I ok with ETH-Zurich patenting the IDEA encryption algorithm because this algorithm IS truly non-obvious. You, me and Joe Q. Hacker are not going to infringe on this patent accidentally.
One click shopping or Apples patent on the "3 pane interface" for itunes are stupidly obvious. A person coding in a drunken fog should not be able to create an infringing program by accident (IDEA passes this test, one click and 3-panes does not).
The reason many folks (like me) jump on the anti-software patent bandwagon is a lack of confidence that anything short of abolishing software patents will be effective. Obvious patents benefit powerful corporations who can set their minions to the task of patenting belly button lint and other "innovations". With all the vested interest in bad patents it is easy to see why we are skeptical that meaningful reform (i.e. enforcement of the "non-obvious" clause) will occur. Of course if software patents cease to exist then the slippery slope of what is "non-obvious" disappears.
Mind you I don't think we will be successful in abolishing US software patents (not without a bloody "cultural revolution" a la Mao Tse Tung) but the disgust engendered by horribly bad patents naturally inspires an excessive reaction in the opposite direction.
BTW, if you think it is an accident that bad patents are issued left and right, think again. You won't find Microsoft, Oracle and Amazon spending millions of dollars lobbying Congress to properly fund the patent office. The patent office is underfunded because the people who get face time with our leaders like it that way.
Couple thoughts as a previous big co. acquirer and with some experience in the patent arena.
:P).
i nv_utl.htm
As a big company... I've worked for a few Fortune 500 companies that have done extensive acquisitions and as a 'big company' guy, the concept that patents are solely used as a chip for negotiations is a naive statement. When buying the assets of a business, the patents and trademarks are typically the ones that last. Many entrepreneurs (I should know as I am one now) are interested in cashing in and as a result, an acquiring business cannot solely look to relationships or know-how for value, so IP is what's left. If you really have a truly unique idea/product/service, then protecting it should be stupid-easy (and with luck, people will say it was obvious 10 years later because of its streamlined solution
Patent novelty is an issue in need of resolve... I don't believe in quantity over quality as Paul Graham might suggest, but I do believe in quantity to be successful. The process is age old - find needs, solve problems, research for current solutions and protect the best ideas. Getting quality patents should be easier now since more data is available. The USPTO and the market really do have a new set of options to consider (e.g. peer reviews, more collaboration amongst reviewers). Slashdot members can find novelty, or lack thereof, in a topic in less than 30 minutes - why can't the USPTO? With a production-line environment at the PTO, it is hard for patent agents to get a fair chance to research technology and be rewarded for deep tenure in a field. We should avoid thinking of this as 'patent reform', but rather as funding the system approapriately given the systems explosive growth.
In the end, patent ownership, like land ownership, has rights and benefits that shouldn't be reduced to a simplistic version of cold war analogies of large companies determining our fates. The patent system should level the playing field and give small guys and individuals a chance to have rights. BTW, if we should ever be worried about the small guy, now is the time. Individual inventors' patent issuance has decreased every year since 1999 - http://www.uspto.gov/web/offices/ac/ido/oeip/taf/
CSorice
Working to make ideas into reality. www.i4e.com