Desicritics Reviews

Book Review: The Enemy at the Gate by Andrew Wheatcroft

Vinod Joseph — Wed, 19 Nov 2008 10:53:39 EST

In 2004, when Turkey’s admission to the European Union was being debated, Frits Bolkestein, a Dutch member of the European Union's executive committee objected on the grounds that Europe risked becoming "Islamized" and the Battle of Vienna would have been in vain.

The Battle of Vienna took place in 1682. At that time, the Ottoman Empire had crossed the zenith of its power and glory. Almost 600 years ago in 1071, at a place called Manzikert in Turkey, Turkish forces had defeated the Byzantine troops of the Eastern Roman Empire. It was the beginning of the end for the Eastern Roman Empire, which had outlived the Western Roman Empire by almost 6 centuries. The Ottomans considered themselves to be the heirs to the Roman Empire, though other western powers did not share that opinion. The Ottomans moved from one victory to another. Murad I and his Christian vassals defeated Lazar, the Prince of Serbia at Kosovo Polje in 1389. Serbia became a vassal state until 1521 when Belgrade was captured. At the Battle of Mohács in August 1526, Sultan Suleiman I (Suleiman the Magnificent) defeated King Louis II and occupied southern Hungary. Vienna blocked the Ottoman route to the heart of Europe. At the height of its glory, the Ottoman troops led by Suleiman the Magnificent tried to capture Vienna in 1529, but the siege failed.

Andrew Wheatcroft’s book The Enemy at the Gate chronicles the second attempt by the Ottomans to capture Vienna, this time in 1683. Wheatcroft is uniquely positioned to describe this conflict since he is an expert on both the Habsburgs, the then most powerful ruling power in Europe with control over Vienna, and the Ottomans. Wheatcroft’s previous works include books on both the Habsburgs and the Ottomans. In clear, lucid style using limpid prose, Wheatcroft builds up the battle settings, giving us an inside view of the players and politics involved.

The Thirty Years War had got over just a few decades earlier and there was not much warm feeling towards the Habsburgs from the Protestant powers. It was even said that Protestants living in Ottoman Europe were treated better than Protestants under the Habsburgs. Even Catholic France was not very supportive of the Habsburgs. The Ottomans too had a major enemy in the form of the Persian Empire with whom they were constantly fighting The main difference between the European wars fought by the Habsburgs and the Persian wars fought by the Ottomans was that the Habsburgs learned a lot from their experiences. Their armies had an organisation and chain of command which the Ottoman armies lacked. The art of generalship was well developed. The Ottomans relied on individual bravery and skills, while the European forces relied on teamwork, organisation and methodical preparation.There were so many areas where the Ottomans were much superior to the Habsburg forces. Their supply chains were much better, with Ottoman soldiers on the battlefield put up in much more comfort than the average Habsburg soldier, though the Ottomans were so far away from home. The biggest advantage which the Ottomans had was that there was a central authority in command, usually the Grand Vizier who acted in the Sultan’s name. In the case of the European forces, the soldiers were supplied by many nation states, some of whom were reluctant to do so and all of whom required payment or other rewards.

The Ottomans lost the battle for Vienna, one of the most intense battles ever fought. There were various reasons for this loss, the main one being the incompetence of the Turkish Grand Vizier, Kara Mustafa. Do read the book to find out the various mistakes which the Ottomans committed. Both sides were charged with zeal, religious and nationalistic. Wheatcroft cites quite a few examples of bravery, but I don’t want to describe them here and spoil the fun. Wheatcroft’s descriptions of battles and troops are second to none. For example, when Wheatcroft describes the Polish hussars who arrived just in time to relieve the siege, he says:

The Polish hussars were heavy cavalry par excellence and they had no equivalent in 17th century Europe, In effect a holdover from the great age of medieval chivalry, man and horse together were a missile with their lance or wielding their long spear like triangular swords more than four foot long – they existed only for the charge. Facing the disciplined volley fire of western armies, they had largely become a liability, but against the Janissary infantry of the Ottomans or their loose flowing formations of sipahis, they could be as devastating as artillery fire.

