5 comments about MySQL Administrator's Guide and Language Reference (2nd Edition).

1. The MySQL Administrator's Guide by MySQL Press is the ultimate reference for anyone installing, upgrading or maintaining the MySQL database server. I found this guide to be completely invaluable when using MySQL, even before I had downloaded the software. The Guide uses clear, easy to read, formatting which makes shell instructions stand out from MySQL statements. A detailed index takes no time to show you where in 600 pages your answer lies. And you can bet you'll find the answer in this Guide. Beginners beware, however, this is no introduction to MySQL. Readers should have a clear understanding of their system, along with experience of MySQL, although an insight into MySQL AB and MySQL's history is included in Chapter 1.

   As I began reading through this Guide, I couldn't help notice immediately how it sets itself apart from similar books. The MySQL Admin Guide has a detail which you will not find anywhere else. Such is to be expected from the company who make the software, and this book certainly shows the high quality of MySQL. After reading through this book, I can't help but agree with Kaj Arno (Vice President Software Engineering, MySQL AB) who is quoted on the back page; "'It is not possible to find a more thorough and more current reference in print, anywhere'". One of the best example I can make of this fact is in Chapter 2 which focuses on Installing MySQL. Not only does this Guide list all the option of a source distribution, all the ins and outs of installing MySQL on all likely platforms - Windows, Mac OS X, NetWare, Linux and other general Unix systems - this guide also deals with Upgrading and Downgrading the most recent version of the MySQL database server. And of course, to ensure that the entire knowledge is in print, Perl installation notes are included too. What other book covers the often troublesome installation process in almost 150 pages of detail?

   And that's only the second chapter. Throughout the book you're assured to find comprehensive information straight from the people who know it best. You may think that this book simply offers too much information, and for most people I would have to agree. It is unlikely to bother a system administrator how MySQL server optimizes the WHERE clause, or how to avoid table scans. Even if someone was interested in understanding something like this, they'd have the opportunity of looking at the MySQL Reference Manual online. So why buy the print version? The printed Guide not only allows for offline viewing, it also includes information which has not been included in the Reference Manual, such as how details are stored and the many feature of MySQL's MaxDB. If your not content with only having part of the story, you'll want to get this Guide.

   The MySQL Administrator's Guide is the ideal book for system administrators who want to get the most out of their MySQL server. With all the advice on installing, maintaining and administering that you'll ever need to know, this Guide by MySQL AB is ideal for those who long for a comprehensive printed reference.




2. This is a good book gives out the details in an easy to understand format.



3. Good stuff. But the MySQL Administrator's guide (2nd edition) and Language reference is out and on Amazon. That contains the same book in a later edition with the language reference on CD on top of it. Buy that instead.



4. This is an excellent book, but it is written for MySql 5. Check your version before buying.



5. Excellent delivery service and the condition of the book was new. The price was also excellent.

5 comments about Advanced CORBA(R) Programming with C++ (Addison-Wesley Professional Computing Series).

1. Don't wish to wade through book after book? This book would be the one to buy! The concepts are clearly defined and the code examples are fairly easy to follow. (The thermostat example grows too complicated at the end of the book to even comprehend all pieces - authors could use other smaller constructs to show the concepts.)

   The authors are well-versed in the topic and it shows in every chapter. There is no hand-waving on topics, as I have seen in other treatments of this subject.

   I've been a Corba programmer for the last 3 years and this has been my bible...

   Can't wait to see a second edition of this book from the authors!




2. Good book. Worth the money. There is a a lot of material here and it is pretty well organized. Some of the examples assume to much - they would be better if they showed complete code segements. If you needed to get one book on C++ and CORBA, this would be the one.



3. As the title states this is a book for advanced programmers. Not the kind of book I would recommend to someone looking to pick up a book and the learn from it. Might serve as an excellent reference source.



4. For my money, this book is worth every cent and more. The authors are knowledgable and articulate. If you know of a
   better book on CORBA, please let me know.....



5. This has to be one of the best CORBA books that I have read. It has helped me debug code and fix some really knotty problems. I found the exposition clear and easy to follow, and the index a useful tool. I don't think the authors intended it to be read cover-to-cover.
   
   If I am working on a CORBA project I alway like to have this book to hand.

No comments about Scratch Programming for Teens.

