If you know or have a strong reason to believe that you are about to violate someone's patent, stop, think, think again, think some more, and keep on thinking until you lose interest in doing something that might bankrupt you. Right and wrong are nice principles to live by, but they don't really mean much in court.

Every piece of nontrivial code infringes on somebody's patent. When people are patenting double clicking and doubly-linked lists, you can't help but infringe on somebody's patent. Stopping development while the lawyers work out a deal every time you hit a patent would destroy programmer productivity.

A good chunk of these patents would be quickly thrown out if they ever went to court. It's in the best interests of the litigant to make sure things never get there. They offer a reasonable settlement and then go find another company to harass.

The only defense companies have against this is to accumulate a pile of their own patents. If a company sues them, the litigant almost certainly is infringing on their patents, so they can counter-sue. Then everything gets dropped. This game favors big companies--small ones wouldn't be able to accumulate enough patents to defend themselves.

So you're correct, trying to stand up for your ideals is impractical in court, but giving in is an equally bad strategy. Patent law and the surrounding bureaucracy is simply unequipped to handle software right now.

I don't think software patents are necessarily bad, and there are some algorithms that deserve a patent. But the system is completely out of hand as it is.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re^2: Copyright conflicts? by hardburn
in thread Copyright conflicts? by DACONTI

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.