5 comments about Computer Algorithms C++: C++ and Pseudocode Versions.

1. This book is a textbook for a Computer Science course "Analysis of Algorithms" in Queens College, CUNY. The entire class suffers, because the book isn't readeable. The language isn't English!

   Authors strive to make even the simplest algorithms difficult to understand. The code examples have almost no comments and are typed in a messy disordered fashion. Mathematical analysis requires huge background in analytical mathematics and prior knowledge of everything it talks about. Proofs of theorems are not clear. Where the authors state something like "... clearly this is so-and-so... " the argument isn't even logical!

   Very often they don't even describe an algorithm - they just say "the algorithm is presented by the code on page ..." (this page is usually 10 pages away). The number of typographical mistakes is enormous. The examples are based on bizarre numbers and data structures.

   Don't ever ever ever consider buying this book! For college professors: please don't use this book as a textbook in your class unless you want to have a "D" average at the end of the semester.




2. I'm a student at department of Computer Science and Information Engineering, National Taiwan University.We took the course "Algorithms",and used this book as a text book.After a semister learning, i never heard any good comments for this book.The most word given to this book is"This book can make easy to hard!"We'll never choose this book as a text book again.



3. This book discusses algorithms in computer science but does integrate enough C++ code into the text, in spite of its title. Also, a lot of the code still has remnants of C philosophy, such as #define statements, in spite of the authors frequent use of "class" in their code. Buy this book with caution, as it is very expensive.



4. Don't waste your money on this text, it is rotten. I had it for a class and found this book to do very little in aiding the learning process due to its lack of any sort of coherent explaination. I ended up purchasing another text and used it from then and until now, after college.

   this is the only textbook i have ever sold back after the semester.




5. ... If the primary complaint against this text is that the authors have not provided enough C++ source code examples for the types of algorithms explained, take a look at the price tag. At a list price of [price], one can logically deduce that this text is for a university audience, emphasizing the theory behind the algorithms, as well as the synthesis it takes for you to generate modified versions from the templates presented. If you are looking for a more "how to"-oriented text (you know, the kind that "spoon feeds" you) with excessive source code examples, you definitely should look for another text. Nevertheless, I consider this book to be both highly appropriate and effective for its intended audience.

5 comments about Visual C++.NET: How to Program.

1. Much like others have said he spent far too much time on areas in which are less important atleast in my eyes
   
   While this book gives you a basic understanding in VC++ I found that it spent far too much time in the commandline
   programing (MC++) when you could teach from the start learning doing it via text boxes/lables which would condence alot of the
   reading making it less balky. Over 1/3rd of the book was on MC++ commandline programming! This book was also intended for
   college courses and answers to the questions are not answered for those of us learning on our own which is a real downside
   and made me skip ALOT of the questions at the end of chapters.
   
   This book doesn't get into real detail about data structors which is an important aspect of programming in general which made me disapointed..
   
   As Jody Blau said:
   "Also, I found that its style of giving a few pages of code, followed by a few pages of explaining the code, could have been used much more effectively. Often the "explanations" involved simply stating "what" they did and not "why". "
   is So true.
   
   
   All in all I feel this book is alright but I'm sure theres better out there.



2. This book is a very nice choice for learning .NET 1.1 programming with C++, provided that you have enough knowledge of the C++ language itself (as always is the case when programming with C++ in some platform).



3. I found that this book gave me good general information on VC++.NET but not quite enough. When going through the book I tried to write the sample pieces of code as I was going and there was just not quite enough information on each of the samples for me to write it with out having to go and copy the code from the examples. Also it wasn't clear what the project settings should be set to. Eventually I figured them out but it just wasn't quite enough.
   
   I have been a C++/MFC Developer for 6 years and am finding the transition to .NET quite difficult. This book has not been the help that I was hoping for. I know the programming concepts but actually getting the proper syntax to work for simple things is taking quite a bit longer and the book does not have what I need.



