4 ms·
It's like there's a massive army of developers solely focused on writing GET APIs even though we have the tools to completely automate this and more but they al
by RedShift1 2y ago
It's like there's a massive army of developers solely focused on writing GET APIs even though we have the tools to completely automate this and more but they always find excuses to not use these tools - this thread is full of them. I don't get it, what they're really doing is just translating a to b over and over again. "Same but different". That's really the last thing I want to spend my time on.
- dventimi 2y ago> even though we have the tools to completely automate this PostgREST is literally a tool to automate this.
- RedShift1 2y agoWell yes but people seem very keen on not using it (or another tool that does the same or similar).
- dventimi 2y agoPeople are free not to use it, of course, but when they offer their reasoning I just don't think it holds up. For example, sometimes they say, "PostgREST doesn't save much because writing REST services is so trivial that it can even be automated." Again, my response to this is: if it's trivial, then why pay an expensive developer to do it? If it can be automated, then why do it it at all? If it can be automated, then automate it. Which...is precisely what PostgREST does.
- rblatz 2y agoThe point I made at the beginning of this thread is that it’s a long term high cost and a potential dead end, that really didn’t save you much time. If you are in early stage and just need to move fast and find your product fit it could make sense. But again the problem it solves isn’t hard, and quickly makes things harder than they need to be.
- dventimi 2y agoYes, that's what I understood your belief to be, right from the beginning of this thread. I just haven't encountered any reason anywhere among these comments to persuade me to share your belief.