2 ms·
As the author notes, there are many exceptions on both sides, and he's not claiming that it's impossible for projects with closed development models to improve;
by cookiecaper 17y ago
As the author notes, there are many exceptions on both sides, and he's not claiming that it's impossible for projects with closed development models to improve; he's merely indicating that the way in which their software is developed lends itself to a final product of lesser quality (because developers are rushed to meet expectations set by other groups, like sales or marketing).
I think the analogy is most relevant in the case of well-matured and widespread software. Microsoft has an incentive to continually release new versions of Office (namely, there will always be many people who will buy new versions of Office), and because people don't like to pay for bugfixes, there has to be new features to print on the box. Furthermore, these features must seem relevant to your average user.
"Mature" software almost by definition includes the standard featureset its users demand. As we all know, there's always something useful you can do to your project, but once your project hits a certain point, those useful, in-demand features apply to a narrower and narrower audience.
The lack of general applicability on the reasonable "New Features" list for the next release probably upsets marketers and others determined to milk more revenue from a successful franchise, so they go back and demand re-engineering of something that already works or the addition of bloat that nobody really wants or uses but that sounds good on the back of the box.
Open-source software has none of these woes. There are no constraints imposed by the uninformed or the ignorant and the BFDL, whom in all cases I'm aware is a technical person, has the last word on a feature's inclusion.
The difference is that in the commercial world, non-technical considerations and individuals generally mandate changes and unless something is just not possible, technical is rarely given a veto. In the open-source world, technical considerations and individuals generally mandate changes, and unless the project just can't continue without it, non-technical rarely gets a veto. One of these methods obviously leads to better software. Can you pick which one?