Hacker News Reader

Then to read the planet’s name, we ask: GET - /planets/1 And to read the films titles, we ask: GET - /films/1 GET - /films/2 GET - /films/3 GET - /films/6 Once we have all 6 responses from the server, we can combine them to satisfy the data needed by our view.

this is stupid there is no need to go multiple rounds?

View on HN

Yeah, this seems like terrible API design that, while it may be constructed to make a point, sort of obscures whether I should actually care.

GraphQL seems a lot more complicated to consume/explore than REST, and it looks like I need to know a good bit about how the data is shaped before I write a line of code - something that can change, and something that the current REST endpoint system (happily) doesn't need.

Reply on news.ycombinator.com