I was just learning about this yesterday, and from what I understand, the judge is actually very smart. He supposedly holds a Computer Science Degree and was a programmer before getting into Patent Law. On the flip side, there is also evidence that Microsoft knew about it and ignored it anyway hoping they wouldn't notice. Since they didn't bring suit right away, they just continued into version 2007. Just another point proving the need to revamp this outdated set of laws.
Personally, since there is typically really only one or two particularly efficient algorithms, I would like to see it where the only patentable code (if any must be patentable) is completed works that have a particular and unique outcome. I liken most code segements to building blocks - there are only so many ways to put them together. It is like patenting bricks, mortar, and building shape(s), all in separate patents.
"Sorry, you can't build that building in a rectangular shape without paying us $$$. Nope, we have circular, oval, and triangular shapes patented too. Our competitor has the 'freeform' shapes patented as well. Good luck."
Absurd...It isn't the code that should be patented, it should be the finished product.
Now for the sticky part...How do you define at what point something is unique and patentable? If my program does the same thing as yours, but yours is monolithic code, whereas mine is 15 different subprograms; am I infringing? What if it is used in a different context (such as grocery cart programs for managing online checkouts)? If you base it on some combination of look, feel, AND function; at what point is it legal imitation vs. infringement? And why can't we have varying degrees of infringement such that if it is determined that the infringement really did take place, but it is a gray area; so you will be penalized much less harshly. Proof that it was known and deliberate - throw the book at em...
Enough of my thoughts....
