I agree with other reviewers who have said that this book lacks issue for developers. The examples, and diagrams, are absolutely atrocious. In addition, I don't think that it offers a decent overview of CORBA. Indeed, the information is all there (that is, overview info), but it is embedded in a dry, repetitive, and big-worded style. Also, I wish that writers would someday learn what a split infinitive is, in order for them __to hopefully stop__ using them all the time!

Some good titles coming out soon. Let's hope.

-Nathan

This is a good book for a broad overview. Essentially, it is an executive summary in book form. The content is complete and useful, but the style is dry and the presentation uninspired. This is the bran-flakes of CORBA: good for you, but not particularly enjoyable. It is also almost useless for developers (but it doesn't seem to be targeted towards them either).

What it is: A good introduction to what CORBA is and what it offers. The sections on the services and the IDL should provide a nice summary for the technical manager. The descriptions and comparisons of other distributed technologies are informative, and the systems engineering section is littered with information a manager needs to consider for a distributed development effort, with or without CORBA. What it is not: The book does not provide much for the developer. It does not contain any nuts and bolts insight for the new developer, but does state that their is approx 6 mo. rampup required. Overall: I thought that this is a book which should be read by any new manager and developer considering CORBA. Likely to be a reference for a manager and less to a developer, but definitely worth reading. A good companion book to this (opinion) would be Java Programming with CORBA, Vogel - Duddy (ISBN 0-471-17986-8) Small quip : Smalltalk community would appreciate "Smalltalk" instead of "SmallTalk".

This book is about 70 pages of recruiting information and 125 pages of addresses and phone numbers of schools. Given the fact that 25 pages are made available with the "look inside" feature, you can read 1/3 of the book online and get the names, phone numbers, and addresses of schools using the web or at the library.

The book provided some decent information at best, but when I got to page 80? and realized the book was over, I didn't feel very good and I certainly didnt need 125+ pages of addresses of schools I have no need to call or no desire to call..

"Everything you need to know about college sports recruiting" is a very thorough presentation of the college sports recruiting process. The chapters are ordered in a logical and easy-to-read format.The pages are filled with invaluable information to help the prospective recruit make sense in an often tumultuous process. However, this book is not just a descriptive analysis of the reruiting process. The author, Jim Walsh, shows the importance of planning the whole recruiting experience. The author challenges the reader to set goals, and to realistically evaluate these goals. Co-inciding with this, Walsh offers many insights into what standards coaches at various colleges use to determine a successful recruit. Another major appeal of the book is the emphasis Walsh places on academic performance relating to the recruiting process.The author shows that academic performance will likely be a determining factor in the quality of the school that is attained.In fact,Jim Walsh shows that strong academic performance will open many doors not otherwise possible with mediocre athletic performance. Emphatically, the author embraces the "student-athlete" philosophy. The "student-athlete" philosophy make this book an ideal purchase for both the prospective high school recruit and the parents of the prospect!Additionally, the book offers a number of insights for parents to be aware of during the sports recruiting process. Finally, the author does an excellent job in

matching a player's talent with a particular school program. He encourages readers not to overlook the Division two and three schools, offering a number of personal stories of players who went on to have successful professional careers. This is a comprehensive book that offers many insights for the prospective college sports recruit.It is highly recommended for the prospective high school recruit and to the parents of the recruit.

The book appears to be a collection of paragrahps from a myriad sources on the same subject. A very non-scholarly book.

As someone new to the field of High Temperature Electronics, this book was of inestimable help to me in coming up to speed rapidly. Using the valuable information provided in this easy to read resource, I was able to complete a system design in rapid time and under budget. I would highly recommend this book to others in this field.

This book has one over-riding theme repeated constantly: The White Man is always wrong and the Indian is and has always been an innocent victem. I won't list details, but the lack of objectivity and obvious implications to the promote the theme are insulting. Although the book may contain some valuable and useful facts about Native Americans and their lifestyles, it is impossible to determine how authentic any of them are due to the overt propaganda that is being constantly asserted.

A beautiful book that pleases the mind and eyes. Very authoritative and full of historical and anecdotal information relating to the Native Americans. Begins with pre-Columbus and continues through the ages to the 90's. A must read for anyone interested in Native american culture and history. The photographs and illustrations are priceless and well worth the price of the book. Add this to your history collection, younsters enjoy browsing at the wonderful prints of paintings and illustrations. An easy read whose pictures entertain and captivate the imagination.

As a die hard Redskins fan, I was very sorry to see this excellent concept so badly muffed. The idea behind this book is to cash in on the Washington Post vault, providing great photos and articles combined with new pieces by long-time Skins beat reporters to tie it all together. Sadly, whoever edited and proofread this thing reeeally dropped the ball. Sentences at the bottom of the page are repeated at the top of the next, photographs are mislabeled, pieces of sentences are missing, words are chopped off in the middle. Probably still of some value for the die hard Skins fan, but a real black eye for the Washington Post. If their newspaper were produced as shoddily, Richard Nixon would have finished his second term.

Yes, there are some typos and such in the early chapters but the book isn't as lousy as described in the 2-star review. Most of the problems are hyphen-ated words that are not at the end of a page or line. It is like the typeset was changed but the book was not reproofed.

Still, there is a lot of good information in the book. I think it covers items that Loverro's book (very good as well) ignored or glossed over-- how Gibbs wanted to sign and trade Riggo and how Joe Jacoby ended up sticking around in that first camp. The Times summary makes it sound like Gibbs and Beathard were geniuses building a team. This book shows that they were also lucky geniuses. If you are a Skins fan, you should own this book.

I see there is also a newer edition out with the Synder years (ugh).

then you should read this book, because all the dirty tricks that IBM used in doing business are laid out and followed by Microsoft. The reading is a bit tedious but once you get by that you find interesting tidbits like the printer that IBM would install for one price, if you needed more speed from it they'd send out a tech who would futz around for a while, throw a switch which would increase capacity and you'd then be charged double. Microsoft follows this strategy in software with Windows XP Home and Professional, throw a switch and double the price, very neat!

There are loads of other fun tricks that IBM pulled, can't remember them all because I read the book 5 or 6 years ago.

This book deals with the times of Richard III, perhaps the most contraversial of English kings. More describes him as a dark villain without a conscience, who set before himself a desire of the crown and waded through a sea of blood of his innocent victims to get it. Even though this book is titled "The History", it cuts off abruptly in the sixth month of Richard's two-year reign. But there are plenty of pages on which to tell us of his evil deeds, namely, the killing of eight people that stood on his way and that most horrible of all the crimes that he is charged with- the murder of his two nephews, the true heirs to the throne. This work was pronounced by some historians as the contemporary account of Richard's reign, and made them believe that if Sir Thomas More wrote it, it must be all true. But there is always room for reasonable doubt. This book was written in 1513 when More was just a young lawyer, not yet knighted, canonized, or recognized as "the most honest man". In fact, he was only seven when Richard died- not old enough to form social opinions of his own. His book is heavily biased since he spent his childhood in the household of John Morton, Richard's enemy and traitor, and therefore heard numerous rumors and only the evil about the king. More is said to have done a research before writing, talking to many people. Since the Tudor dynasty was now in power, who had less claim to the throne than Richard, it was treason to speak in praise of him(a historical fact). Many things in More's book are inaccurate. He states, for instance, that King Edward IV died at the age of 52, when in fact he was only 40. He also says that Richard's left shoulder was higher that his right, while historian John Rous, writing 23 years earlier(a true contemporary!), says vise versa. More is also the first one to "give" Richard a witheres arm eventhough Rous does not mention it at all. Furthermore, More states that James Tyrrel, who was paid by Richard to kill the two princes, was knighted by the king after performing that deed. But Tyrrel was knighted 13 years before by Edward IV for courage in battle. Apparently Thomas More's "sources" were not all that reliable; and seeing the falsification of such undisputable facts as the age of Edward IV at his death would make one wonder if the rest of this dark "history" is true, undoubtedly coming from the same sources.

Behind David Lean's directorial masterpiece 'Lawrence of Arabia' (1962) lay a series of attempts to film T. E. Lawrence's life, most of them centred around the abridged version of 'Seven Pillars of Wisdom', known as 'Revolt in the Desert.' Chief amongst the filmmakers eager to produce this epic was the great Alexander Korda, who bought the rights to both books and also to several biographies that contained their material. Korda was asked by Lawrence himself not to make the film while he was alive. Five months later, Lawrence was killed in a motorbike accident and Korda began his preparations. Locations were scouted, scripts were drafted, and several actors were tested to play the lead. Walter Hudd (who had played the Lawrence-based character Private Meek in 'Too True to be Good') and Leslie Howard were the favourites, although Cary Grant and Laurence Olivier were also considered. The Foreign Office thwarted Korda at every turn, protesting that it would be ill advised to show the Turks in an unfavourable light with the ongoing political unrest in the East. After a dozen attempts to make the film, Korda let it slide. This book is tripartite: part one sketches a brief history of the attempts to film 'Lawrence of Arabia' and includes pictures of all the key players. The second part is an interview given by Leslie Howard on how he would play Lawrence; and thirdly, the final script (1938) of the Korda epic is reproduced. While it is a laudable piece of work, the book fails to hang together and emerges as two articles and a film script that are linked by the same subject, but have no cohesion. Part One is far too brief for the reader to gain an understanding of the forces arrayed against Korda and his project, and it would benefit from more research and more expansion on the views of the various directors and actors engaged for the film in its different stages. Part Two is simply the Howard interview with no editorial comment offered. Part Three, the script, also has no analysis. This is surprising, as it is rich in allusion and with peculiar sequences that (to modern eyes) detract from the overall pacing of the film. It relies heavily on 'Seven Pillars' for dialogue and description, with little or no modification. To those who are acquainted with the Robert Bolt script of the Lean film, the Korda Lawrence is but a pale shadow: eloquent passivity rather than "nothing is written" man of action; cold detachment rather than anger and angst in crucial scenes (Tafileh, the Turkish hospital); the smug imperialist rather than the tortured anti-imperialist. Korda's Lawrence was intended to be heroic, a ( ) puff-piece with a serious bite, but looking at the script today, he seems shallow, self-important and obnoxious. The real Lawrence evaded any attempt to capture him by constant shifts in personality, presenting a different face to each person he met. It would appear that the celluloid Lawrence of Korda's vision was the same; and, as such, defeated him wholly.

It's a bit difficult to know who to recommend this book to. It's not that it's a bad book - it isn't - rather that it contains almost exactly the same arguments as Leviathan, only shorter and in less detail. Consequently they are more convincing in Leviathan than here, and I have to recommend Leviathan instead of this.

If you're unfamiliar with Hobbes, what his political argument basically boils down to is that people are naturally bad, and will all try to steal from their fellows, and kill those that displease them, and so on, meaning that in their natural state man is in a constant state of war. It is necessary then to establish the Leviathan, that is, a Sovereign, who has ultimate power unquestioned by anyone, who stops men from fighting by imposing laws with penalties for breaking them so harsh that it would be madness to not obey them. In this way order is kept.

That is the argument put forward here, and in the Leviathan, only, as I said, the Leviathan puts it better. I can only think this book would be useful to those who find the 500 odd pages of the Leviathan too daunting, and want to start with something shorter.

This is a good introduction to functional programming.
It is less language specific than some of the other books.