Wheatcroft does not stop after the Battle of Vienna. He goes on to describe how the Europeans capitalised on their victory and went on to win more battles. Hungary was freed from Ottoman power, though the initial attempt to take Budapest was a failure. As the Ottomans became weaker and weaker, they began to be regarded as just another European power. The Habsburgs and the Ottomans discovered various mutual interests. After Napoleon was defeated by Czar Alexander I, the Russians became stronger and this led to the Austrians and the Ottomans growing closer. During the Crimean war, the Turks fought on the side of France and Britain against Russia. Finally, in the First World War which resulted in the destruction of both the Austro-Hungarian and the Ottoman empires, the Habsburgs and the Ottomans were on the same side.

Book Review: Head First Statistics

Ganadeva Bandyopadhyay — Sat, 15 Nov 2008 01:29:26 EST

Head First Statistics is more a study guide covering basic topics of most statistics courses or even parts of statistical topics in application areas such as analog and digital communication, noise theory. Measuring central tendency, measuring variability and spread, calculating probabilities, using various distributions for solving problems, correlation and regression are some of the topics covered across fifteen chapters.

While the discussion is paced to be reader friendly, there seems to be an emphasis on distributions with entire chapters dedicated to some of them. The quality of the examples can do with some upgrading for a consistency within the book. Maybe lesser number of useful examples such as the one bringing out the various statistical concepts related to measuring central tendency in improving a health club could be continued across multiple chapters. This could ensure the continuity as the concepts build on one another.

To summarize, a good statistics study book with an emphasis on distributions. It would be good to see some of the other statistical concepts to be given more coverage in future editions. At least one other book which can be an additional read to this book would be Statistics in a Nutshell.

Book Review: A Soul of Steel by Carole Nelson Douglas

Fleiger — Fri, 14 Nov 2008 12:49:12 EST

If asked which one person we would have liked to see again, true Holmesians would vote for Irene Norton née Adler with a huge majority, if not by an unanimous vote. "A Soul of Steel" by Carole Nelson Douglas is a novel from her Irene Adler series which tries to fulfill that fantasy.

Irene and her husband Godfrey Norton are spending their “posthumous” lives with their friend cum housekeeper Miss Penelope Huxleigh in Paris, when a man from Nell Huxleigh’s past is thrust in their lives.

Capt. Emerson Quentin Stanhope, presumed dead in Afghanistan has found that, a decade later, somebody is trying to silence him because of the secrets he holds about battle of Maiwand. And by association, the life of the doctor who saved him in battlefield is also in danger. When he is found, sick and dying, by Irene and her friends, they decide to help him find and warn the Dr. Watson. But, helping Quentin makes them a target for an extremely dangerous hunter, and they have to knock on the doors at 221B, Baker Street to bring the mystery to a safe conclusion.

Chronologically, the story does take a few liberties with Holmes canon. Taking place some time after “Scandal in Bohemia”, during and after “Naval Treaty” (possibly placing it back by some time), it introduces a major character before it appears in canon (If we go by timeline according to this novel, there are some serious questions about Watson’s memory re: people trying to kill him). Although, that’s just the Holmesian in me cribbing.

Characters-wise, Godfrey Norton is your Standard English Gentleman, a good friend and a honourable man. He and Irene are completely in love with each other (though their married life sounds a bit more 20th century American than 19th century English) and are equal partners in their adventures. And of course, he is understandably jealous of The Man his wife remains fascinated by.

Miss “Nell” Huxleigh is the typical vicar’s daughter, governess in a respectable family kind of girl. She is Watson to Irene’s Holmes (although she will not approve of that comparison). Loyal to the fault and having lived a sheltered life before sharing in Irene’s adventures, Nell is the voice of common sense in the household. And that explains her feelings towards Holmes.

