There are a bunch of easy technical critiques on this blog post. Here's a pragmatic one: name me a REST API in a real-world piece of software that doesn't have

There are a bunch of easy technical critiques on this blog post. Here's a pragmatic one: name me a REST API in a real-world piece of software that doesn't have at least one chunk of special product-driven logic in it -- one with customers, I'm saying. As soon as you need to own even the smallest bit of backend logic, assuming you're using a framework where everything else is done for you, you've cargo-culted your way into trying to shoehorn the most degenerate case for a problem into a generalized framework. Like, god forbid you want your backend to talk to another internal service. Or use third-party auth for managing access to privileged data. We should definitely just send that to the client and let JavaScript sort that one out. Love that idea. Anyhow, this is a blog post that doesn't really do anything new, but presents it in a way that claims it's evidence that something that a lot of people stake their careers on isn't necessary. I'm happy to dismiss it in kind.