While some of their complaints are legit I think most of the SQL in this article are straw men. Most of it can be made more readable and more performant.
Care to back up those claim with evidence? The SQL queries are toy examples. Experienced SQL users don't write SQL like in the article because they know SQL's pitfalls and avoid them. It doesn't mean SQL isn't full of pitfalls and bad decisions (like many very old programming languages still in use).
Evidence? This is just, like, my opinion, man. But nested subqueries and old style joins... ripe for rewrite if I had say.