Irene on the other hand is portrayed as the equal and opposite of Holmes. They both share liking for adventure, the ennui coming out of commonplace existence, the flair for drama, as well as the immovable sense of justice. But where Holmes is an analytical machine, Irene the Prima Donna is impulsive and emotional (in short, dare I say, a woman); jumping into whatever catches her fancy without a thought for dangers involved.

This is before Watson’s stories start getting published, and hence Holmes to Irene’s friends is a just paid agent trying to swindle Irene out of her only means of danger. Since this is a story from “the other side”, that was the only reason I could read the portrayal of Holmes for most part. Given that tone of the novel, I was worried about the eventual meeting between Holmes and Irene, but a careful reading dispelled my doubts.

In short, if you can’t get enough of the world of Holmes, or (like somebody said,) you can’t get enough of The Woman who got better of Holmes, this is for you. For me, continuing the series would depend on how they talk about The Man.

Book Review: The Photoshop CS4 Companion for Photographers

Rajen Nair — Fri, 14 Nov 2008 12:01:55 EST

Umpteen numbers of books gets flooded in the market on the wizardly Adobe Photoshop software, highlighting its unique features for enhancing your images. The latest book launched by O’Reilly, the publishers of The Photoshop CS4 Companion for Photographers and authored by Derrick Story has all the ingredients a typical Adobe Photoshop would offer.

What stands out is the unique feature of Photo download and Adobe Camera Raw application incorporated in it. Unlike other books on Adobe Photoshop which primarily focus on software tools for improving one image, this book dwells more on the advantage of using Photo downloading and Adobe Camera Raw (ACR). The author makes an impressive presentation in its simpler and elaborate narration of applying CS4 to its optimum utilization. It goes on to explain right from importing images from the camera by using Photo download to defining pictures in A C R and then giving final touches in Photoshop.

Photo downloader helps the pictures open in Adobe Bridge, which I suppose most professional photographers might be familiar with for organizing and editing images. In CS4 the automatic Photo downloader can create two copies of each picture during the download process and one set of copies can be stored in an external drive attached to your computer, which works as additional backup, all in one go. Adobe Bridge acts as a sophisticated image browser and an effective photo management tool offering innumerable features such as collections, filters, thumbnails, a filmstrip, file properties, a keyword pane and much more. After organizing the first batch of images, one can review the shots in the overview, Photo-edit by sorting pictures and finally give rating to the pictures. Bridge CS4 has added features like smart collection that let you group images across folders and main advantage is that you can create folders according to the your rating assigned besides choosing your favorite images .

In the images editing section we have another important application that is ACR. It is a plug in that is bundled with Photoshop CS4. This is the most amazing software for image processing as it allows you to fine tune your pictures using adjustments tools such as Exposures, Fill lights, Brightness, and Saturation. ACR is not just to process RAW file but also to process JPEGs and TIFFs. ACR is non-destructive as the image that opens in this application saves all its meta- edit, thus protecting your images.

In advance ACR, if you shoot series of images under similar conditions you can use batch processing to adjust multiple pictures simultaneously. ACR tools have other features like Black and white conversation, spot removal, cloning and tonal and color adjustment with graduated filter tool. There some chapters giving some useful Photoshop recipes for Photographers and about using Photoshop to control printing. Photographers already using CS4 and for those who intends to use, this book would turn out to be a useful companion.

Book Review: Nagios - 2nd Edition

Ganadeva Bandyopadhyay — Fri, 14 Nov 2008 02:52:39 EST

The book comes across as a wonderful companion for utilizing Nagios- an open source system and network monitoring tool. There are twenty six chapters covering a lot of depth and variety with respect to Nagios.

There are five main sections in the book, viz. Source code to a running installation, In more detail,The web interface and other ways to visualize Nagios data, Special applications and Development. Some of the more unusual topics worth mentioning is the configuration for external notification via SMS and via email, monitoring room temperature and humidity, monitoring SAP systems via plug-in check_sap.sh and via SAP's own monitoring system CCMS and monitoring oracle database with oracle instant client.

