Hacker News Reader

> Which brings some simplicity to the client

And puts all the complexity on the backend :-)

As far as I've seen, front-end developers are generally quite happy about graphql. Back-end developers on the other hand are a different story.

View on HN

I kind of agree, but at the same time I don't. Before REST API's has always been a situation of discussion ( as in schema and what not, even with openapi). But with GrapQL I've seen more discussion about the schema the anything else. Which is what I prefer as a backend developer.

So if GraphQL front-end developers into discussion about schema I rather take that over whatever REST solution they're using today.

But I might be biased here...

I’d say it moves “all the complexity” to the backend if it were defining one REST endpoint for each page the client loads. With GraphQL, each resolver is individually much simpler logic, and there’s no effort to do the stitching.

So basically frontend+backend effort with GraphQL is much smaller than frontend+backend with REST

Reply on news.ycombinator.com