Earlier quoted context omitted.
As a seasoned TypeScript backend/fullstack developer I don't understand - why is it such a bad tool, and if it is because of the tool and not the concept, it seems possible it will be fixed in the future - why is it a bad habit; I consider the boilerplate CRUD code I write to be a bad habit that I should've automated years ago, and that's exactly what PostgREST does - why can't you learn the basics of API services an…
It's a bad habit because of separation of concerns.
tl;dr: business logic can be done with views/sps on an isolated schema. More layers makes the overall OLTP system less performant and harder to scale.