Reading the TL;DR it's almost hilariously obvious how all that reasoning leads to one simple conclusion: SQL beats both.
The reason why we might use GraphQL over SQL is the same reason why we might use REST over GraphQL.
These protocols are all on a spectrum and GraphQL has the most difficult position: it sits right in the middle. No matter what it does, one of the two extremes will be better at doing that, so the only good point for using GraphQL is: For many projects, it sits right in the sweet spot between the extremes. Arguing that it's objectively "better" than either extreme will just lead to the question "Why not go all the way to the other extreme then?".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Reading the TL;DR it's almost hilariously obvious how all that reasoning leads to one simple conclusion: SQL beats both.
The reason why we might use GraphQL over SQL is the same reason why we might use REST over GraphQL.
These protocols are all on a spectrum and GraphQL has the most difficult position: it sits right in the middle. No matter what it does, one of the two extremes will be better at doing that, so the only good point for using GraphQL is: For many projects, it sits right in the sweet spot between the extremes. Arguing that it's objectively "better" than either extreme will just lead to the question "Why not go all the way to the other extreme then?".