[KirinDave]

> one of the practical benefits is that multiple queries from client to server can be merged into one, thus saving bandwidth and improving performance.

Sure, but if we're doing that by dragging the API implementer over every possible permutation of queries, optimizing whatever you could possibly ask for, I'm not convinced this is LESS work than me shipping BTO API requests.

> I'm sure certain types of projects will benefit more from the pros than cons of GraphQL.

My sneaking suspicion is that it's the kind of projects where their data model is small and isolated and doesn't offer much sharing between queries. Which is great when you can get it.