Contrast that with the open source world, where you get five good user-generated suggestions in five minutes, developer queries overnght, and patches the next morning.
<rant>
That's so untrue. Yes, there are a few projects in the open source world where that happens, but that's true for closed source projects as well. But people generalise the positive exceptions from the open source world, and the negative exceptions from the closed source world.

Look at Perl. Look at the list of open bugs. Some bugs are many years old. That's a far cry from "patches the next morning". Perl currently is on a 3 maintainance releases/year scedule, but that has been different as well. There were 14 months between 5.8.0 and 5.8.1, with no maint releases in between. Now I understand why this happened, I'm just pointing out that the open source world isn't all that shiny and fast as you suggest. And then, Perl is one of the better projects. How many open source projects are abandoned? How many authors unreachable? From how many is the status totally unknown? Care to do some statistics on sourceforge? Or CPAN for that matter?

Let's face it. No one has an interest in solving bugs that don't affect them. New features give a much bigger rewards, either because it sells, or because it gives more glory. You remember the person creating a popular CPAN module, like DBI. But do you know who solved the most bugs? You might put your list of CPAN modules on your resume. But do you list the patches you submitted to various open source projects? In fact, commercial vendors may have more of an initiative to fix bugs - not fixing them could mean losing customers (of course, if you have 10 million customers each paying a small amount losing 10 of them is less of an impact than if you have 300 customers each paying a million).

In my experience, all software sucks, and most vendors/authors are hard to move to fix their bugs. And it doesn't matter whether they are closed source or open source developers/vendors.
</rant>

In reply to Re^4: Are Perl programmers just easier to deal with? by Anonymous Monk
in thread Are Perl programmers just easier to deal with? by CloneArmyCommander

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.