| |||||||||||||
Implications of pure and constant functionsImplications of pure and constant functionsPosted Jun 12, 2008 11:57 UTC (Thu) by ekj (guest, #1524)Parent article: Implications of pure and constant functions
This low barrier to entry, though, is also probably the cause of the widely varying quality of the code of these projects. I hope you're not suggesting that projects where entry is more closed, such as proprietary development do not experience "widely varying quality" of code.
(Log in to post comments)
Implications of pure and constant functions Posted Jun 12, 2008 14:26 UTC (Thu) by Flameeyes (subscriber, #51238) [Link] > I hope you're not suggesting that projects where entry is more closed, > such as proprietary development do not experience "widely varying > quality" of code. In my experience, it isn't much varying... it usually is so bad it's not even funny to think of it twice. On the other hand, proprietary software that is written badly is more easily discarded, as it fails to work at all in most cases - unless it's so proprietary you can't switch for a different one. On Free Software, badly written software can easily be patched up so that it works, and is kept in circulation of months and years. I think the problem is in the big numbers, there is probably way more Free Software than proprietary software being developed by amateurs.
|
|||||||||||||