GQL is great, if only because it stops endless bikeshedding about "what is RESTful". It's not going to be right in every use-case and I find it useful to have G

GQL is great, if only because it stops endless bikeshedding about "what is RESTful". It's not going to be right in every use-case and I find it useful to have GQL and normal API endpoints on the same API so I can use the right tool for the job. From a client perspective it's night and day, server implementation is a little more tricky but the C# libraries seem to avoid a lot of the pain other back-end answers seem to be encountering, not sure why that should be.