The chapters are very concise and readable especially for the system, network or other infrastructure administrator already hard-pressed for time. One of the important facets of this book is that although there is an attempt to present the useful information, it also motivates the reader to go further and explore based on the suggestions and hints that is provided in the book.

To summarize, a highly recommended book for interesting and very useful topics in present-day IT infrastructure.

Book Review: Head First Physics

Ganadeva Bandyopadhyay — Thu, 13 Nov 2008 10:18:58 EST

Here is a refreshing approach to the subject of Physics which is one of the elementary science subjects in any high school. Emphasizing a “reader as part of the problem” approach among the many innovations in this book, it is a delightful read.

The book covers almost all the topics of algebra-based mechanics and practical physics in its eight ninety four pages, including an index. In spite of being such a huge book, the book makes for a consistent pace of understanding and comprehension as it starts from guidelines to think like a physicist, units and measurement more advanced topics such as gravitation and orbits, oscillations and finally coming back to applying the algebra and physics formulae to having a new understanding to thinking like a physicist.

With memorable examples and various innovations of the Head First series on full exhibition, the book is one of the must reads taking away from drab text-books and learning by memory approaches to learning physics. One of the outstanding aspects of this book is the continuity of the topics as they connect with each other while interpreting the examples.

Book Review: NEXT

K. M. — Thu, 13 Nov 2008 01:24:33 EST

NEXT is a novel by Michael Crichton. Or at least it claims to be. It has a disorganized plot, too many characters with too little characterization and gratuitous sex. Just about two weeks after reading it, I can hardly remember the characters or their roles in the plot.

The main plot describes the efforts of a biological research company engaged in creating genetic drugs to recover some cells that could be used to fight cancer. The cells have been obtained during a routine treatment and the patient is unaware that his cells are special. The doctor who treats him discovers that the cells are special and continues his research without informing the patient.

When he decides to commercialize the cells, the patient sues his company but loses the case. He then gets an offer from a competitor for his cells and goes into hiding. Meanwhile the cell samples are stolen and the company attempts to obtain cells from the patient’s daughter and grandson, providing enough material for all the action.

There are also some sub-plots. There is a researcher who discovers a “maturity” gene, accidentally gives it to his drug addicted brother who comes out of his addiction, then tries out the gene on some other people, only to discover that the gene actually causes premature ageing and death. There is another researcher who inseminates a female chimpanzee with his own sperm with some genetic process (I don’t recall the details) and lands up with a humanzee kid, resembling a chimpanzee in appearance but capable of human speech.

He takes the kid home and sends him to school disguised as a child with some rare medical condition. Overall, the plot is somewhat incoherant and one has to make an effort to remember the characters when they reappear after a few pages.

As a novel Airframe was much more engaging and Prey was a lot more exciting even though the plot in Prey was much worse. (Airframe and Prey are the only other novels by Crichton that I have read). If NEXT were just a novel, it would be a waste of time. But NEXT is more than a novel. It raises serious questions about patent laws in the domain of genetics, intellectual property rights, what it means to own ones body, commercialization of genetic research, role of universities and government in research etc. In fact, Crichton has a 7 page note at the end of the novel, explaining his views on these issues. Since one of the purposes of this novel (perhaps the primary purpose) is clearly to raise these issues, let me present a summary of some of the issues from the novel and Crichton’s views.

Crichton presents a world that is almost out of control, a world in which the state of the art in genetics has far surpassed the state of the relevant laws. Here are some examples:

The lawyer representing the doctor and his research company tells the patient’s daughter after winning the case, that it would be futile for the patient to appeal the ruling. “UCLA is a state university. The Board of Regents is prepared, on behalf of the state of California, to take your father’s cells by right of eminent domain.”

The CEO of the research company wants a divorce and custody over his children but his wife doesn’t. His wife’s grandfather died from a fatal genetic disease and there is a chance that she might have it too. The CEO’s lawyer demands that the wife be genetically tested and gets a court order. The wife is unwilling to be tested since a discovery that she carries the disease would ruin her life.

