1 comments about An Object-Oriented Approach to Programming Logic and Design, Second Edition.

1. This author is imprecise in her use of terminology. She switches between similar terms for the same thing without signaling. She uses the same term for different things without signaling. She even uses incorrect terms.
   
   The author tends to use a concept in a discussion and then, later, she introduces the concept formally to the reader. Sometimes she never introduces the concept, and youstruggle with the text before you realize that a new concept is involved and you must set about untangling the spaghetti on your own.
   
   On a positive note, the author makes good use of analogies to illustrate abstract programming concepts. Overall, however, this text is a monument to mediocrity.

5 comments about Introduction to Languages and the Theory of Computation.

1. I normally don't write reviews. Couple of not very positive reviews could not stop me writing one for this title. In my opinion, this book really presents a breadth of information
   on the subject. If one is considering to buy this book, one should have due background in Discrete Mathematics.



2. During the course this book has been anything but helpful. The introductory part is a laugh as it takes for given you as a reader is very deep into mathematical lingo and proofs. Indeed the poofs are some of the worst written, many of them using statements as "Clearly it is..." and "It is now easy to see...", well, no, it isn't easy and mostly seems like a shortcut from the author to excuse himself from actual explanations.

   Even worse is the examples where solutions reference something form an excercise, here's a hint to Mr Martin, students don't solve all the extremly many excercises unless asked to, so saying something will be clear after a certain excercise doesn't work, how will we ever know if we're right or wrong?

   The educational value is very low due to the authors way of writing, never really getting the point across and always assuming the reader knows exactly what's going on. This is certainly not the way to teach people rather complex things. All in all anyone should look elsewhere to have a chance.




3. As far as basic ideas of automata goes, this book will do. It's not phenomenal, and it's not awful. It is merely sufficient. The main problem is that it lacks elegance in a number of places. In many places, it feels sloppy. Definitions are almost arbitrary, and often lack rigor. Techniques are long, tedious, and not very interesting. (This is nowhere more evident that the finite automaton -> regular expression conversion from Ch. 4, which has a really neat solution that this book does NOT give.) Yet, despite all this, it conveys the important ideas nevertheless.
   
   As far as developing skills for more advanced concepts of theory of computation, things don't look so good. This book's approach can be described as attempting, by sheer force, to make automata problems fit into rather vanilla proof techniques that readers will probably have already learned. The result is likely to do little more than convince readers that the subject is hard.



4. i am currently part of an online course, there is no teacher and all we have to learn from besides this text (which was assigned) is maybe 2 or 3 examples posted on a website for each chapter - almost all of which are entirely too simple to offer any real help. if you have to teach yourself this course this is definitely NOT a good book.
   ..
   -there are no solutions to the problems
   -the writing is not on an introductory level &
   -the questions escalate in difficulty way too fast from the examples
   -the examples are circular
   -the examples actually say "at this point its obvious that"
   -the examples offer little to no help for complicated problems like any of the one's we get on homeworks & tests
   ..
   i think the worst part of this book is the fact that generally after i do a problem i look back just to check if i got the right answer .. since i can't do this i have no real security of whether or not i'm doing anything right. then when i look back through the chapter when i need help i realize that the examples skip the steps that i need and the writing frustrates me more than it teaches me.
   ..
   it's kinda like trying to learn calculus and the very first problem you ever see asks you to prove green's theorem.



5. The material covered in this book, if you expected to prove what you are doing is correct, is challenging. There were several times in this book, where the explanation from the book was not enough for me to grasp the concept. I am not talking about cramming for the test, I am talking about repeatedly reviewing the concept in the book over several days before giving up and going for extra help.
   
   This is surprising, not because of my shear genius, but because the concepts in the book are not all that hard to grasp after the fact. For this reason, I think the book could be better written, by either including examples of more of the concepts or clearer language explaining the concepts.

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 Professional ASP.NET 2.0 XML (Programmer to Programmer).

1. I would recommend this book to anyone working on ASP.NET 2.0. XML is the integral part of .NET framework and used widely on all projects.
   Book explains XML classes, Data Validation, XML transformation, XML and ADO.NET, Web Services and use of XML in Web.Config and Configuration files.



2. This book was very useful. It covered a wide variety of topics and explained most topics very well. I would have liked the book to get into some more subjects a little more in depth, but when you are covering so many topics that is a little difficult to do. This book did cover a lot of the new XML classes in the 2.0 framework. I would have liked some more info on the sql server 2005 xml stuff, particulary xquery. The book talked about OPENXML and even made the statement that you should use .nodes for these types of queries now. But it made no mention of how to do so. Overall, this was a very useful text.



