This thread is most interesting to me. The arguments of the pros and cons of commercial vs. opensource (sometimes in the context of commercial vs. freeware) always has the "when you pay for it, you get higher quality and/or more reliable support".

But, for me, the argument that you get better support when you pay for it seems not sufficiently well backed up in my real-world experiences.

For example, I actually dread ever having to call "customer service" or the "help desk" for any commercial product.

I can't remember when, for any commercial product, I could successfully (1) get through to the help in a reasonable time and (2) actually get someone who could answer my question (no matter how simple the question or answer) without having to spend interminable time trying to get them to (a) understand my language (english) and (b) getting them to be interested in actually helping me find an answer.

My experience is that the only real help comes from the generous help that folks like the Monks offer...and it's free.

You gurus providing the help are always interested and often passionate about helping, the level of knowledge and expertise seems to almost always far exceed the pay-for-help "gurus", and so many seem to truly enjoy writing amplifying documentation, faqs, and tutorials that are incredible, helpful, and extensive.

I just don't see the real-world confirmation that "you get better help (or products) when you pay for it." I can't see that Perl, Python, MySQL, Subversion and other such "freeware" products are in any way subsuperior to any of their commercial counterparts.

That's just my experience and perspective.

ack Albuquerque, NM

In reply to Re: If you want a passionate open source life, you need to fight for it by ack
in thread If you want a passionate open source life, you need to fight for it by metaperl

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.