An insurance company cancels a person’s coverage based on some genetic information about his father who died in circumstances that caused a legal enquiry. Someone at the company that performed the genetic tests says “Anyway the son is saying he did not authorize the release of genetic information about himself, which is true. But if we release the father’s information, as we’re required by state law to do, we also release the son’s, which we’re required by state law not to do. Because his children share half the same genes as the father. One way or another, we break the law.”

“The COX-2 inhibitor patent fight was famous. In 2000 the university of Rochester was granted a patent for a gene called COX-2, which produced an anzyme that caused pain. The university propmptly sued the pharmaceutical giant Searle, which marketed a successful arthritis drug, Celebrex, that blocked the COX-2 enzyme. Rochester said Celebrex had infringed on its gene patent, even though their patent only claimed general uses of the gene to fight pain. The university had not claimed a patent on any specific drug.”

Op-Ed commentary: “Columbia University researchers now claim to have found a sociability gene. What’s next?… In truth researchers are taking advantage of the public’s lack of knowledge… Geneticists will not speak out. They all sit on the boards of private companies, and are in a race to identify genes they can patent for their own profit…”

At the end of the novel, Crichton presents his views in the form of a 5 point course of action

1. Stop patenting genes: Crichton writes that genes are a fact of nature and such cannot be owned or patented.

2. Establish clear guidelines for the use of human tissues: Crichton writes that there should be legislation to ensure that patients can control the purpose for which their tissues are used.

3. Pass laws to ensure that data about gene testing is made public: Crichton suggests (not very clearly or convincingly) that there should be some genuinely independent verification of findings and full disclosure of research data.

4. Avoid bans on research: Crichton essentially argues that “To the best of my knowledge there has never been a successful global ban on anything. Genetic research is unlikely to be the first.”

5. Rescind the Bayh-Dole act (an act permitting university researchers to sell their discoveries for their own profit, even when that research had been funded by taxpayer money): Crichton laments that thirty years ago, universities provided a scholarly haven, a place where disinterested scientists were available to discuss any subject affecting the public. Now universities are commercialized, the haven is gone and scientists have personal interests that influence their judgement. Also “Taxpayers finance research, but when it bears fruit, the researchers sell it for their own institutional and personal gain, after which the drug is sold back to the taxpayers.”

I agree with points 1, 2 and 4 and strongly disagree with points 3 and 5. In fact I believe he has got the issue backwards.

In his support for point 3, Crichton writes “Government should take action. In the long run there is no constituency for bad information. In the short run, all sorts of groups want to bend the facts their way. And they do not hesitate to call their senators, Democratic or Republican. This will continue until the public demands a change.” This is true but his conclusion doesn’t follow. An “independent agency” in charge of verifying findings has to be under the control of politicians who will be all too willing to oblige the groups who who want to bend facts in exchange for backing. This phenomenon is not new at all. It is called lobbying. Requirements for disclosure are even more ridiculous than bans. You can force a person from doing something with limited success. How do you force a person to disclose what no one else knows? And most importantly, government has no moral right to <i>require</i> someone to do anything. Men are not slaves.

About the Bayh-Dole act, again Crichton has the facts right and the conclusion wrong. Universities are certainly commercialized today. And researchers who are funded by public money and allowed to make private profits certainly act in unscrupulous ways. The incentives are definitely wrong. But the solution is not to de-commercialize research. That is neither possible nor desirable. It ignores the context of why the act was passed in the first place. It was passed because non-commercial research does not work.