4. I think this is a great book. I learn best in a "classroom" environment while doing lots of hands-on exercises. This book meets both of these needs. The material is presented in a logical manner that makes sense and the book is inundated with example code for hands-on work. When I received my book, there was some problems with some of the pages. I contacted the Deitel company and was impressed with how quickly and professionally they responded to my problem. When I have a need for books on programming, they will be the place I look first for resources.



5. I find Deitel to be a good author. I've used this book, C#, Visual Basics 6.0 and others. They are all well written and sometimes you can learn more from the Deitel book stand alone then in a college course. Note all Visual Microsoft software have free downloads.

5 comments about C++ Strategies and Tactics (Addison-Wesley Professional Computing Series).

1. For the reviewer below that stated that this book is dated because it does not cover templates could not be farther from reality, as apparently he has not read the book nor has he looked at the table of contents. If my eyes are still functional, this book has two chapters consectutive dedicated to to templates, chapter 7 [Templates] and 8[Advanced Templates]. This book is easy to read and for the novice wanting to get up to speed on the syxtax of the language and more importantly when and how to use each contruct of the language, this book has no equal except two other books. The books are Kayshav Dattatri's C++ Effective Object Oriented Software Construction and James O. Copliens Advanced C++: Styles and Idioms from Prentice Hall and Addison Wesley respectively. This book is not even 300 pages which allows you to read it again and bolster what you vacumed on the first pass and ready for instinctive mastery for the second and third passes if you are really ambitious. The discussion on smart pointers is informative and will assist you in your way to patternizing COM code. This book is for all experience types and serves as a perfect desktop reference guide for C++ masters alike. With this book and the two mentioned above, plus the C++ IO Streams Handbook by Beale, there are no other books you should refer to, probably including Stroustrup's.



2. Once you have good knowledge of the basics and know basic OOP, you should start reading this book. This book has lots of good information reguarding design and loop holes all new programer can commit. But its best feature is that its so easy to understand.



3. This was the original book of C++ "idioms and traps", full of practical details such as where to use virtual destructors and the correct way to write the copy constructor and assignment operators. Then Scott Meyer's book came along with such sparkle and wit that I put this book aside, even though they pretty much covered the same ground. The second edition of Meyers' book covers the new ANSI standard - and while this was needed, it has a fair amount of "code lawyering" and is no longer a breeze to read. I'm glad I held onto the Murray book to cover the basic concepts, even though it's slightly out of date.



4. You have to know that its target audience is beginner C++ programmers. I am somehow experienced with C++ programming and by looking at the excellent reviews this book got, I had high expectations when I purchased it. I have been disappointed to only have found maybe 2 small advices that I did not know. Reading over 250 pages for a so small reward has been disappointing. If you consider yourself good in C++, my advice is that you should skip this one.



5. Like Tom Cargill's C++ Programming Style, this is another widely-recognised classic of the genre which has lost some of its immediacy with the passing of time.
   
   If you're familiar with the works of Scott Meyers and Herb Sutter, then you will probably not find much here that you don't already know (although this clearly predates some of their output). But if you're still fairly new to OO, I recommend this highly as your first non-introductory book. It's got a much more cohesive feel than the Effective C++ and Exceptional C++ books, and unlike the Cargill book, it's sufficiently modern to have covered templates. Bear in mind, though, that the 'advanced' templates chapter is about writing a linked list class. Solid data structure stuff for sure, but not what a C++ practitioner would consider advanced these days.
   
   You can also find lots of solid OOP advice, although you may find it similar to the OOP wisdom dispensed in other C++ of the same vintage. There are some suggestions on 'reusability', although they're more concerned with memory management, and feels more like optimisation. That's not to say that it isn't interesting and accessible, though.
   
   There's a brief introduction to exceptions, but at the time the book was written, they had only just appeared in the language. Likewise, there's nothing about namespaces here.
   
   My 4-star rating takes into account that you can obtain this book cheaply and the material is presented in a clear, readable fashion. If you're already an experienced object oriented programmer, you can safely bypass this book and go straight to the Meyers and Sutter books. If you're not, then this is a good place to start the journey to more advanced work.

5 comments about The C/Unix Programmer's Guide.

