As far as I know, JS clients Lokka and Urql are pretty small and cloud be easily ported to a different language.
How is pagination worse than the REST equivalent?
I guess I could see a case for client side caching based on IDs, but unless you couple this with subscriptions thats kind of brittle.
With rest, you can only paginate that particular call. You cannot really paginate different results in that one call. At most you can do is say get the list of objects at this endpoint. And that is far easier to grok than graphql's pagination in even the simple case.
I mean, just look at the official guide on this: https://graphql.org/learn/pagination/
And that only covers a simple use case!
Graphql allows you to paginate several collections in the same call, but you certainly don't have to. You can do just like REST and do one at a time.
Where did you get this idea that REST in any way dictates how you do pagination?
My point remains, why write queries when you can query endpoints and write filters easily without having to learn a new query language?
What's so amazing to me is that it is really easy to spin up a server that talks graphql in any language. But there is no client support.
And hand crafting queries is a million times worse than reading the rest documents
Oh, you want to get a list of items by owner, you can do that but you'll also have to paginated the inside and outside list. And the client will have to follow these pages while also having a deep understanding of your model.
Without good client tooling, graphql is a nightmare.