3 ms·
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 s
by emteycz 6y ago
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 and databases with PostgREST
- Thaxll 6y agoIt's a bad habit because of separation of concerns.
- emteycz 6y agoYou're not forced to write your app code in the DB as SQL procedures, you can also write TS or whatever else and use it next to PostgREST.
- steve-chavez 6y agoCheck this thread[1] for a previous discussion about "separation of concerns" and PostgREST. 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. [1]: https://news.ycombinator.com/item?id=21438307 https://news.ycombinator.com/item?id=21438307