I\'m not quite sure where you are getting this view of software development from, but it differs sharply from my experience. So I don\'t think you can say it is universal.
I\'m used to software development as a collaborative thing. There\'s nothing I want more than feedback, especially in early stages. Sure, the feedback needs to be filtered and, at times ignored. But the more I put out there, the higher quality feedback I get. There\'s been times when people have found a big hold in my code, or a use case I was unaware of, and that let me correct it early and well.
Implying that it will add extra to work to the devs by not obfusticating the code is silly. No one is ever \"done\" with a project. If you note I specifically didn\'t suggest making it open source, I just said to open the code. They are as free to ignore proposed changes as they are to ignore proposed suggestions in the forum. So your car analogy doesn\'t fit. The \"other guy\" who wants to custom the car is off in some other room behind a glass barrier. The devs can watch their antics if they like, if they think it will be inciteful, or just keep heads down working. The \"other guys\" are just happy to be working on something. No matter every week a change comes through that invaildates half of what they\'ve done. It\'s a risk they\'ve accepted. They\'re building familiarity with the code base. If no one cares about what they do, the devs take no notice. But if it gets traction in the user community, then this acts as a perfect filter for something the devs might want to look at.
There really isn\'t a down side to it.