<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>kos.gd (Posts about books)</title><link>https://kos.gd/</link><description></description><atom:link href="https://kos.gd/categories/books.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Mon, 16 Feb 2026 19:53:59 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Commentary on Javascript: The Good Parts</title><link>https://kos.gd/posts/commentary-on-javascript-the-good-parts/</link><dc:creator>Tomasz Wesołowski</dc:creator><description>&lt;div&gt;&lt;p&gt;"The Good Parts" has been a good read. The language has been described briefly and consistently from ground up, including a thorough explanation of objects, functions, closures and arrays. A great addition to the mix is a description of the numerous pitfalls and design problems. It seems opinionated at some points (more on this later), but very valuable as a whole. (That's correct - "The Good Parts" actually has two appendices dedicated to the not-really-good ones.)&lt;/p&gt;
&lt;p&gt;My commentary for selected parts of the book follows.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://kos.gd/posts/commentary-on-javascript-the-good-parts/"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>books</category><category>javascript</category><guid>https://kos.gd/posts/commentary-on-javascript-the-good-parts/</guid><pubDate>Sun, 22 Dec 2013 18:18:12 GMT</pubDate></item></channel></rss>