Describing a character who is a director of NIH (National Institutes of Health), another character says: “Rob’s a major player at NIH, He’s got huge research facilities and he dispenses millions in grants. He holds breakfasts with congressmen. He’s a scientist who believes in God. They love him on the Hill. He’d never be charged with misconduct. Even if we caught him buggering a lab assistant, he wouldn’t be charged.” and again “It was classic Rob Bellarmino. Talking like a preacher, subtly invoking God, and somehow getting everyone to push the envelope, no matter who got hurt, no matter what happened. Rob can justify anything. He’s brilliant at it.” The solution to unscrupulous researchers (in as much as the problem can be “solved”) is not to have more such men like Rob. It is to make them impossible, or more precisely to make it impossible for them to enjoy political clout and arbitrary powers to grant millions in grants. It is to divorce research from government.

Python for Unix and Linux System Administration

Ganadeva Bandyopadhyay — Wed, 12 Nov 2008 09:54:02 EST

In addition to a very noticeable acknowledgments section, here is a book for system administrators trying out a new language to reduce their difficult and sometimes repetitive tasks. In fourteen chapters the authors have tried to do a commendable job for presenting Python as a language that could be used with little bit of learning.

Among the system administration tasks that are tackled via Python in this book, there are chapters dedicated to documentation and reporting, networking, handling data, SNMP, package management and building GUI s among others. One of the important additional tasks i.e. backup and restore seems to have not got the attention it deserves from the system administration perspective. This is true in spite of the newer scenarios where there is separate role of storage administrator as a specialist within system administration is coming up in most organizations and setup handling the massive growth in data storage and maintenance requirements.

While the examples presented are useful, there are some variations that could have made the book a more useful read. For example, in the example 5-9 about connecting to an SSH server and remotely executing a command, the password seems to be required in clear text. One variation could be an answer to the question “Would it be possible to use encrypted password so the script can be read and run by any less privileged user?” Another thing about the discussions is a frequent reference to books for further reading within the text. While it is a good idea, sometimes the list of books of further reading could have been given at the end of each chapter.

All in all, the book is giving a clear idea for using Python as a tool for system administration. Further reading and experimentation is definitely recommended to the readers after going through this book. Absence of major discussion on backup and recovery scripting is a big gap within the book of this nature.

Book Review: Romancing with Life by Dev Anand

Anuradha Goyal — Tue, 11 Nov 2008 11:31:40 EST

I have always loved Dev Anand for all the melodious songs in his films. Having grown up in the Doordarshan era, I have grown on all those black and white numbers, which still keep resonating in the ears. So, when his autobiography was published last year, it was definitely on my list of ‘to be read’ books.

Like most autobiographies, this book also moves in an absolute chronological order, except in the beginning where Dev Anand remembers his life before he moves to Bombay while on a train from Gurdaspur to Bombay. He briefly talks about his family and what he felt when he left them to pursue his dreams. Throughout the book Dev Anand comes across as a constant dreamer, who lives in his dreams and then wakes up to make those dreams come true both in his life and his films. His life is all about films and the women who walked with him in his journey, specially the ones which painted the silver screen with him. At times he met them while being a part of the film and at other times, he met them and then went ahead and made films for them. From the early forties to the 21st century what has not changed is the age of the women he fancied and romanced; it was less than twenty then and continues to be the same now.

In line with his image of an evergreen, timeless hero, he does not mention the years anywhere, though you can make out the rough timing by the films he mentions and the national events that he mentions here and there. But otherwise he has tried to keep the story more or less timeless. He is a man totally in love with himself; everyone else comes and plays a role in his life and goes. He also comes across as someone who lives only in the present, totally in the moment, with the person he is with, feeling the surroundings he is in and weaving out his future dreams from this present moment. He talks very romantically about all the women he romanced on and off screen.

His autobiography also brings out the businessman in Dev Anand. You would admire his networking skills and leveraging his fan following and start status as and when required. The fact that he once tried to launch a political party was a revelation to me. But what I admired about him was his ability to very quickly let go of the failures and move on to the next dream. I was amazed at the care and caution he takes to maintain his image in the minds of his audience, going to the extent of hiding his small disease that he had to suffer, going all the way to England to get a small operation done. All this so that none of his audience see him in a diseased state, something he thinks they can not imagine, their eternal hero can not fall down with a disease.

