Then there's the new 'Bazaar', in which rapid development around a core team of developers is favoured, developers who are constantly in contact with users and co-developers - most of open source software development happens like this. Especially towards the end the book builds up a few straw-men to take down, and then it gets annoying - like when the book says that 'Bazaar' style development doesn't need the business (Cathedral) world's top-down style management, because open source is just so much fun that it doesn't need managers!
The statements and assumptions are that bugs in a new version will be seen and fixed quickly, and that a project will be forked if it represents a change in direction not desired. Twelve years later, Fedora may now have returned as the most acceptable desktop version to support KDE and bleeding edge development software. Four and five year intervals are a long time in any software cycle, and too long for instability for a dedicated user. In this case, the Gnome desktop shell has been forked, and is being modified in separate stream versions, but it has represented a major disruption in the configurability and interaction with the desktop. In a more mature phase, open source is not shining to either established or new users due to the lengthy time disruptions of large scale critical systems. Apple is an extensive user of open source and has even been a major sponsor of important projects. 3. A lot of open source startup companies have been purchased and squashed by major corporations. For example there is not an effective up to date x86 version of Android that can be conveniently run on any desktop. 5. Being too critical two decades in hindsight is not fair, but near the end of the book it was approaching an evangelistic tone, which as a dedicated open source user for the last 12 years, I feel needs to be a moderated message in the face of massive FUD campaigns and limited uptake by general users who don't have the need and will never understand development models.
How would a book shaped like THE INTERNET feel in your hands?
The book is an exploration into the world of Open Source, and the culture that goes with it. This cultural phenomenon is enabled by the developed connectedness that has come with the internet.
No one can be an open source coder for the reputation, but the reputation is the community's way of letting developers know that their work is being used and appreciated. One way to think of it is that reputation lets people know there is value is working for others, not just themselves.
Outro ponto marcante no livro é as experiências de Raymond com o cliente fetchmail que trabalhou e administrou, comparando o seu desenvolvimento com o do Linux, juntamente, contando 'lições para um bom programador open-source' que aprendeu durante o desenvolvimento da tecnologia e das tedências que observava.
Raymond is an observer-participant anthropologist in the Internet hacker culture.