3. This is an excellent book covering the XML features of ASP.NET. It is very professional but, not for any beginner. It has the first 2 chapters which pretty much cover the basics but, throughout the rest of the book you need to know what you are doing. It is very detailed but is not really "step-by-step" like 1-2-3...It will walk you through how to do something through reading; so if your not one of those people who don't like to read, I wouldnt fully recommend this book to you. It shows a many screenshots in there so it makes it fairly simple to follow along. The book has almost 500 pages that are completely dedicated to the XML features of ASP.NET. If you are willing to take out the reading glasses and read a little bit. Overall, its an outstanding book!



4. Thiru Thangarathinam is one of the few authors out there who truly know how to teach and convey the knowledge they are presenting. The manner in which he approaches and expounds a topic should be formulated and used in all books. Most books these days simply show how to do the simplest of tasks and never provide real world scenarios. But guess what, in the real world your tasks are never that simple.
   
   Thiru does a great job in not only showing "how to" but also provides best practice tips so that you know "when to", "when not to", "when you do be sure to". These are the things I need to know in the real world. Without a doubt this was one of the best technical books I have read in a while. I will definitely buy any future books that he authors. Glad to see he's a fellow Phoenician also!



5. This is an excelent book. The section about MsSQL server and XML is excelent. I highly recommended

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.