5 comments about The Definitive Guide to JasperReports (Expert's Voice).

1. I miss more Java code examples in the book, also it is too much an aseptic reference of the options of JasperReports, being really not a friendly or instructive book.



2. This book does not provide enough details about the JasperReport especially about how to use it. It also be lack of examples.
   
   I strongly recommand directly using iText for PDF file generating.



3. JasperReports is a great reporting engine which suffers heavily from its utter lack of useable documentation. I bought this book, written by JasperReports' author Teodor Danciu in the hopes of finally getting adequate documentation. Boy! was I disappointed!
   
   The book is an extremely superficial overview of the product; it's really no more than a glorified README file. Chapter 5 ("Large File Support") is a perfect case in point: The classes in the virtualization API are named, but nowhere is there any explanation on how to actually use them.
   
   It's quite unfortunate that Danciu has put his name on this poor excuse for a book. Luckily, I bought the PDF version, so I wasn't responsible for any trees dying...



4. This book is not what I expected, because there is not a single example, step by step, not even a basic one, that introduce you to the practice, is just like read an API documentation and that is all you get.



5. The name suggests that this is a guide to development of reports, using an open source reporting API. That said, with APIs being the exclusive domain of the coder ... why isn't there any code? $50 down the drain.

5 comments about Flexible Rails: Flex 3 on Rails 2.

1. The author goes into great detail on how to efficiently get Rails and Flex working together. The book is updated for the latest version of Rails as well as the upcoming Flex 3 release. I've found the book easy to follow along with and enjoy the author's humor spread throughout the book.
   
   As a developer I'm often tasked with making "things talk to each other". Typically if I can I'll use a tool like Flex Builder for a project and if I have a choice I'll pick Java, .NET or Ruby for the server back end - whatever is the best fit. This book only backed up my belief that Rails and Flex really do work very well together. I've learned a lot going through the code both on Rails and Flex.
   
   I also liked how the author is continually refactoring the application (called "Pomodo"), that is where your learning kicks into overdrive. He uses the Cairngorm framework and even RubyAMF. I didn't have any experience in either up until this point. Now I can say I do and it all fits together nicely.



2. I wasn't sure whether a mixed-technologies book would be adequate for both reading and reference, especially with two technologies. As both a software engineer and a moonlighting instructor this book was an easy read from the start. Mr. Armstrong explores both Flex 3 and Rails 2 with enough background information on both technologies to get a reader ready to code--and that was just Chapter...err...Iteration 1. The second iteration begins with coding (Hello World) and it doesn't stop. This is a must for your coding library and makes a great textbook for students who enrolled in courses geared toward building web and Rich Internet Applications.



3. This is a great book. Peter is the #1 expert in Flex + Rails.



4. I have used Flex for about a year and I have only dabbled in Ruby/Rails development. I have been curious how I might back a Flex front end with a simple service layer that isn't hard to create, maintain or host. So far I have only worked with Java/Spring/Hibernate backend services which can take a little while to build and integrate (Grails is MUCH faster).
   
   After about 100 pages I'm in interation 4 building an interesting RIA with a Rails backend that I can host on relatively inexpensive server if I wanted to. My only struggles thus far was getting MySQL going properly. But that was only because I forgot a step in installing it.
   
   If you have little exposure to Rails and/or Flex and you feel at home on the command line as well as you do in an IDE like Eclipse, this is a great "project" book for you. I'd say you probably want a primer in Ruby, Rails and Flex before you get going but it is pretty easy follow and has a lot of free professional advice from someone that has obviously been around the block a few times. Peter is very upfront about some things that he has done in the book that should not be considered "best practice".
   
   I am hoping to get some good insight how I might do something similar for Flex and Grails. Regardless, I am confident this is going to be a fun journey!



5. I found it best technical book till date but you should know Flex & Ruby before you can jump into this..

5 comments about CSS, DHTML, and Ajax, Fourth Edition (Visual QuickStart Guide).

1. I was looking for a book to get better acquainted with CSS and Ajax. I picked up "Visual Quick start Guide. CSS, DHTML & Ajax." From Peachpit Press. The book is a quick read and it efficiently provides a quick start guide as promised. I particularly liked the example based introductions for all topics covered. Also, I enjoyed the brief introduction the book provides on Web 2.0 and the way the authors define it.
   After going through it once you will probably keep it as a quick reference guide, although it is never too hard to find information on web technologies on the web. Overall I could recommend the book if you are not a client side developer and are in need of a brief and comprehensive look at CSS and DHTML. I cannot imagine client side developers being too impressed with the book though.



2. I looked through this book at a bookstore before buying and I was impressed with the idea of working through with visual examples about what could be done with different manipulations of code (something that is hard to quickly get on the web with many many clicks).
   
   In using this guide, I have though become frequently exasperated by the execution because of confusing examples, what I believe to be mistakes in the code examples in the text, etc...



3. A great book for beginners as well as a good reference tool for programmers as well. I bought this book for my 14 year old son who used it to teach himself. He said it was well laid out and has used it quite often.



4. This is a great book for learning CSS, DHTML & AJAX. I needed something quick to pick up this language and the book worked perfect.



5. While this book (Fourth Edition) appears to be another quality release from Peachpit, it is unfortunately plagued by typos (rather unusual for this publisher). Code simply will not run properly due to occasional errors (often replicated in both the inline code and the illustrative tables/diagrams) and filenames are frequently incorrect. In addition, the auxillary red spot color is a nice visual break from the typical black text at first but isn't always implemented properly and eventually feels distracting. However, the major concepts and methods are addressed and presented well in the text.
   
   Overall, probably not the best book to start off with from unless you also enjoy debugging the author's code as you go along. I'd wait until a 5th edition corrects all the typographical errors.

5 comments about The Art and Science of C: A Library Based Introduction to Computer Science.

1. I borrowed this book from library and believed I had made a right decision.

   Quoted from the book, Mr. Roberts have been teaching computer science for over 20 years, I'm not sure how long he has taught C language but I suppose this book is written in a way that he believes is most beneficial to the readers, based on his teaching experience.

   C is a cryptic and complex language, so the author teaches in a stepwise manner, he hides the complexity by introducing his private libraries and data abstractions. So the readers implement the functionality of C, which is independent from the complexity of C; once the readers have enough grasp at C, they may move on to explore the complexity of C.

   The author have done these with good intention because data types in ANSI C are limited in size, for example, the data type int is different from our perception of integer in daily life. The address operator & may be confusing as well.

   How did I use the book? I rewrited all the examples presented in book without his private libaries. I did the exercises in the book without his private libraries as well. Instead of copying all his codes and getting them work, I tried to make errors: for example, in the simple hello world program, omitted the preprocessor operator #, then read the error messages. I also tried to improve the efficiency of my algorithm.

   This maybe a good introductory book for people who have experience in programming in languages other than C since the syntax of C may confuse them, but owning it is not recommended.




2. I thought this was a wonderful beginners book. It gave me the basics and then allowed me to go on and try new things by myself. By the end I really felt like I could write my own programs in C.
   
   I only gave it four stars because I think five would have to be a textbook that really brought the information to life, while this one was rather dry.



3. I have read and worked through both of Eric Roberts books on C.
   Of all the programming books I have read, and there are many, his two are the best.
   
   My only regret is that he has not written books on C++.



4. This book is annoying with the way the author asks the user to write programs using his custom library functions, as opposed to the standard C commands. Because of this, I did not learn about scanf until probably the 7th or 8th week of the C programming course I was in. I feel like that alone warrants a 1-star rating. If you buy this book, you will be learning to program in "Roberts," not C.



5. I was frightened when I opened the book... The characters in the book look like a copied-material of a very very old 8-pin dot-printer output...

5 comments about Agile Database Techniques: Effective Strategies for the Agile Software Developer (Wiley Application Development).

1. Like many, we struggle to de-couple logic from data, and we pay the price every time we need to do substantial schema changes. Scott's approach is sound, however, like many who write on these topics, it lacks a certain degree of pragmatism that will let you take a big, complex system from ugly, embedded database queries to one with a clean, extensible persistence layer. Not that there's anything particularly wrong with the approaches outlined, it's just that it starts to feel like a "religion" and that makes any of these ideas hard to retrofit back into a complex system.



2. The book was well written and very easy to use. I found many insightfull thoughts as to the purpose of Agile development. If you are looking for a great book to guide you into AGILE development, this will do it.
   Drawbacks or missed points, yes this book has two flaws that I have to list. 1. the repeated use of the word Legacy and the very negative congnitation of the word. Older database will have many flaws, and we need to identify them. They will also have many objects and data patterns that are valid and efficient and should not be abandoned because its not todays effort.
   2. Agile and refactoring of tables does not address, production, zero down time, large volume databases. How do you refactor a table with 2 terabites of data and can not allow downtime. (medical)



3. This is very well written, enjoyable book, with few (if any) competitors. Given its agile sensitivities, it's perfect for a programmer looking for an overview of the whole data modelling she-bang, from use cases to impedance mismatch. Despite clocking in at 400 pages of fairly dense type, interspersed with various tables and UML diagrams, it's a breeze to read. It assumes a bit of knowledge of database technologies, but you don't need anything more than a nodding familiarity with SQL and basic concepts like normalisation.
   
   This book deals with a lot of issues related to using databases as part of agile modelling. The main message is that agile application developers need to think about persistence issues, and database admins need to understand agile development. The differences between data-driven and object-driven models are clearly laid out, and there's an excellent section on refactoring databases.
   
   The important thing about this book is not so much offering you specific solutions to problems, but alerting you to potential problems you might not even know exist, and explaining that you do have options in solving them. As well as introducing agile methods like TDD and refactoring, it also covers database issues like transactions, security, concurrency and object-relational mapping.
   
   Additionally, there is an emphasis on the organisational and political issues you might face in transitioning to agile methodologies, and it's very pragmatic in pointing out that some things that might be considered the preserve of an application developer, could be done in the database itself. The issues are presented at the same level of detail as those presented in the likes of The Pragmatic Programmer (but a different subject, of course). For more specifics, you will need to turn to the likes of Martin Fowler's Patterns of Enterprise Application Architecture, or to see specific technologies being used, Chris Richardson's POJOs in Action. I would definitely recommend this book before reading those.
   
   As someone with little knowledge of databases, I found this an excellent and unique resource to join up the dots when it comes to persistence and agile.



4. To be fair, the book title suggests that it is for the software developer, and not a database administrator. I thought that it had a good overview of agile related items. Although it was probably not as useful for software developers who might have more exposure to the agile methods. From a DBA point of view, I thought it was a nice overview because agile is not typically used in DBA teams.
   
   As far as specifics relating to databases, I thought it could have had more real-life scenarios and suggestions on how to deal with them. Some of the ideas presented were just too unrealistic for my liking.
   
   That being said, there are a few good ideas in this book. It was a quick read too. So if you are a DBA who has no idea of agile, it might be something to start with.



5. If you are an application developer that has ever worked with a system that is difficult and convoluted because of fear of touching the Database then you owe it to yourself to read this book. This book will provide you with the insight and techniques to make changes to your Database with confidence.
   
   I also recommend Refactoring Databases: Evolutionary Database Design (The Addison-Wesley Signature Series) for those who seek details on how to implement the topics discussed in "Agile Database Techniques"

5 comments about AI Game Programming Wisdom (with CD-ROM) (Game Development Series).

1. "Artificial Intelligence" means different things to different people. One useful application is the control of nonplayer characters (NPC) in video games. This is the first book to address this field. Like any collection of papers, it is uneven and does not systematically cover the subject. It should be read in conjunction with a traditional AI text, such as Murphy "Introduction to AI Robotics", Russell and Norvig "Artificial Intelligence: a Modern Approach", Tom Mitchell "Machine Learning" or perhaps Bruce Blumberg's forthcoming "Synthetic Characters".

   I teach AI at DigiPen Institute of Technology and made this one of the required books. It is good in showing which techniques are most useful in games and what you need to consider when designing your AI. Some papers are overly general and some are too specific. That's probably unavoidable, but game programmers can pick and choose the most appropriate ideas. Unfortunately, some of the better introductory articles on A*, finite state machines, flocking and fuzzy logic are not in this book but in "Game Programming Gems".

   Once you understand the basics of AI, this book can save some major headaches by helping with the selection of an appropriate architecture. The CD has source code to help you get off to a good start. Reading the appropriate articles will let you anticipate problems before they happen and design around them. Professional game programmers will likely find at least one technique that pays back the cost of the book.




2. Published by the same folks who brought you Game Programming Gems (and edited by one of the more prolific AI authors in that series), AI Game Programming Wisdom provides a wealth of real knowledge by actual game programming professionals, not professional authors. As a game programming professional, the number of game programming books that sit on my shelf is fairly small. Most have nothing interesting or meaningful to offer beyond rudimentary descriptions and concepts.

   AI Wisdom is definitely a cut above the rest. The topic selection is intelligent and relevant, and the articles are all of a consistent quality and polish. I've already referenced articles several times when writing production code, and several co-workers have borrowed it when they had a particularly tricky problem to solve. This is simply a must-have resource for any professional AI programmer, period. Or, if you're an amateur or hobbyist looking to see the tricks and techniques professionals use, then this is a book you absolutely can't afford to miss.




3. Being in the game development business, I am always on the lookout for new and different tricks, techniques and strategies. When most programmers go to the lectures, panels and roundtables at the Game Developers Conference, we are looking to pick up this same sort of material... we share ideas and approaches - but rarely get the chance to get down to the code details to make it easy for us to implement those ideas into our own work. This book makes that possible.

   Along the lines of the other "Gems" series of books, this collection is filled with ACTUAL techniques and code chunks that are used by some of the top professionals in the industry. Just flipping through the list of the contributors to the book is like going around the room at one of the AI roundtables at the GDC... in fact, Steve Woodcock and Neil Kirby are 2 of the "3 AI guys" that RUN those roundtables! (The 3rd being Eric Dybsand who has contributed to the "Gems" series but not this title.)

   Many books on game development are informative. This one is actually USEFULL. I have personally adopted Steve Rabin's source code from the section "Implementing a State Machine Language" into my own game and it has saved me many hours of development and improved the readability and understandability of my code for the rest of the team. Just that section alone has netted at least a 1000:1 return on the cost of this book. Other sections have given me a different approach on how to handle the economic strategy layer that I could have come upon myself... but was able to implement a lot quicker than if I had done it myself. It was definately worth the price.

   Are any of these sections worth the purchase price for YOU? I suppose that depends on how much you value you your time. Once you equate the cost of the book to the man hours you save, it's a no brainer!




4. This is the best book in my library.
   Write by professionals, with usefull techniques and well explained details of almost every cool aspects of AI in the game programming world.



5. It's hard to find good information about game programming and design. The trouble is that people working in the industry have an incentive to keep their techniques secret -- they don't want their competitors to learn them. The people who aren't in the industry can write about games but don't have the experience to back it up.

   Game AI Programming Wisdom gives us wisdom from people who have worked on real games. Each section is a short explanation of a particular problem (like pathfinding, tactical reasoning, or pattern recognition). Since they're short and independent, you can pick the section that applies to the problem you're trying to solve and read that without having to read everything in order. However, each section is written by a different person, so if you try to read the book straight through you will be distracted by the change in writing styles and level of detail.

   I'm quite glad to see this book. It's actually the first game programming/design book that I purchased. (I'm quite picky when it comes to books. I'm sure Amazon doesn't like that.) Most of the game books I see go into low level programming details. This book teaches you the principles and techniques that will be useful for more than the specific problems they cover.

3 comments about Open Sources 2.0: The Continuing Evolution.

1. This collection of essays on the open source movement could be called a second edition to the book "Open Sources: Voices from the Revolution" that was published in 1999. That book spent much space trying to argue that the open source movement was legitimate and here to stay. That argument has long since been settled, so this book takes up the current and future trends of the open source movement. The essays can be read in any order, and depending on your expertise, some may not be of any real interest to you- for example the open source biology essay might not be valuable to someone interested in network security. However, all essays are written to be accessible to a wide audience in spite of that fact. For example, I have no background in biology whatsoever, but I still found the essay on open source biology an understandable and interesting read. I particularly enjoyed the essay on the open source paradigm shift by Tim O'Reilly. His premise is that free and open source developers are in much the same position today that IBM was in 1981 when it changed the rules of the computer industry, but failed to understand the consequences of the change. This allowed others, Microsoft in particular, to reap the benefits. O'Reilly concludes that existing proprietary software vendors are no better off, playing by the old rules while the new rules are reshaping the industry around them. Another favorite of mine was on the commoditization of software in which it is explained that this process has been driven by standards, in particular by the rise of communications-oriented systems such as the Internet, which depend on shared protocols, and define the interfaces and datatypes shared between cooperating components instead of those components' internals. There are also two fascinating essays on the open source movement in China and India, neither of which was really a factor when the first edition of this book was published six years ago. I would recommend this book to anyone interested in where technology might be headed in the future, not just those who are employed in the tech industry. I notice that nothing about the contents of the book is currently shown by Amazon, so I show the table of contents here for the purpose of completeness:
   The list of essays are:
   1. The Mozilla Project: Past and Future by Mitchell Baker
   2. Open Source and Proprietary Software Development by Chris DiBona
   3. A Tale of Two Standards by Jeremy Allison
   4. Open Source and Security by Ben Laurie
   5. Dual Licensing by Michael Olson
   6. Open Source and the Commoditization of Software by Ian Murdock
   7. Open Source and the Commodity Urge: Disruptive Models for a Disruptive Development Process by Matthew N. Asay
   8. Under the Hood: Open Source and Open Standards Business Models in Context by Stephen R. Walli
   9. Open Source and the Small Entrepreneur by Russ Nelson
   10. Why Open Source Needs Copyright Politics by Wendy Seltzer
   11. Libre Software in Europe by Jesus M. Gonzalez-BarahonaGregorio Robles
   12. OSS in India by Alolita Sharma and Robert Adkins
   13. When China Dances with OSS by Boon-Lock Yeo, Louisa Liu, and Sunil Saxena
   14. How Much Freedom Do You Want? by Bruno Souza
   15. Making a New World by Doc Searls
   16. The Open Source Paradigm Shift by Tim O'Reilly
   17. Extending Open Source Principles Beyond Software Development
   by Pamela Jones
   18. Open Source Biology by Andrew Hessel
   19. Everything Is Known by Eugene Kim
   20. The Early History of Nupedia and Wikipedia: A Memoir by Larry Sanger
   21. Open Beyond Software by Sonali K. Shah
   22. Patterns of Governance in Open Source by Steven Weber
   23. Communicating Many to Many by Jeff Bates and Mark Stone
   Appendixes :
   A. The Open Source Definition
   B. Referenced Open Source Licenses
   C. Columns from Slashdot



2. Open Source Software (OSS) has radically redefined the landscape of the software industry and the Information Technology field. As much a mindset as a methodology, there are many elements of OSS that draw some of the deepest thinkers of our field. You can find some of those essays in the book Open Sources 2.0 - The Continuing Evolution, edited by Chris DiBona, Danese Cooper, and Mark Stone. There's a little something here for everyone...
   
   Contents:
   Part 1 - Open Source - Competition and Evolution: The Mozilla Project - Past and Future; Open Source and Proprietary Software Development; A Tale of Two Standards; Open Source and Security; Dual Licensing; Open Source and the Commoditization of Software; Open Source and the Commodity Urge - Disruptive Models for a Disruptive Development Process; Under the Hood - Open Source and Open Standards Business Models in Context; Open Source and the Small Entrepreneur; Why Open Source Needs Copyright Policies; Libre Software in Europe; OSS in India; When China Dances with OSS; How Much Freedom Do You Want?
   Part 2 - Beyond Open Source - Collaboration and Community: Making a New World; The Open Source Paradigm Shift; Extending Open Source Principles Beyond Software Development; Open Source Biology; Everything Is Known; The Early History of Nupedia and Wikipedia - A Memoir; Open Beyond Software; Patterns of Governance in Open Source; Communicating Many to Many
   Part 3 - Appendixes: The Open Source Definition; Referenced Open Source Licenses; Columns from Slashdot; Index
   
   As with all compilations from various writers and authors, it's not possible to have all the articles flow with the same voice and pace. And really, they shouldn't. You're looking to get a wide array of opinions and insights, not a blended mind dump from a single writer. Conversely, you'll find that some of the articles resonate with you, and others have you moving into scan mode to get to the next one. If you keep that in mind as you're working through the book, you'll get a lot more out of it.
   
   For me, there were two areas that were enjoyable and valuable. The story of how Wikipedia went through growing pains and worked through rules and culture was interesting. Likewise, the story of Slashdot and how it got to what it is today is insightful. I still don't care for the site, but you can't argue it's effect in the technology world. The most thought-provoking essays for me revolved around the commoditization of software. Coupled with a different book I recently finished, I realize that certain software vendors are in a very precarious position, and they are following the same path that has led others to destruction as they attempt to hold on to what doesn't work any more. Those essays would have been worth the cost of the book alone to me...
   
   If you're part of the OSS movement, or if you're trying to understand how it will affect your business, this is a good book to read and ponder...



3. Chris DiBona, Danese Cooper and Mark Stone edit Open Sources 2.0: The Continuing Evolution, a collection of essays from today's tech leaders exploring open source's impact on the software industry. Open source is network- enabled distributed collaboration that holds the potential of changing not only online business itself, but the nature of collaboration. Articles address the future of open source in essays that cover not just the developing technology but the participation of international communities. A 'must' for any interested in open source who would understand its ongoing evolution and potential.