#5: I would agree that you have more communication with OSS developers, but do they listen?
In some projects, the developers are very responsive and work on issues, but in others, they usually ignore your requests or bugs unless they're interested in addressing it.
OTOH, with proprietary, you may not have a much direct access to the developers, but the company as a whole is much more interested in your feedback. They spend lots of times at big customer sites observing their software in use and addressing issues immediately.
So if you're interested in being heard, but not necessarily being acted upon, OSS is the way to go.
If you're interested in having problems addressed, but not necessarily having direct access to developers, then proprietary is the way to go.
I think most people are interested in the later.
Another interesting point is that the level of responsiveness of an OSS project is directly proportional to the free time the project members have. And if they have more time, they're generally unemployed or probably not as good for some reason and the project isn't that great.
There are some good projects where the developers have lots of time to address issues, but they're usually subsidised by a larger corporation in which case the model isn't sustainable.
So you either have not-so-great developers with lots of free time, or good developers with no free time, or good developers who are being paid through an unsusstainable business model.
I don't see how any of those are good things.
|