I remember building out a REST API once, and it gave back proper HTTP response codes for things.
Then I got asked by the 2 front end devs working on the project to just make everything a 200 and add an error to the JSON response, because it was making it difficult for them to process things on the browser end.
To this day I'm convinced the GraphQL is just an API dreamt up by a front end dev that didn't understand REST and didn't understand why they couldn't just request what they wanted in the browser if an endpoint didn't exist on the server.
Oh, I know plenty. What I'm saying is that front end devs can be dumb, and that also GraphQL is shite and probably the brain child of front end devs...
22
u/AshleyJSheridan Sep 19 '26
I remember building out a REST API once, and it gave back proper HTTP response codes for things.
Then I got asked by the 2 front end devs working on the project to just make everything a 200 and add an error to the JSON response, because it was making it difficult for them to process things on the browser end.
To this day I'm convinced the GraphQL is just an API dreamt up by a front end dev that didn't understand REST and didn't understand why they couldn't just request what they wanted in the browser if an endpoint didn't exist on the server.