I don't really understand his point. He says that SQL has been around for 40+ years, as if that's a bad thing, and doesn't really say anything else. I guess he

I don't really understand his point. He says that SQL has been around for 40+ years, as if that's a bad thing, and doesn't really say anything else. I guess he is complaining about the idea that the user's input doesn't get insert directly into the database, i.e., the connection would be browser->db, and instead we need an application component that reads from the browser and shapes to the DB. At this point, we must ask if the author has ever worked with one of the thousands of applications that implements their "API" through stored functions. I won't condemn this method wholesale, but people have mostly moved on to more flexible representations for good reason. The whole article seems predicated on a belief that most work should be on the consumer workstation, which is why he starts by talking about how much better it is that people now have desktop computers instead of clients that connect to a mainframe in the basement. The author apparently doesn't grasp that the web acts just like those old terminal clients he refers to in beginning of the article. There's a big server running the application in someone's datacenter, and your browser is a thin client over the top of it, an interface into its inner workings. He blames this on databases. (???) The browser doesn't provide the mechanisms to directly connect to arbitrary protocols. I don't really think there's much substance here.