1. well, this book has proven handy for reference and review, but i would certainly NOT recommend it. the author repeatedly used obscure functions(imho) that were prone to bugs, and he introduced totally new concepts in breif 10-word sentences only to use them all-too-frequently in most examples following. yes, im a 16 year-old, shift-key-fearing mexican, but i've seen good code, and mr.bacon's code doesn't fool me. if you want to take full advantage of this book, read the ENTIRE THING in one sitting so every little concept sticks with you throughout, and don't you dare approach a computer without reading a book that emphasizes on structure, organization, and clean, effective code first



2. The C Unix Programmer's Guide was the only book I could find that provided useful background information as well as thoughtful, applicable coding examples. What impressed me most is the fact that all the information found in the man pages on C as well as further insight was combined into an easily readable and searchable format. As a student of computer science, I was familiar with Borland/Microsoft C++, but I had no previous experience with C or Unix. This book helped me get an A (one of three) in Operating Systems! While my classmates struggled on assignments, I was able to find exactly what I needed to complete the assignments on time. I truly believe that without this book I would not have performed nearly as well. Thank you Mr. Bacon for writing such a great book!



3. This book did an amazing job of introducing many important concepts about C, and C in UNIX.
   
   The description of the material is very clear, and the examples are well thought out.
   
   If you're looking for a beginner/intermediate text on C and UNIX, this is THE book to get.



4. I wish this had been my First C programming book. It teaches all the basics required for you to start some worthful programming under *nix. It doesn't go into as many details for e.g., as given in 'C programming: A modern Approach by King but it still gives many details on what things are. It starts with basics of Unix and provides a lot of information on the C development tools in *nix. A very good starting point for learning programming in C under *nix.



5. I have seen good C programming tutorials, and this is not one. It isn't very descriptive. It will introduce you to new library functions and not give a good explanation on it, and then it rarely describes the code snipets. The C Primer Plus by SAMS is far superior to this for learning C. Having said that, this book is decent in its coverage for UNIX system calls with C, in that it is easier for a beginner to understand the code snipets in this book as compared to other books I have seen. Other books I have seen require you to at least already be an intermediate C programmer, and use examples that require you to study the complex code snipets before you can begin to understand what is being accomplished with the system calls.
   
   The author/publisher hasn't updated this book with regard to hardware, and it talks about 286's, 386's, 486's and Pentium processors. It considers 16 bit and 32 bit processing, and it puts too much emphasis on 16 bit, when every compiler I have seen for C is 32 bit. It even gives suggestions based on 16 bit technology. It references DOS, and if anyone is still running DOS, they shouldn't be reading a book about programming. They should be reading about survival skills and moving to Montana and building a bomb shelter.
   
   So, to learn C, this isn't a good book. If you are dealing with the C/UNIX environment and are a beginner, the end of this book is decent for understanding system calls, as long as you already understand C from some better, more up to date source.

5 comments about Visual C++6 for Dummies.

1. If you already know C++ and want to learn to make programs that run in the Windows GUI instead of a command line, this book DOES NOT cover that. The most advanced example program provided runs at a command line ! If I had known that, I would not have purchased this book. The book barely touches on menus, buttons, etc, and does not cover how to write a complete Windows program that uses the GUI.

   If you don't know C++ at all and want to learn it, this book has lots on C++, but there are much better books out there for learning C++. The coverage of C++ in this book is not sufficient to teach it to someone who is learning it for the first time.




2. This book is pretty good on C++ syntax, but doesn't do much on actually getting into the MFC and Windows programming side of things. I would highly recommend Sam's Teach Yourself Visual C++ 6.0 for learning the basics of MFC programming.



3. I bought this book with the notion of learning Visual C++ 6.0 in my spare time. I was very disappointed. There are a lot of examples but some did not compile. I worked every example in the book but I do not see how some of these examples fit into the big picture. The book may have been better if the author had chosen 1 specific example and then built upon that example to give you a real-world application. The examples in each chapter had nothing to do with the examples in the chapters before it. The author just shows you several different ways to accomplice the same thing.



