Linked by Thom Holwerda on Thu 19th Jun 2014 23:59 UTC
Legal

The US Supreme Court has made it ever so slightly harder to patent software.

The patent claimed a method of hedging against counter-party risk, which is a fancy word for the risk that you make a deal with someone and later he doesn't uphold his end of the bargain. The Supreme Court unanimously held that you can't patent an abstract concept like this merely by stating that the hedging should be done on a computer. This kind of abstract patent is depressingly common in the software industry, and the CLS ruling will cause lower courts to take a harder look at them.

It's a small victory, but hey, I take whatever I can. Sadly, the SCOTUS also states that "many computer-implemented claims" are still eligible for patent protection, without actually explaining which claims. So, while appending "on a computer" to an obvious abstract concept does not make it patentable, the actual concept of patenting software is still very much allowed.

Even if the SCOTUS had completely abolished software patents, however, we still would have to deal with them for more than a decade - existing software patents would not magically vanish, and would still require lengthy and expensive court cases to be invalidated. Something bullies like Microsoft and Apple can afford easily, while many others cannot.

Sorry for not putting a smile on your face, but reality is reality. Sadly.

Thread beginning with comment 591037
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Well ...
by WorknMan on Fri 20th Jun 2014 19:40 UTC in reply to "RE[5]: Well ..."
WorknMan
Member since:
2005-11-13

All developers should be free to access whatever file formats they want to using their own code implementations to read/write the format.


Okay, fine. Then I should be free to use whatever GPL'd code I want in my proprietary projects, and never give the source code back. I mean, if you as a developer are going to make up arbitrary rules about what you're allowed to do with other people's file formats, protocols, codecs, etc, then two can play this game ;)

You did not respond to this paragraph, so did you agree that the patent system can deprave some developers of their own hard work?


With the software patent system being so out of whack as it is now, sure. That's why I'm talking about reform here.

Reply Parent Score: 2

RE[7]: Well ...
by Alfman on Fri 20th Jun 2014 19:58 in reply to "RE[6]: Well ..."
Alfman Member since:
2011-01-28

WorknMan,

Okay, fine. Then I should be free to use whatever GPL'd code I want in my proprietary projects, and never give the source code back. I mean, if you as a developer are going to make up arbitrary rules about what you're allowed to do with other people's file formats, protocols, codecs, etc, then two can play this game ;)



Let's not conflate copyright and patents, they're very different and I can agree with one while disagreeing with the other. To keep the example "apples to apples", then you as a proprietary developer are free to re-implement the GPL project functionality in your own software, but you'd have to write your own source code.


With the software patent system being so out of whack as it is now, sure. That's why I'm talking about reform here.


But mutual exclusivity is one of the fundamental underpinnings of a patent system, is it not? How would you reconcile one developer's right to independently develop something with another developer's right to own a monopoly on it? I don't believe this is fixable, but I'm curious to hear what you have to say.

Edited 2014-06-20 20:03 UTC

Reply Parent Score: 3

RE[8]: Well ...
by WorknMan on Fri 20th Jun 2014 20:50 in reply to "RE[7]: Well ..."
WorknMan Member since:
2005-11-13

How would you reconcile one developer's right to independently develop something with another developer's right to own a monopoly on it? I don't believe this is fixable, but I'm curious to hear what you have to say.


I'm not sure I completely understand the question, but I'm not suggesting that you shouldn't be allowed to develop something with the same functionality as what I developed. I mean, if you make something that's better than mine, and my customers end up becoming your customers because of it, then GREAT!
I'm simply saying that if you're going to do so by reverse engineering my shit, incorporating that into your own project, and marketing it based on the fact that it's compatible with mine, then you should at least be paying me a little off the top. THAT is what I mean by 'piggybacking'. Hell, I might even be willing to sell you a license to the source code, and save you the cost and aggravation of reverse engineering it yourself.

Edited 2014-06-20 20:55 UTC

Reply Parent Score: 2