Back in the heyday of Netscape, I did JavaScript client-side development as part of web development. It was often frustrating work. Recently I began reading Cr

Back in the heyday of Netscape, I did JavaScript client-side development as part of web development. It was often frustrating work. Recently I began reading Crockford's "JavaScript: The Good Parts". I must admit that, as I make my way through the book, I find myself shaking my head in amazement at the idiosyncracies and weaknesses remaining in the language. It was a clumsy language then and remains one now. But it's the only show in town where the browser is concerned. Crockford claims that, by restricting oneself to a subset of JavaScript (i.e., the "Good Parts" of the title), one can do what is necessary. He writes also about the bad and awful parts of JavaScript. I am thankful that Crockford had the skill to discern signal where I saw noise, and the patience to carry out and publish his reorganization. But reading about JavaScript is still good for laughs!