I agree with what he says about OO patterns. The p/r equivalents are usually simpler and are "local views", often based on relational formulas, and not some large hand-built monmonstrosity.
One thing about his program size challenge problem is that he does not justify the need for it. Just because a language can do something intellectually keen does not by itself make it a better language. "My vacuum tube can make new vacuum tubes" might be a neat trick, but not very useful if nobody wants vacuum tubes.
He should show it in a practical context.
I also like his comment about how to sneak LISP into an organization: tell the boss that it is XML. Perhaps somebody can write an interpreter that uses angle brackets instead of parenthesis.