4. This is undoubtedly the worst C++ book I have seen. It spends so much time being cute and funny (well TRYING to be funny) that it fails to teach the material. It is broken up into many little incomprehensible parts. Each part has a name that does not tell what it is about because the authors are trying to use silly little puns for titles. Nor does the order of the parts contribute to learning anything.
   After reading this (well trying to read it) I was more confused than when I started. Stay away from this one at all costs. A better choice is Beginning Visual C++ 6 by Ivor Horton.



5. Ok. i know its called "for dummies".... and i dint really consider myself one, until i dropped $29.99, but, i looked at the first few chapters, and it look OK.... I thought id get much more "Windows programming" out of it

   i got a bit tired of :
   "see me feel me touch me print me..."
   "smooth operator"
   "holy debugger batman, it works... etc...

   A bit to bubble-gummy for me AND, as was mentioned before:
   What About Windows ???? ... id didn't buy it Strickly for c++, it said "VISUAL c++"... maybe if it had been called "Visual c++ console apps", (which is what it is) i would have (should have), left it on the shelf.. maybe its my fault... i guess when i think visual c++, i think sdi, and mdi classes...OH... maybe i am a dummy, after all

   I was NOT amused, nor very happy...

3 comments about Algorithms Sequential & Parallel: A Unified Approach (Electrical and Computer Engineering Series).

1. I'm coauthor, so I'm not unbiased. Having said that....
   
   The dominant textbook in the field of computer algorithms is Introduction to Algorithms, by Cormen et al. This is a very fine book. However, we have written Algorithms Sequential and Parallel in a very different style, which we feel will give significant advantages to many who use our book. Points of difference between these texts include the following:
   
   1. Algorithms Sequential and Parallel has a unified approach to the presentation of sequential and parallel algorithms. Students of 21st Century computing will need to learn parallel algorithms, which are often closely related to their sequential analogs. Ours is the first algorithms text to integrate presentation of sequential and parallel algorithms so that readers can understand their relationships. This integrated treatment also frees the instructor from the common practice of spending most of an algorithms course on the study of sequential algorithms, with the last 2 or 3 weeks devoted to parallel algorithms - a practice that may mislead students into thinking that parallel computing is still the immature specialization of researchers, rather than a core technology for the 21st Century.
   
   2. Algorithms Sequential and Parallel does not compete with Cormen et al. in the scope of topics covered. The Cormen et al. text, whose 2nd edition is well over 1100 pages, seems designed for at least a year sequence in the study of algorithms. By contrast, Algorithms Sequential and Parallel, 2nd edition, is under 400 pages. This makes it suitable for a one-semester study of algorithms, appropriate for many undergraduate and first- or second-year graduate programs; also, it makes Algorithms Sequential and Parallel significantly less costly.
   
   Algorithms Sequential and Parallel discusses mathematical tools used in the analysis of algorithms, a variety of sequential and parallel models of computation (including the RAM, PRAM, linear array, mesh, hypercube, pyramid, mesh-of-trees, and coarse-grained models), fundamental algorithms (including broadcast, semigroup computations, parallel prefix, sorting, searching) and their sequential and parallel implementations, paradigms such as recursive divide-and-conquer, and algorithms for a variety of applications areas (matrix operations and a variety of other numerical problems, computational geometry, image processing, graph problems, etc). Each chapter concludes with exercises at varying levels of difficulty.
   
   Note that a disinterested reviewer gave the first edition of Algorithms Sequential and Parallel a rating of 5 stars (out of 5) in SIGACT News 34 #2, June, 2003, pp. 3-5.



