A Generation of Software Patents Examined
pieterh writes "Boston University's James Bessen has published a landmark study [abstract; full paper available at the link, free of charge] on a generation of software patents. Looking at almost 20 years of software patents, he finds 'that most software firms still do not patent, most software patents are obtained by a few large firms in the software industry or in other industries, and the risk of litigation from software patents continues to increase dramatically. Given these findings, it is hard to conclude that software patents have provided a net social benefit in the software industry.' Not that this surprises anyone actually innovating in software."
They're definitely a contributing factor as to why I'm still in academia, rather than trying to start a software shop with my CS degrees.
Oh god, that woman is John Romero!
Patent process are too expensive for the average Programming shop. As well many of their innovations are not produced in systems for the general public but for their customer. The time it would take to write up the patent application get it approved etc... Could takes days or weeks of work away from working on a project that can bring revenue now.
Big companies that can produce software to a large scale (write once copy a million times) have the ability to deal with Patents, as once the product is released it is making money and will bring in a stream of revenue for a while, giving time to make formal patents and do R&D.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
The language in the US Constitution says
To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.
If software patents do not promote the progress of science and useful arts are they not unconstitutional ?
I got called in for a deposition when $BIGCOMPANY was sued for infringing a patent on $OBVIOUSTECHNIQUE in $FIELD. The level of inefficiency in the proceedings was staggering, particularly since the project I was on hadn't even used $OBVIOUSTECHNIQUE. One of $BIGCOMPANY'S attorneys told me that progress in $FIELD has halted due to fear of patent litigation, which anyone much smaller than $BIGCOMPANY couldn't possibly afford.
To slashdotters, this may be "duh" science, but it's really important to have this on paper when we talk to judges and legislators. Otherwise, we're left explaining the problems and hoping that the legislator will agree that our logic is "obviously" correct.
Bessen also co-authored Patent Failure with Michael Meurer and a previous study An Empirical Look at Software Patents, along with Robert Hunt.
http://en.swpat.org/wiki/Studies_on_economics_and_innovation
http://en.swpat.org/wiki/James_Bessen
http://en.swpat.org/wiki/An_Empirical_Look_at_Software_Patents
Expert in software patents or patent law? Contribute to the ESP wiki!
The patent process takes longer to complete than the lifespan of most software products. Writing software patent applications would pull valuable engineering resources away from where they're needed most, engineering. If everything that "could" be patented "was" patented then no one would be able to write software without infringing upon someone else's patent. This is largely the case already. Most dev houses get away with infringement because they are either not big enough to bother frying and/or the infringement is non-obvious and they fly under the radar. The expense of patenting from authorship, to lawyers, to application, through to approval is prohibitive. Enforcement of patent rights is reserved for those with war chests large enough to field the researchers, lawyers and court costs, etc..
Two of my imaginary friends reproduced once