That comparison is misleading, to say the least, particularly because Crockford’s book also includes a colophon, a dedication, a preface, lots of syntax diagrams, and two appendices called “Bad Parts” and “Awful Parts”. All in all, the good parts are just 140 pages, give or take.
string, and nobody quite understood the relationship between both; there was
=== and nobody quite understood the difference between both. And the list could go on and on and on.
But we can go even further, without exaggeration or hyperbole: in retrospective, the biggest contribution of Crockford was to finally make functional programming mainstream. It was this book, together with the rise of Ruby on Rails, what would make millions of developers all over the world, including the author of these lines, understand what a closure was for the first time. And since, according to Herb Sutter at least, the free lunch was over, the time was ripe for functional programming to rise.
Cover photo by the author.