2. Have you been trying to find a way of to integrate the presentation of sequential and parallel algorithms? If you are, this book is for you! Authors Russ Miller and Laurence Boxer, have done an outstanding job of writing a great book on how to employ a philosophy of presenting a paradigm, such as divide and conquer, and then discussing implementation issues for both sequential and parallel models.
   
   Miller and Laurence Boxer begin by introducing the concept of asymptotic analysis.
   Next, the authors explain the Python programming language to write scripts. Then, they focus on fundamentals of induction and recursion. The authors continue by presenting the Master Method, a very useful cookbook-type of system for evaluating recurrence equations that are common in an algorithms-based setting. In addition, the authors next present an overview of combinational circuits and sorting networks. They also introduce fundamental models of computation, including the RAM and a variety of parallel models of computation. Next, the authors focus on the important problem of matrix multiplication, which is considered for a variety of models of computation. Then, they introduce the parallel prefix operation. The authors continue by introducing pointer jumping techniques and show how some list-based algorithms can be efficiently implemented in parallel. In addition, the authors next present the powerful divide and conquer paradigm. They also focus on two important application areas, namely, Computational Geometry and Image Processing. Next, the authors focus on fundamental graph theoretic problems. Finally, they cover sequential algorithms for polynomial evaluation and approximation of definite integrals.
   
   Due to the fact that authors of this excellent book present design and analysis of paradigms for sequential and parallel models, the reader will notice that the number of paradigms that can be treated is limited. But, that limitation is of no consequence when compared to a traditional sequential algorithms text.



3. The book represents a very decent approach for a transition from the sequential algorithms design ( RAM model ) to parallel algorithms for different models of parallel machines( not only SMP for which most of the software engineers get accustomed ).
   
   The book is an introduction for a person with a good background in a sequential algorithms design. The proof of the Master Theorem is somehow overcomplicated - it would have been better if there had been a sketch of the proof before the authors delve into the mathematically rigorous part. Before reading the proof in this book I recommend to read a proof of a simplified version of the Master Theorem as given in "Algorithms" by Dasgupta, Papadimitriou and Vazirani - it takes less than a page compared with 11 pages for the complete case in this book.
   
   I first came across the first edition's translation on Russian nearly 2 years ago ( the author's site says it was translated in 2007, but actually it was in the first quarter of 2006 ), then I bought the original 2nd edition - the book worth it.
   
   P.S. I've found nothing about Python language, as one of the review says, the authors use easily understandable pseudo-language. The book is not a cook book with code - this is virtually impossible for such a type of book as an algorithm realization heavily depends on a parallel machine architecture.

5 comments about Scientific and Engineering C++: An Introduction with Advanced Techniques and Examples.

1. I found this book to be very good, except for a few unnecessary parts. A lot of what the book covers (i.e., "scientific & enginnering") doesn't overlap my problem domain, and the Fortran/C intro sections were skipped since I already knew C++. It would have been better if the Fortran/C sections were put into different books. However, the rest of the book was excellent; even the stuff I didn't use right away was intellectually stimulating.

   This book should be bought by every serious C++ programmer. Barton and Nackman show several *excellent* examples of more advanced template usage than the boring old "generic container".

   For those of you who are more familiar with advanced template programming, the "B&N trick" gets its name because it's in this book.





2. I was first interested in this book for its implication of the title, scientific computing (whatever it is). However, I must say I was pleasantly surprised to learn that the book is not just relevant for the implied target audience, but also for those who need a good introduction to OOP with C++.

   What makes this book great for learning OOP is that it is rich in concrete examples that are relevant for people who have worked in science or engineering. Many OOP books take more abstract approaches, and often the relevance of discussions for the practical situations is not clear. It is not the case with this book.

   Another thing I like is the quick and concise introductions of C++. I think the authors do a great job of summarizing "do's and don'ts" of C++ by extracting the information in indented, bullet style lines throughout the book. Other C++ books are just enormous and often it is hard to find relevant information.

   I would guess the drawbacks of learning from this book is that if you do not have any background in science or engineering, you might have harder time understanding some examples in it. Also, the book is somewhat outdated in terms of coding practices (pre-Standard Library, etc.).

   In any case, the superb introduction to C++ OOP is in this book, which mostly remains unmentioned when people talk about good C++ books authored by other prominent authors. This one definitely deserves better recognition.




