Totally agree, Graphql pushes the problem to the backend, where arguably, it's easier to mitigate after bottlenecks are discovered. Seems like it postpones pre

Totally agree, Graphql pushes the problem to the backend, where arguably, it's easier to mitigate after bottlenecks are discovered. Seems like it postpones premature optimisation... which is a good thing in my opinion