Earlier quoted context omitted.
I don't see what's so bad. Seems like it would be a convenient way to skip some boiler plate back end code used for CRUD. Probably not optimal for a complex application, but it looks very neat for something quick and small.
If you're learning backend services, don't start by things like postgREST, it's just bad habbit, would be better to start by the basis with API servers / DB ect ...
- 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 and databases with PostgREST