The Software Patent Debate Is Incorrectly Framed
An anonymous reader writes "It doesn't matter whether a true invention is implemented in hardware or software, it should still be patentable, argues Marty Goetz — the man who was granted the first software patent in 1965."
The crux of the argument, according to the author: "Has there ever been a controversy about whether an invention using hardware circuits is patentable? I doubt it, even though hardware circuits are much like software in that they can be reduced to a mathematical algorithm."
I'm not sure if software patents should be completely abolished, just reduced. Maybe five years? I mean, how long in the software industry until something is considered old news or common knowledge? For them to last 20 years just seems to be nothing but inhibiting of innovation to me -- and I'm a software developer! I'm one of the guys that should be benefiting from a longer term. But so far, it's only been a major pain in the ass. I'm sure Goetz could argue I'm just not "inventive" enough to hold software patents. I'd wager I'm just not up to the task of working with an army of lawyers.
I actually take serious issue with Goetz's explanation on the second page of the article about software:
Note that these terms are all consistent with a manufactured product: research, competitive analysis, functionality, specifications, operational environment, operating characteristics, interfaces, modules, engineering, implemented, debugged, tested, quality assurance, alpha and beta testing, documentation, installation, training, OEM, component, system, repackaged, maintenance, warrants, workmanship, guarantees, errors, defects, improved, enhanced, upgraded, and models.
Dude, you can make software development as complicated as goddamn rocket science. But at the end of the day some kid in a basement can also write software sans all that shit. I know where we work, we use Agile Methodologies, high communication, we work in very small teams and we depend on our developers not to be complete liabilities. Sure your control gates and extensive product assurance works too with just about any level of competence in your developers but I feel that's why software is so unreasonably expensive these days.
There are plenty of resources online that get you from nothing to your first "Hello, World!" program in a matter of minutes. The same is not true of hardware circuits -- especially if you want to manufacture them at all in a commercially viable way.
This analogy is rather flawed.
My work here is dung.
That's why all patents are just plain bullshit and should be nullified...
Video of some good progressive thrash music
Hereby inserted: http://xkcd.com/435/
At one time, innovation and invention were hard to come by, and needed to be encouraged greatly. They weren't viewed as profitable and useful enough otherwise.
Today, innovation and invention is far cheaper, faster, and more profitable. The low end of the range can have massive changes in weeks. The high end still take years, money, and knowledge.
It's still worth protecting the high end. But 'protecting' the low end just stifles innovation. The system was supposed to correct for this by refusing 'obvious' patents. Now, either we need to redefine 'obvious', or there needs to be more unpatentable things. If you can bring something to market in a single month, there's no way that should be patentable. (1-Click, I'm looking at you!)
But if it takes a year, then it needs protection for the creator to recoup their money.
I don't know if it would work, but it would be an interesting twist to see patents expire when their cost has been recouped. So if you try to license patents out instead of creating the item, the best you could do would be to break even. (This would not include operating costs in the mean time, only profit, so you could probably make a decent living by stretching it out, but you couldn't possibly grow your company with it.)
"If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
Article 29 Conditions on Patent Applicants 1. Members shall require that an applicant for a patent shall disclose the invention in a manner sufficiently clear and complete for the invention to be carried out by a person skilled in the art and may require the applicant to indicate the best mode for carrying out the invention known to the inventor at the filing date or, where priority is claimed, at the priority date of the application.
Emphasis mine.
While there are a great deal of faulty patents granted, one of the larger problems Software Patents in particular face is the 20 year duration. For an industry which re-invents its self every two or three years, twenty years might have well be two lifetimes worth of work. If the duration was shorter many of the obvious junk patents would have already expired and we would be in a far healthier place.
To solve Software Patents you can't get rid of them, we're already in too deep. But you can shorten the duration substantially and make a series of special courts who's job it is to deal with technical patents (and who employ technical experts). The courts are simply too ignorant to be able to understand what it is they're meant to be deciding. They have no expertise in the software field, or in any other special area (drugs, business processes, etc) but yet we expect these people to use their "common sense" to decide things like if slide to unlock or one-click checkout should be a valid patent.
The problem with software patents is not that they are software, it's that the vast majority of them are obvious and they tend to be overly broad. Anyone encountering vaguely the same problem would produce the same solution, or one sufficiently similar that it would be covered by the patent.
The other problem is that patents really fail at their primary purpose: encouraging disclosure. No one looks for algorithms by doing a patent search. People look for published papers, existing libraries, or invent something themselves. Any one of these can end up violating a patent, but without gaining any of the advantages of the patent system.
People campaigning against software patents often get bogged down by assuming that this is something that is limited to software patents. It isn't. Talk to people in almost any industry, and you'll hear the same thing. They either have big cross-licensing agreements that let them ignore all patents and just keep out new people, or they find themselves constantly having to pay royalties for things that they invented independently.
I would have no problem with software patents if they were limited to the scope that the patent office claims: novel, non-obvious, useful. If this happened, I doubt even 1% of current patents would stand up.
I am TheRaven on Soylent News
Should you be able to patent the combining of two old ideas? Many software patents are not new but are simply an old idea implemented in a new way but using existing techniques which are obvious to anyone skilled in that area. Typically it is just an extension into a different field of use.
Eg. A database to keep track of bird sightings. There is prior art of how to record such things in a log book (spreadsheet/table format) and anyone skilled in the creation of digital databases can duplicate this format and write CRUD operations.
This would probably receive a patent in the current atmosphere. I've seen many patents just like it but for other topics.
IMHO the above example and all "software" or "business method" patents like it should be nullified. They are not new or innovative in any way. They are just applications of existing technology.
A fool throws a stone into a well and a thousand sages can not remove it.
"The software products industry is competitive and needs patent protection as much as any other tech industry. Those software doomsayers who say software is just ideas, mental processes or mathematics would change their mind if they examined the different phases of the life cycle of a software product."
Last time I checked the people that were opposed to Software Patents where almost exclusively Software Engineers, since almost no one else is aware the issue even exists.
Is he trying to say the Software Engineers do not understand their own product?