News for hackers. Stuff that matters.
Re:Why not use GraphQL? by jmnicolas on Saturday November 07, 2020 @09:04AM (#25015127)
> You'll likely never be in a situation where over-querying via a non-granular REST call will ever be an issue worth optimising around.

While I agree with your beginning sentence, the one I quoted doesn't sit well with me. It would be good to remember that not everybody has 100 Mbits fiber or 5G download speed.

We all saw the data on how milliseconds affect user retention then proceed to completely forget about it once building our apps.

I think we can do better.

Re:Why not use GraphQL? by HeyHoJoe on Saturday November 07, 2020 @09:25AM (#25015226)
Even if users don’t have 5G, why is your rest api so slow that it’s an issue? Why is graphql the solution? The featured article points out that optimising rest can be a better solution, in terms of time and effort, than implementing graphql. The problem that graphql solves isn’t this one.
Re:Why not use GraphQL? by jamil7 on Saturday November 07, 2020 @10:30AM (#25015597)
Agreed but I think the point was over fetching is likely very far down the list of optimisations.