This is an essay/book by Eric S Raymond, that examines if it is a good idea to release the source code to the public. It examines why the top-down and bottom-up designs struggle against each other, and if the source code is available to the public, if then the bugs and kinks will be worked out faster in the program, than if its only available to a couple developers.
I believe it is important to release the source code to the public, because by using the public to help solve the bugs in the programs, it will happen faster, and I believe its always better to have more heads look into a problem than one. With more people looking into problems, you have more creativeness and more experimentation that will happen.
Subscribe to:
Post Comments (Atom)
I agree with you however, what about all the not so nice individuals that want to scam, take, and make life alittle more difficult by reworking the source code to benefit them. I believe there is a home for both depending on the application.
ReplyDeleteWhat do you do if the people reviewing your code aren't as knowledgeable as the coders? Couldn't they just cause more problems?
ReplyDeleteAll of these questions are really good questions, that I didn't think of. People that have less knowledge, or use their knowledge for 'bad programming' can cause some pretty good problems.
ReplyDelete