I'm more of an ops person and had the misfortune having to assist an inherited Drupal/static site generator project that heavily used GraphQL. It was not fun to debug this crap, and that is my biggest issue - as if the SSG setup itself isn't already a pain in the ass, adding GraphQL to the build stack was just the icing on the cake.
(One of the issues the dev team faced was the insane amount of RAM that was consumed by the GraphQL crap in both the FE and BE containers, which was a pain to debug for the FE side because that was an ephemeral container on an EKS environment)
IMHO, GraphQL entices developers on both ends to just be lazy and throw the complexity to the other team, and Ops who has to support both teams and mediate between both sides who just blame the other side for being too dumb.
(One of the issues the dev team faced was the insane amount of RAM that was consumed by the GraphQL crap in both the FE and BE containers, which was a pain to debug for the FE side because that was an ephemeral container on an EKS environment)
IMHO, GraphQL entices developers on both ends to just be lazy and throw the complexity to the other team, and Ops who has to support both teams and mediate between both sides who just blame the other side for being too dumb.