Slashdot Mirror

← Back to Stories (view on slashdot.org)

Understanding (and Avoiding) Software Patents?

Posted by Cliff on from the patent-infringement-mine-sweeping dept.

An anonymous reader asks: "I'd like to write some Free backup software, but this area is mined with patents. I downloaded one and tried to understand it, but the 'claims' section (arguably the most important part) is made up of utterly incomprehensible patentese, and I can't afford to hire a patent attorney to help me understand it. Are there any free or cheap ways to learn enough about patents to understand them, so I can figure out exactly what is patented and therefore avoid it?" "How different does my software have to be in order to be non-infringing? The patent I tried to understand is Dantz's 5,150,473. Many, including Slashdot readers, have said what this patent covers, but from reading the patent itself, I would never have guessed. Also, there are lots of other patents to understand and avoid, so I'm looking for general information on how I can unravel it all into language I can understand."

4 of 72 comments (clear)

  1. ObLinus quote by ccady · · Score: 3, Funny

    Do what Linus does: don't read patents.

    "Technical people are better off not looking at patents. If you don't know what they cover and where they are, you won't be knowingly infringing on them. If somebody sues you, you change the algorithm or you just hire a hit-man to whack the stupid git."

    --
    J'aime mieux les méchants que les imbéciles, parce qu'ils se reposent. -- Alexandre Dumas
  2. Fish/Google by CyberVenom · · Score: 4, Funny

    Dude, that's like, totally bogus! Try using the Fish on it... Maybe its in like, Polish or something...

    Seriously, it would be interesting to see the technology behind Google Translate or AltaVista Babelfish applied not only to proper languages but also to specialized jargon and dialects: Legalase, Technobabble, maybe even Diner.

    Hmmm, imagine using the fish to translate "From Legalese to Engrish" *cringes*

  3. Simple by Anonymous Coward · · Score: 5, Funny

    Just clone something at least 20 years old. Bring it up to modern standards by adding translucent drop shadows and a few gratuitous memory leaks. This is the method used by all major software publishers and it works without fail.

  4. For a temp solution by boogy+nightmare · · Score: 3, Funny

    Or for a more temporary solution.... move to Europe

    --
    Kingdom of Loathing (www.kingdomofloathing.com) Addicted is me