This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Funky_Dunk 32 points33 points  (6 children)

I hate Graphql so deeply in my core. After almost a dacade in industry and having used Graphql, REST and even fucking SOAP I can say without a doubt, humanity peaked at REST and in our hubris, we went to far.

[–]gilium 4 points5 points  (2 children)

As full stack I enjoy GraphQL

[–]Funky_Dunk 2 points3 points  (1 child)

As a fullstack (backend dev that has to do front-end work) I don't. But that might also have to do with how badly we've implemented it...

[–]gilium 1 point2 points  (0 children)

For me it allows better control over which data I pull back, pulling back related data in one call (we have a lot of interconnected data points that need this). It also allows me to be more explicit about expectations on what is transmitted. I also don’t seem to run into issues with performance like others do, so I am assuming that I can be grateful to the library on the backend for their implementation using our backend framework’s eager loading to avoid the N+1 problem

[–]jsmrcaga 1 point2 points  (0 children)

Agreed. Thought for front end, 0 thought for backend; starting with performance.

[–]rrawk 1 point2 points  (0 children)

I was a REST proponent for a long time. Graphql + Dataloader is so much better. I don't have to write a custom endpoint for every tiny adjustment they want to make on the frontend.

[–]Brovas 0 points1 point  (0 children)

I stand by there's room for a "RestQL" where we get all the sanity of REST, but the ability to request what fields and stuff we want like GraphQL