I think you're all right. Yes, it could be much better. Is it broken? No! It's amazing how well these bears dance! The tools you speak of in your follow-up attest to the enormous creativity of the OS movement. Compare this with trying to fix an incompatibility between M$ and Symantec... MTBFix is about five years, maybe, if ever. Remember "We'll fix it in five oh"???

Another point to be made is that the very nature of open source is that the wheels usually *have* been invented before (yes, it's a good thing!), and the info is out there. One of my cow-onks had some common code that built input multiplexing daemons, and we discovered that his code was linking to the wrong library APIs when we used it in two different daemons at the same time... a little research and he discovered "versioned symbols," invented to solve the glibc version crashes that plagued the GNU and Linux worlds for several years.

I think the real issue is not that there's a lot of chaff out there, it's separating the wheat from the chaff. There are two answers to this: know what you're doing, and know whose code you're running. One could postulate rating systems like PM's XP for projects -- and, yes, they're out there -- but there is no substitute for grokking something until you understand it. If you're in bed with somebody else's code, don't blame me if you get AIDS. :D

Don Wilde
"There's more than one level to any answer."

In reply to Re: Criterion for success in open source by samizdat
in thread Criterion for success in open source by Scott7477

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.