2 comments about Pro Java 6 3D Game Development: Java 3D, JOGL, JInput and JOAL APIs (Expert's Voice in Java).

1. There is some overlap between this book and the author's other book on Java game programming, "Killer Game Programming in Java", but overall there is enough new material to make it a worthwhile purchase. The author starts out trying to explain Java3D. His explanations are OK, but the best explanation I have ever found as an overview of the API is "Java 3D API Tutorial" on the Sun Microsystems website. It's old, but the basics haven't changed. For the specifics of working with Java 3D in the modern era, come back to this book. The author has done a good job of putting together some programming examples that show how to program in current versions of Java 3D including a 3D version of Conway's game of life. He then modifies the program to show off some of the features of Java 6 such as its ability to communicate with scripting languages. Further chapters show how to build creatures with operational limbs that demonstrate Java 3D's TransformGroups, how to handle physics and Java3D using a specific physics API, multitexturing for more natural looking outdoor scenes, and finally how to deal with level of detail problems using mixed mode rendering. In each case, the author just doesn't talk about how to do something, he produces working code that gets the job done and provides a blueprint for the reader to go further.
   
   The section on non-standard input devices deals with interfacing devices such as webcams, game controllers, game pads, and the P5 Virtual Reality Glove to your 3D worlds and games. He mentions parts of Java that are seldom well-explained such as JInput to describe how to control these devices. In the section on webcams, the author talks about JMF and an alternative method of interfacing to cameras. This is good, since for all intents and purposes JMF is really a dead API with very little useful capability. One of the more interesting chapters in this section really has nothing to do with input devices, that being the chapter on JOAL, which is a wrapper around OpenAL, the OpenAudio Library. This is very practical since there are bugs in Java 3D's sound interface that have been there from the beginning and show no sign of being resolved. This chapter provides a practical way for Java programmers to get actual reliable 3D sound into their games and applications.
   
   The final section of the book is on JOGL, which is a Java wrapper for the OpenGL graphics library. The author explains and illustrates the use of JOGL by first implementing a very simple application to clearly illustrate all of the steps needed. Next, a 3D world is written using JOGL that includes a floor with a checkerboard pattern, an orbiting earth, a skybox of stars, a billboard that shows a tree, overlays, and keyboard navigation.
   
   This book, along with the Sun tutorial, is a good education in how to use the Java 3D API in general, and also how to build virtual worlds in Java as well as how to write 3D Java games, which was the book's original purpose. Highly recommended.



2. If you are new to 3D programming in Java then this book is not a very good place to start. That's not to say this isn't a good book its just that you will need to be somewhat comfortable with Java3D before reading this book. Like the previous reviewer said the sun tutorials will help to understanding the examples used in this book, just don't think that this book will hold your hand.

5 comments about Web Development & Design Foundations With XHTML (3rd Edition).

1. It was greate doing business with you. I received the book as you promised. Thanks, Nader



2. Ive taken the online course of this class and while over all the book is very imformative, there are several HTML errors every now and then which for me really has no excuse as this is the 3rd edition. The author DOES correct these errors on a website she maintains, but as this is a text book for a subject that requires exacting work, it can be quite a hinder to the learning process when the students are forced to check the professors own work when the coding does not work for them even after following the example to the letter. I highly recomend this product none the less, but you may want to have a friend on hand to double check the text if you are experiencing a problem with no reason.



3. The errors in this text annoyed me to the point of wanting to drop my course. I took this class online so it was difficult to get feedback from professor. The case studies were helpful, and despite it all I have learned a couple of things about web development.



4. Comments from reviewers of this book:
   
   "The layout of Felke-Morris's text is excellent. I have always
   disliked texts with crowded pages, distracting sidebars, and many colors. Felke-Morris' text focuses the student on salient content and uses color, text boxes, and the like to enhance and emphasize, rather than distract. Felke-Morris' hands-on exercises are something my current text does not even have. I really like these exercises because they give students a chance to learn and practice small chunks of material before applying the knowledge to a larger project."
   
   "Great coverage of web accessibility standards! Glad to see a tutorial on File Management. Many students coming into this course struggle with those
   concepts."
   
   "Great inclusion of ethical issues and accessibility tips (these are areas that I do find myself supplementing with our current text)."
   
   "Superior aspects of Felke-Morris include:
   --Inclusion of web site pages and/or addresses that have been referred
   to in the text as either examples of techniques, or places to find more information, or used as a part of the end-of-chapter section on Web Research. These are a real strong point of the text.
   --Use of the same four example sites through the text as end-of-chapter Cases. As each chapter is completed, each site is enhanced using the current chapter's skills and concepts.
   --The inclusion of Hands-On Practice and Web Research sections."



5. Web Development & Design Foundations With XHTML (3rd Edition)
   I used this text for a college Web design class. The lessons were easy to follow and laid out in a logical sequence. The case studies that are built upon as new material is learned are useful. I appreciate the attention paid to accessibility issues. I do have two major complaints though. First: There are far too many errors for a third edition, as noted by others. A great deal of study time is wasted before a student realizes that the text is wrong. Coding solutions provided by the publisher in the "Student Data Files" don't always validate, for example, and there are several mistakes not yet updated in the "erata" sections on the publisher's web site. Second: the extensive "Hands On Exercises" at the end of each chapter are less than helpful at the college level without at least some sample solutions. College instructors don't usually waste time on going over this type of material, so it's often a waste of time doing them. Suggestions for the publisher: Fewer "Hands On" exercises, more solutions and please fix all those text errors you've been hearing so much about!

5 comments about TCP/IP Sockets in C#: Practical Guide for Programmers (The Practical Guides).

1. I've read through the first couple of chapters and I must say this is a good book. The thing I like most about this book is that the authors take time to not only give you working code but explain what the heck blocks within the programs do. If you are a novice programmer you may want to pick up a different book because it does assume you have a good understanding of basic C# programming.



2. Did you ever just want a book get to the point and tell you what you need to know? This is that book. If your new to winsock, this book will get you rolling quickly.



3. I think this book is very good because es simple, explain clearly and go directly to the matter.
   
   Juan Ramon Divison



4. This book is a good intermediate to somewhat advanced book on TCP and UDP protocols using Sockets in .Net - all examples of-course as the title suggests are in C#. It does show some interesting examples and was able to get me started using Sockets in .Net - however it didn't go as far as I had hoped. But if you're needing something to show you how to start using Sockets it is a very good book.



5. This book gets very high ratings on both amazon.co.uk and amazon.com. I've given it a slightly lower rating than some, although still four stars, and will explain why...
   
   The subtitle on the cover of the book is "Practical Guide for Programmers" which suggests it is going to be good even for experienced developers. It is only when you read the preface (page X) that you find that the book is aimed "primarily at students", and even then is "intended as a supplement, to be used with a traditional textbook", which seems a bit of a contradiction when it then says that "we have tried to make the book reasonably self-contained".
   
   Anyway, what are the good points of this book? Well, it does mention most of the bits that a developer using sockets will want to consider. It has everything from blocking sockets, through non-blocking sockets and the select model, through to overlapped I/O. It also mentions threading, the use of thread pools, broadcast and multicast. All good stuff. Even includes example code for each.
   
   Where the book falls down is that having skimmed over all of those topics it (a) doesn't provide adequate information about how to choose the model (synch vs. asynch, blocking vs. non-blocking, 1 thread vs. fixed number (> 1) of threads vs. thread pool, etc) to use for a particular project, and (b) falls short of being self-contained, doing the blah-blah is beyond the scope of this book thing.
   
   I have seen many projects developed using the wrong model, resulting in poor performance, lack of responsiveness, inability to shutdown cleanly etc. I'm pretty sure that the authors of the book will have seen projects like that too. Books about using sockets really need to advise on this area.
   
   It is understandable that a book of this size and price will say that some things are outside the scope of the book, but not something as basic as socket options (p52 refers the reader to the MSDN). Again, socket options are an area where well-meaning developers or support staff set values that are little better than guesses, and which sometimes cause adverse effects. If there's going to be a second edition of this book, please include advice on such matters.
   
   So, all in all, good for students or people new to sockets, but not quite great. It tells you the basic techniques, but not how to use them to best advantage. Having said that, I prefer this book to C# Network Programming which rambles, uses language that is ambiguous in places, and contains a significant error (if being very generous, it could be very lazy English causing an unintended meaning) on the very page I opened it on.
   
   It's probably best for people who already know sockets really well, but who are switching from one language to another (e.g. C++ or Java to C#). Those people probably know what model and options to use, just need to see how to do it in C# - something the book does do well.

2 comments about COBOL for the 21st Century.

1. There is a somewhat defensive tinge to this book. The authors take pains to point out that Cobol is still widely used in business. Though you could hardly discern this if you glanced across a range of new computer books.
   
   This text explains thoroughly Cobol. Plus background on the continued demand for it. It certainly shows its vintage. A procedural-based language because when it was first devised, object oriented concepts were unknown or unappreciated.
   
   The book goes into how a significant portion of the Cobol usage nowadays is to maintain and perhaps extend legacy code. This does have the advantage of less competition from other programmers, if you choose to go into this field.



2. Well-written; however, there was nothing to warn me that I would not be getting the CD that was supposed to be part of the ISBN.

5 comments about Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series).

