I won't disagree with that (because I can't), but I find it does not apply directly to software. I'm in the camp of those who say that if you don't want this thing or that to be done with your code, it's a legal issue, not a technical one, and so should be kept in the license.

Making it a technical issue doesn't work.

It would only be worth the effort for software for which you expect broad distribution, anyway: if the code is written for a specific customer under contract, it shouldn't be hard to figure out how to insure yourself with simple and effective legal measures.

Except that the broad distribution scenario makes things much worse than they'd otherwise be. For one, increasing complexity leads to an increasing rate of bugs; many copy protection schemes that fail for a small, but significant portion of potential customers have provided ample evidence that they're no exception to this law. For another, in contrast to security in the material world, once one copy of your software is cracked, all copies are cracked. The bottom line is that your paranoia is only going to penalize your legitimate users, without particularly detracting the bad guys.

I'm not even going to go into the ethical issues I have with the idea of profitting from an incredible amount of freely provided volunteer effort while refusing to give anything back.

Makeshifts last the longest.

In reply to Re^12: Perl 6 ... dead? (no, just convalescing) by Aristotle
in thread Perl 6 ... dead? by hartwig

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.