3. Barton and Nackman is probably the best advanced C++ book I have read. It covers the basics of C++ programming for FORTRAN and C programmers, then dives into more advanced material. The book discusses many important design issues, such as how to represent and take advantage of name, structure, and function commonality. Several of the later chapters build extended examples making use of advanced template techniques. One chapter develops in detail a family of array classes, another presents classes for smart pointer functionality. Though this book predates the standard template library, it discusses the use of iterators to provide sequential access to data stored in classes. My favorite chapters build a family of template classes to implement algebraic categories, e.g. groups, monoids, rings, and fields, and a set of classes to implement some rudimentary symbolic computation capabilities through function objects. The use of templates in the later chapters is truly advanced and it is fascinating to see many of the tricks templates allow you to perform.

   My only gripe with the book is its age. It predates the ISO/ANSI C++ standard and the standard template libraries. It would be interesting to see how the authors would incorporate these recent advances into their treatment of advanced C++ programming.

   Despite being a book for scientists and engineers, Barton and Nackman should be read by everyone doing serious C++ programming. Highly recommended.




4. It's unusual for a book on scientific computing to gain currency in mainstream software development, but a small number of C++ authors in the know have been recommending this since its publication, and rightly so.
   
   Skim read the first 300 pages, which introduces C++ to Fortran and C programmers, without being too interesting, with the exception of the illustration of a Fallible class, which is like Haskell's Maybe. It's a neat use of templates, which has nothing to do with typesafe containers of T.
   
   Fortunately, the rest of the book is in this vein, providing a very thorough introduction to object oriented design, using scientific examples. Don't think you need to read another introduction to OOP? No problem: the applications include modelling algebraic structures to provide mixins that provide + and * operators, function objects, wrapping C and Fortran libraries (e.g. LAPACK), implementing arrays and matrices, and an SVD solver. All good solid scientific programming, and all of which makes use of templates (including an appearance of the Curiously Recurring Template), in as elegant a way as the earlier implementation of Fallible.
   
   In particular, the authors make excellent use of the ability to use non-type template parameters. These were introduced into C++ as an optimisation so that library designers could know at compile time how large a container was - here, they're used to implement dimensional analysis, to provide compile time safety when multiplying and dividing quantities (e.g. speed and time) with units. This exemplifies the authors' use of templates - creative and eye opening, but not too baroque. In these pages you will see the beginning of the major direction taken by C++ in recent years - template metaprogramming.
   
   How interesting you find it may be proportional to how numerically nerdy you are, but whatever your interests in matrices, technically, this provides an essential introduction to advanced template usage. You'll find the transition to the material in Generative Programming or Modern C++ Design much easier if you digest the template usage here. And arguably, the resulting code in this book is at a sweet spot of functionality, readability and maintainability, compared to the more arcane representations in those later books mentioned above.
   
   Being a scientific computing book, it's a tad pricey compared to some others that might be on your reading list, but it's still well worth your (or your company's?) cash.



5. I work mostly in fortran and a little in C, so it was nice to find a text that approached things from the perspective of learning a new language, vs. learning my first language.
   
   The only downside is that the text is a bit dated and could benefit from a new addition.

5 comments about A First Book of C++, From Here to There, Third Edition.

1. C++ is the most difficult programming language to learn, yet Bronson does an excellent job in introducing topics painlessly. This book progresses in a very smooth fashion from topic to topic, and if the reader works all exercises at the end of each section, the concepts will be firmly grasped. Be careful, though, because this book does have quite a few typos, but they are easy to spot since the understanding of the material makes them obvious. The only drawback can be that not all the exercises have answers in the back of the book. Other than that, I would highly recommend this book to someone that wants to understand C++ and get a general knowledge of it, bearing in mind that this book will not make you an expert.



2. I would of never bought this book but it was for a class. Mainly focuses on C and then gets into C++. However my class never made it to the C++ portion where the author introduces OOP and classes. According to my professor, this is a two semester book. However, I learned quite a bit from this book and I already was familar with C and C++. I would recommend this book to anybody who wants to learn C and C++. However this book is not going to be very helpful for Visual C++ topics but still a good overall starting book on C/C++.



3. This book is very clear, well-organized, and easy to read. The author does an excellent job of explaining programming concepts instead of relying on diagrams to let us know what he's talking about. The sample code is easy to follow. Best of all, the exercises are carefully chosen so that they each represent a unique challenge. You will not get bored or lost in this book. My one complaint is that it doesn't say much about the String class or how to deal with string input (e.g. the common problem of the user entering more characters than you have room for).



4. After struggling with another C++ text I was lucky enough to come across this one. It's very easy to understand provided you didn't fail middle school English and have a decent knowledge of math.
   
   Bronson has saved "average Joes" like myself from pain in programming by making an easy-to-understand volume of C++. Even though it is unlikely I'll ever write another program in any language after taking two programing classes, I do have this laying around just in case.



5. Received book promptly and in great condition. Wish i knew which edition it was before buying but info is same as newer editions.

No comments about Introduction to C++ Programming, Comprehensive.

5 comments about The Dream Machine: J.C.R. Licklider and the Revolution That Made Computing Personal.

1. If The Dream Machine were a novel, you might conclude the author used every writer's technique to make it a thriller. Even though you know the outcome, you wonder how the many "miracles" and lucky breaks it took for the dream to become reality.



2. A graduate course in a book! A tour through historical theories, accounts, and events that made up the development of the modern computer and the Net. Far more extensive than just the story of Kicklider, a historical overview of many of the minds at that time and the events that converged to form the new informaton era.



3. If there such a thing as an "epic" story of computer science, then M. Mitchell Waldrop's The Dream Machine is it. Although it purports to be the story of J.C.R. Licklider, and the birth of personal computing, this book is much more than that. It takes us from the edges of the computer science revolution, through the development of the modern computing industry and the World Wide Web.
   
   Waldrop spends more time exploring the shadowy edges of the rise of computer science in America, and the intellectuals whose raw thinking provided the structure around which computing would develop. Giants like Norbert Weiner and Claude Shannon, and more obscure players like John Atanasoff of Iowa State University are given more thoughtful attention here than in most popular history accounts that I've encountered. Not only are their concrete accomplishments covered with clarity and understandability, but the thinking that got them there is attended to as well.
   
   Of course, among the cast of great individuals is Licklider, whose efforts are worthy of the title billing Waldrop gives him. J.C.R. Licklider was a computer scientist before there was computer science, in any practical sense. While Lick (as everyone called him) himself, and the voice of technical accuracy, would likely disagree with that assertion, I stand beside it. Licklider was first a scientist, and he applied those core principles to developing his ideas in computing; computer science.
   
   However, Waldrop's book does not feel like it was about Licklider, per se - despite a very intimate coverage of the man. Instead, the book remains focused on the growth of the intellectual concepts, and the practical technology that rose from those ideas. The scope of characters and technical detail covered by the book is remarkable, and yet it remains a readable and compelling story. The science is clear and understandable to individuals with an interest in the subject, without requiring a deep background (although, those with deeper backgrounds will still find the book enjoyable, and original).



4. For anyone who wants to know the history behind the personal computer revolution, this book is a must read. The author was a senior writer for Science magazine and understands both the technology and the people involved. There's almost no fluff in the book's 475-pages of fact-rich, well-written prose. My only complain it that, along with pictures of people, I'd have loved to have seen pictures and diagrams of the early equipment he describes.
   
   --Michael W. Perry, author of Untangling Tolkien: A Chronology and Commentary for The Lord of the Rings



5. "The Dream Machine" is billed as the story of J.C.R. Licklider, one of the main driving forces behind the research and engineering of personal computing. However, at least half of the book actually consists of general computer science history having little directly to do with Licklider, but which rather serves as context for Licklider's long and varied career. Well, it seemed to me that both aspects were handled very well by the author Mr. Waldrop and I am certainly much more educated now on computer science.
   
   Though quite long at nearly 500 pages, the book was actually a page turner for me as the style of the prose is closer to that of a novel than of a textbook. I found the transformation of government funding from virtually unlimited in the '50s and '60s (e.g. the massive SAGE project) to greatly budget constrained in the '70s fascinating, as well as the various contractors' reactions to the changing federal priorities.
   
   I give this 4.5 stars as it could have used a bit more focus on the purported subject, Licklider. Highly recommended for anyone with a strong interest in computers and software.