I was thinking after my previous post, that irregardless of whether the source is open or closed, if the end product is good, or fills a niche, someone is either A) going to extend/refine it, or B) recreate it in some shape or fashion

So given your feelings, how would you suggest they go about making money off their creation, without losing their edge over the competition. I personally am adamantly for open source, but alot of people out there aren't.

You have been in this field a long time and more than likely have garnished a bit of wisdom over that time. Can you provide suggestions in regards to a (better|different) way to handle this given scenario?



/* And the Creator, against his better judgement, wrote man.c */

In reply to Re: On open sourcing your applications by l2kashe
in thread Restricting access to cgi source by pernod

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.