Rating: 
Summary: Five stars is too few
Review: There are good reasons why the stock market puts astronomical values on the Internet, Linux and the open source software development methods that brought us both. You will find those reasons in The Cathedral and the Bazaar, by Eric S. Raymond. What the market intuits, Raymond explains.And what he lays out is nothing less than the take-over of the software business by its own most inventive and accomplished practioners: the software inventors, architects, designers and builders who gave "hacker" its original and persistent positive meaning, and continue to wear the label proudly. Nobody knows more about hackers, and hacking, than Eric Raymond, the "accidental revolutionary" who is no less qualified and effective as an "accidental" anthropologist, sociologist, historian, economist and publicist. Raymond is more than a polymath: he is the only leader in his movement playing most of those roles, and doing it with equal measurues of delight and authority. The fact that he is himself a first-rate hacker is diminished only by the presence in the world of so many others. So is the fact that he is a first-rate writer. Maybe hackers would have taken over the software industry without Raymond's help. But at this point it is too hard to imagine either hacking or the software industry without him. It was Raymond's original on-line version of The Cathedral and the Bazaar that convinced Jim Barksdale and Netscape to open the source code to their browser. That started a fire that Raymond has stoked with log after log of additional insights. Some came in the form of new essays and others in the form of highly quotable public and media appearances. All the major essays and many of the additional thoughts are represented in this book. My only quibble is with the first word in the subtitle. If these are "musings," then E=mc2 was just a "thought."
Rating: 
Summary: Provocative
Review: This bible of the Open Source movement is well written and provocative. It lays out the thinking behind Open Source clearly and takes one into new territory about how work should be valued in the information society. Not every point is convincing and recent history may make some points obsolete, but it is well worth looking at. And good read also.
Rating: 
Summary: I hope you'll share my journey of discovery
Review: This book explains how I learned that most of what I thought I knew about software development was wrong -- and how we can build programs that actually attain the kind of reliability that is normal in other branches of engineering.
Rating:
Summary: hacker = good guy
Review: this collection of eric's papers is a wonderful start for anyone intersted in the open source "revolution." i suggest visiting his website also. eric's view on software development/management will change the way anyone thinks about the process and appreciate the power of the internet. also the word "hacker" won't strike one as a criminal anymore. great book.
Rating:
Summary: Very Good,
Review: This is a pretty awesome book. ESR shines as a master historian of unix/open src/linux and the hacker culture.
a must read for any hacker at heart. santy
Rating:
Summary: "Given Enough Eyeballs, All Bugs Are Shallow"
Review: This statement above is the fundamental premise for open source software development. Basically, open communications work better than closed, limited ones. So why is this book worth reading? Essentially, because it explains why people are willing to volunteer their time and talents to improve open source code. That characteristic of the open source movement will be the main puzzlement to nondevelopers. But beyond that, this book also provides the basis of an important paradigm for accelerating and improving knolwedge development generally that will be its more lasting and important contribution. Mr. Raymond is a very good thinker from an economic, sociologial, and anthropological level, and applies these perspectives well in the essays in this book. Because he assumes you may not know about the development of the open source movement, his essay, A Brief History of Hackerdom, fills in the gaps. By the way, he defines a hacker as a capable software developer who loves his or her work rather than someone who breaks into other peoples' computer systems. The centerpiece of the book is the essay with the book's title. This essay describes his own experiences in developing an open source e-mail utility, draws lessons from that experience, and compares it to the development of Linux (the primary open source operating system). I knew the Linux story well (if you don't, you should, and this essay will be valuable to you), so I was primarily drawn to the discussion of the author's own experiences. Clearly, the appeal of open software is a chance to work in depth on something that has compelling interest to the free source developer, receive help in getting a better result, get to use the improved software oneself, and recognition for the effort from highly talented people you respect. In other words, assuming your day job still pays the bills, your open source software work will provide for most of your psychic needs. That's pretty neat! I couldn't help but think about the analogies to people writing book reviews on Amazon.com as I read this section. As a result of reading this essay, Netscape chose to open up its software and escaped oblivion in the process while undergoing the assault from Microsoft's Explorer program. The key limitation of open software is noted on page 57, 'It's fairly clear that one cannot code from the ground up in bazaar style.' This sentence refers to the theme of the essay. A bazaar is an open market where everyone is free to evaluate software and decide to use or improve it. A cathedral refers to closed, proprietary programming where the software is kept pure of outside influences and is developed in a small team, usually with a hierarchical organizational structure. The choice of comparisons is interesting, because the internalized rewards of working on open software are more akin to building a cathedral than to bustling in a bazaar. In a sense, Mr. Raymond's bazaar is also very cathedral-like in the best sense of that concept. The next essay, Homesteading the Noosphere, looks at the motivations of the developers and why open source development works. His basic analogy is to 'gift cultures' where people compete for status by the size and value of the gifts they can give others. This has long been true of elites. Since software developers are and feel like they are part of an elite, this is not surprising. His test of the concept is that credit for the work done is jealousy respected. Although Mr. Raymond doesn't say much about it, I suspect that the academic tradition of scholarly papers to advance knowledge is a fundamental experience and construct familiar to many hackers. Naturally, much knowledge advancement has failed to have immediate economic consequences in the past, and knowledge development occurred anyway. Anyone who has read the creativity literature knows that creativity is primarily its own reward for the joy of the task. That research is not referenced here. Mr. Raymond is not an academic, even though he thinks like one in many ways. The next essay, The Magic Cauldron, takes a look at the long-term economic consequences of the open software movement, and its implications for developing future software. His fundamental point is that 95 percent of all software has use value, rather than value as code that can be sold to someone else. Because of this, any software developer of code that has only use value would be foolish to give up the open source code benefits. He proceeds to provide very helpful examples, and posits future models for this. I suspect that in ten years, this essay will be considered the most important one in the book, while today the title one is. Share this essay with every executive and software development person you know! The final essay, The Revenge of the Hackers, is a brief memoir about the author's experiences since publication of his essay, The Cathedral & The Bazaar, and helps put his ideas into better context for their impact on others. If you are interested in becoming a top hacker, be sure to look in the appendix for the essay, How To Become a Hacker. This book raises many other fundamental questions that the author is unprepared to address at this time. Perhaps one of the most obvious is that with embedded microprocessors headed for virtually every product, should the designers of the products that will employ these microprocessors also use the 'open design scheme' structure? I suspect that they should. It is natural to go from there to consider business model development as another place where this structure would work. I'm sure you will come up with your own, better examples. Basically, what is described here is the paradigm for how to create better results by harnessing more minds. Normally, development results have been reduced and time to completion has been stretched out by increasing involvement. We seem now to have moved past that fundamental barrier . . . much like when we first passed the sound barrier with airplanes. Where can we go next? I think the answer is anywhere we want. After you read this book, please ask yourself how you could apply this development model to important aspects of your working and personal lives. You will have to become more open about sharing your ideas and concerns, but the payoffs should be tremendous!
Rating: 
Summary: Nothing new...
Review: Well, I agree pretty much with the only negative review I saw here...Linux and FreeBSD have been around for a while now, they're only recently getting popular and moving in the mainstream and everybody is jumping on the bandwagon. Microsoft bashing isn't new either, but somehow it's become the cool thing to do. Some of the essays are well written but as with the other reviewer I don't see why the author is as popular as he is in the community. The book is a good primer for the latecomers who want to join the hype and the circus.
Rating: 
Summary: Open Source - the big debate
Review: While the book is quite interesting, it is not well organized, and trails off at the end like an unfinished term paper. Raymond has become the spokesperson for the OSI (Open Source Initiative) and is now its president. The problem is that many of his arguments don't even stand up within the Open Source Community, let alone in the software world at large. While Open Source has been effective in creating a compelling OS as an academic endeavor, now that Open Source has gone "commercial", the arguments no longer hold water.
Even within the Open Source community many people are refusing to release their source code. This concept of development worked fine while students and enthusiasts were working collaboritvely on the Linux OS, but it will be interesting to see how this holds up as the community goes out and attempts to make money on their works. Open Source development only seems to work as long as those contributing don't intent to commercialize their offerings. None-the-less this book is a good read for anyone interested in the Open Source debate, as Raymond was the first to articulte the process and the ideals. Good food for thought.
| 
