I especially didn't like the rant about the "horrible boilerplate array declarations at the top of the Wordpress plugin". That array looks like it provides some

I especially didn't like the rant about the "horrible boilerplate array declarations at the top of the Wordpress plugin". That array looks like it provides some declarative information to the backend on how to display the configuration UI. So the 226 lines of PHP code plugin does incredibly much more than his ~25 lines of code: It has runtime configuration settings and it provides a HTML UI to set said configuration options. All that in addition to the actual functionality. I would even go as far as to say that rebuilding all the Wordpress functionality in Clojure would not take significantly more or less lines of code than what WP already has. Or in other words: If I only need a small defined subset of Wordpresses functionality and if I have the time to actually write a blogging engine from scratch, then it will always have significantly fewer lines of code than WP - regardless of language. Once I add features, the line count will increase - regardless of language. This article is comparing apples to oranges: It's comparing a small, custom-built solution to a configurable out-of-the-box solution designed to satisfy the needs of the whole blogging community. Of course that's more complex. But it spares you the procedure the author later describes as "When I find a bug, I SSH in, re-attach to screen, fix it in Emacs, hit C-c C-c to recompile just the functions I need to update, and then detach from screen again.".