URLs you can change by hand in API calls? When I'm at that level, I can just as easily edit the call body.

> One critique I haven't seen about GraphQL is that it's less human-readable.

My experience is the opposite, reading a complete graphql query is way easier than reading a mix of URL, query parameters and entity body, even more so when I need multiple such queries to replace a single graphql query.

And the query tells me exactly what's in the result, to boot, so it acts as documentation for the data-extraction code.

No, that's not what I meant. I meant that RESTful APIs relate the URL to the data in a way that isn't true in GraphQL APIs.

Take reddit, for instance. I can clearly see a username in the url: https://www.reddit.com/user/masklinn

Swapping one out behaves as I'd expect: https://www.reddit.com/user/faitswulff

And tacking on a format type to the end exposes the content in the manner I'd expect: https://www.reddit.com/user/masklinn.json

The conflation of route and content is frustrating for developing single page apps, but it maps better to my understanding of disk files and folders, thus making the URL more human readable and easier to toggle and change by hand.

If everything was an SPA, you'd have to interact with the data through the frontend, which speaks to some singular GraphQL endpoint, hence my mentioning that GraphQL itself mentions that it is "unapologetic" about its front-end orientation.