Open source software bugs get squashed faster – even on the user’s computer!

Posted by Stormy on October 11th, 2007 in Open Source

Matt Asay has an interesting blog post about how open source software bugs get squashed faster.   I'd like to add that it's not that they get fixed faster, it's that the fix gets out to end users faster.  An open source fix is available to end users almost immediately after it gets created.  With almost any proprietary software the company has a whole test and QA process that needs to be followed first and it's at least days if not weeks before the fix is released to end users.  

I'd take it one step further and say that's why security is so much better with open source software.  When there's a security flaw in open source software, there's a fix released immediately.  With proprietary software, they try to keep the security hole quiet until they publish their fix, which just by the nature of their processes takes longer than the release of an open source software security patch.   The big proprietary company guy that finds the bug in the middle of the night is not allowed to publish his fix – he needs approval from others.  In the open source world, he can publish the fix right away and others can begin reviewing and commenting.  

Bookmark: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • del.icio.us
  • digg
  • Reddit
[Trackback URI]

Comments

Subscribe to comments with RSS

  1. Don said, on October 11th, 2007 at 5:40 pm

    With almost any proprietary software the company has a whole test and QA process that needs to be followed first and it’s at least days if not weeks before the fix is released to end users.

    Are you saying that open source software doesn’t go through any kind of test or QA process before release?

  2. Stormy said, on October 12th, 2007 at 1:30 pm

    Open source software does have a testing and QA process but the order is different. When the fix is done, it’s posted. Then anybody can see it, use it, test it, etc. Testing continues after the patch is posted. With proprietary software the fix isn’t posted until the company finishes their testing. And then often you don’t have clear visibility into the problem or the fix.