1. Start reading Chapter 1 of this book for even just the first few pages, and for various topics, it will say to go to future Chapters. If you take a look at those future chapters, there will be notes on the side telling you to go back to Chapter 1 or to other chapters. You can run into infinite loops or dead ends not really picking up anything. It is possible to maybe find what you were looking for, or find that the explanation for it is just not sufficient.
   
   If I'm trying to look for a topic to remember, this book is not an easy read with the index either. If you look up some topics in the index and go to all the pages listed, it may not list all the important pages. Sometimes, when I had to look for information on something, say a "use case" for instance, then I'd look that topic up in the index. I'd go to all the different pages listed in the index and it might not be what I was looking for. Then I'd have to look at the side of the page of usually the lowest or 2nd lowest numbered page listed by the indexed topic, and go to the Chapter(s) listed. When I went to those chapter(s) I'd still have to scour the entire chapter(s) until I might find what I was looking for. An example was when I was trying to understand what one of the diagram types was, a "state diagram" I believe it was, as compared to say an "activity diagram." Sometimes I would find out that things just weren't worded well if in there at all, and I'd have to refer to another UML book.
   
   This book may have some good use, but I haven't found that yet. It's hard to read and hard to look things up, and hard to learn from if you don't already know much or anything that is for sure.



2. I picked up this book as a way to familiarize myself with the changes to UML in UML 2.0, which are extensive, as I found the OMG specification nearly impenetrable. I had liked the first edition, though I too felt Fowler's Distilled was a much better intro to give to students and engineers learning UML for the first time. This edition, though, does not meet expectations. The typos and bad references throughout are bad enough. Join that with a complete lack of real-world design examples, poor organization, and poor design. Why a chapter on State Machines and a separate chapter on State Diagrams that repeats a lot of the earlier chapter? The blue cross references make it clear that the book is spaghetti design at its worst. Check out the table of contents, you won't know where to look for your favorite diagrams; check out the index, and you won't be able to find the definition of the concept you just can't quite remember. The glossary is useful, as the UML 2.0 spec dispensed with a glossary, making it even more impenetrable. On the other hand, the authors make no attempt to call out the new UML 2.0 features, which would have made my day. What I find most unforgivable, though, is the authors' inability to present the new UML as it really is: the book is seriously misleading in many ways for learning UML 2.0. My biggest peeve is the way they treat the new and highly useful composite structure diagrams. In the list of diagrams, they don't even mention it, calling it by the name of a different diagram, the "Component Diagram", which they feel is the same thing. They then separate the discussion of composite classes and components, making it seem as though they're totally unrelated. They fail to mention quite a few of the new UML features (the X navigation adornments that make non-navigability explicit, for example, which is critical to code generation, or the fact that you can have multiple stereotypes associated with model elements. In their defense, the UML standard isn't very clear on these diagram types, but this is a practical tutorial that should take practice into account. There are constant references to the Reference Guide for more advanced features; these are mostly the UML 2.0 features that they didn't feel were important enough to include in the comprehensive tutorial. The appendix on UML notation simply ignores many UML 2.0 notations. I can't help but feel shortchanged.



3. Book is complete waste of money. Find more prevalent information online. Not really a required book. Not used at all.



4. I don't know what people who would review this book well are thinking. These authors may be good at creating the UML, but terrible at explaining it. The sentences are packed with words they haven't explained - or uncommon uses of words that really have no meaning, unless you are already a UML expert. I can't imagine a more poorly written text.



5. When I am using tools supported UML, I often search key concept with this book. Because this book is an user guide.
   I made some sequence charts, so I use some functions of UML.
   I can not understand which architecture is good or not.
   I think there are little idea about that.