Courgette meets a dangerous (Red) Bend
Posted Nov 2, 2009 22:41 UTC (Mon) by
socket (guest, #43)
In reply to:
Courgette meets a dangerous (Red) Bend by AlexHudson
Parent article:
Courgette meets a dangerous (Red) Bend
I think an argument can be made that any invention becomes obvious if you can ask the right question to prompt it and understand the basic prerequisite knowledge.
There are likely a large number of patents in the world that aren't obvious to me, but I attribute that to the fact that (for example) no material-science related patent is obvious to me, because I'm not a chemist. But show me a software patent, and it will seem obvious to me. Thus, the "rule" that patents shouldn't be obvious to the typical practitioner with the relevant experience.
Sometimes the interesting part of an invention isn't the process used (the content of the patent) but simply the problem it's trying to solve. The solution may be obvious, but realizing the fact that the problem existed in the first place is an insight in and of itself.
This particular patent seems to me pretty obvious, once you start thinking about how to do compression: Compression relies on finding repeated patterns in data, and abstracting away that information - that's obvious. The result of compiling code after making changes is an object file with systematic changes. Those changes can involve pointer address changes - and this is obvious to anyone who programs much in C. If the typical C programmer were asked to make a compression program for executable patches, this seems to me that looking into systematic changes like pointer addresses is not just obvious, it's the low-hanging fruit.
Nearly every software patent I've heard of is either an analogue of an obvious, everyday process in the physical world, or the description of a mathematical algorithm in terms of software. Simply adding "...with a computer" to an obvious, ordinary process doesn't make it any less obvious. The patent system would be made consistent with itself either by removing the exclusion of mathematical algorithms from patentability (a bad idea, in my opinion) or by adding an exclusion for software-related patents.
(
Log in to post comments)