Before he could find himself a job in film industry, he worked for the military censor office and had the job of screening letters written by army officers. He probably got lots of romantic ideas from the letters written by army officers to their wives and girlfriends. He also got the idea of quitting the job from one of the letters, which said ‘just do it’. But wherever he was, and whatever he was doing, he was always a Casanova, trying to charm people and specially women around him, always believing he is the best. This phase also highlights his ability to draw inspiration from just about anywhere.

Dev Anand’s career spans almost the whole lifetime of Indian film industry and hence as he talks about himself, his films and his friends and colleagues in the industry, you also get the feel of how this industry has evolved over the ages, how things have changed. Here and there he also mentions his views on the social and political scenarios in the country and the world, giving a feeling of someone who is very connected to the outside world and its happenings and not just lost in his eccentricities.

Having been educated in the British era, he writes in flowery English.I guess the editors have not really changed the text. At places you feel that the language of the book could have been a bit better. There is a chapter for each of the films he made under his banner and some of the films he worked in. Though hardbound, the quality of the physical book could have been better along with the cover design. But now having read the book, I realize that the star might not have wanted anything except his picture on the cover. I would have wanted little more depth in the book, as there is so much the author has to share, but I guess in the interest of the length of the book, he has not gone into too much detail and just touched upon what he felt was important to share. He has hardly spoken about the music, which in my opinion is the biggest contributor to his success. The last portion of the book could have been compressed, as he talks about his films which not many people have seen and have starred people whom no one recognizes.

Read the book to see a man completely in love with himself. A star, who thrived on public adulation, who worked towards it, lived amongst the adulation poured on him from all directions and continued to seek more and more of it. An eternal optimist, who looks back at his life as if everything was picture perfect including the heart aches that we went through.

Book Review: Javascript: The Good Parts by Douglas Crockford

AJ — Fri, 7 Nov 2008 06:28:37 EST

The phrase "JavaScript master" and Douglas Crockford are considered synonymous in the web development world. When I heard that Crockford was writing a book on JavaScript, especially a guide to the better features of one of the most maligned but popular languages in the current web development industry, I was sure I wanted to read that book. I opened the book with very high expectations and unsurprisingly, I was not disappointed one bit.

With the recent explosion in the usage of JavaScript, the interest in JavaScript is at an all time high. When Netscape, which created JavaScript, released the specification of the language in the mid-nineties, it was unable to define a robust and complete specification for the language due to pressures of rushing out a production release. As a result, fair chunk of the language is not well thought out which contributes to bad programming style and promotes some bad programming practices. It is not the programmers but the language which causes this. Programming models based on Global variables, JavaScript eval, inconsistencies in variable scope, and confusion regarding how objects are created and handled in JavaScript can all be the sources of programming errors and give rise to bad programming practices.

This book, as its name suggests, focuses on the "Good Parts" of the JavaScript while cautioning the readers against the "Bad Parts" of the language. All the above mentioned "bad parts" and many other programming constructs are cautioned against in a two-part appendix.

Two other appendices also touch on JSLint, the powerful JavaScript syntax and program correctness verifier and JSON, the preferred and increasingly popular text data exchange format. These two chapters give a taste and a starter for two very important support tools for JavaScript.

However, the meat of the of the book focuses on the better parts of the JS language. In ten chapters, Crockford explains why features like - JS inheritance model, prototypes, objects, arrays and how the language handles regular expressions - are very useful and make JavaScript a fairly powerful language in its own right. Object Oriented programming in JS, how methods and the prototype chain is handled and can be used to write clean and powerful code are all a must read for advanced JS programmers.

The language of the book is very simple and sprinkled with illustrative source code which makes understanding the concept in discussion easy to understand. That said, this is not a beginners book. This book is aimed at those who have programmed in JS and have a working knowledge of the language. Nevertheless, it is a highly recommended book for anyone looking to get into better and more powerful JavaScript programming.