In every company I've worked at, there is a group pulling for graphql adoption. I've gotten involved and made it to having some well fleshed out graphs. Still,

In every company I've worked at, there is a group pulling for graphql adoption. I've gotten involved and made it to having some well fleshed out graphs. Still, I find the ergonomics to be lacking. Making POST requests with large bodies of JSON-ish queries that you have to meticulously craft from some hard to understand docs is way harder than an API call should be. And this is JUST for a query language. It's not like the server code comes for free. There are still all the same complexities of joining this with that, filtering on foo, limiting to X results, projecting the output fields. It's super complex on the backend yet people think graphql can give them exactly what they need for free. If there is some amazing benefit to FE developers it's lost on me. When I go to use an API and find that I have to use graphql I just groan and move on.