Most of good parts are well-known, but not widely used. I can see they are fully and correctly used in JavaScript frameworks or toolkits but they are rarely or inappropriately used by page designers.

For me, sections on bad parts are much useful. I tell “===” from “==” but I have never used “===” just because I, as a Java programmer, am not familiar to it. The book helps use bad parts less rather than use good parts more.

Introducing other’s work

• A paper, Using JavaScript as a Real Programming Language
• The Non-Designer’s Design Book

Introducing his work

• Adsafe
• Contributions to JSON

Informative but arguable (in my view)

• XML’s future in WEB : XML is on web trending down. XHTML failed to displace HTML because
  • Its client-side validation is not so beneficial.
  • It lacks security model

• Thread is evil.
• Scribe, the first trial of data-document translation, is similar to JSON. Adopting SGML and XML instead of it was a bad choice.

Security of JavaScript seems to be one of his current concerns. His recent talk shows his approaches toward the security problems.

<script src="http://yui.yahooapis.com/2.3.1/build/yahoo/yahoo-min.js" type="text/javascript"></script>
foo= function() {} // function is storable in variables
YAHOO.lang.isObject(foo) // returns true

Some technique enabling OOP were helpful. I just enjoyed the encapsulation technique.

ClassA = function(){
this.funcA = function(){
}
this.funcB = function(){
}
}

Later, I knew that using “prototype” is more efficient in memory usage. Refer to this.

ClassA = function(){
}
ClassA.prototype.funcA = function(){
}
ClassA.prototype.funcB = function(){
}

Now, I found more readable and concise style from YUI.

ClassA = function(){
}
ClassA.prototype = {
funcA: function(){
},
funcB: function(){
}
}

Nowdays, if I am asked to use the grid-like control on the WEB, I will not hesitate to select YUI. Check out YUI if you want to know the beauty of unobtrusive JavaScript.