I pick REST over GQL and such also. GQL has some distinct disadvantages that people seem to gloss over. Front end architecture seldom is oriented around makin

I pick REST over GQL and such also. GQL has some distinct disadvantages that people seem to gloss over. Front end architecture seldom is oriented around making efficient queries. My last slot that used it as glorified REST and didn't shrink the number of queries to the backend. It does make more sense if you have a variety of consumers of the data, but meh, after my experience I still wouldn't use GQL. Higher complexity in the backend. Our GQL backend was schema stitched together microservices. Highly complex, random services would bring the whole thing down, and it was not understood why. The schema stitching happened on every request and seemed very "heavy and slow" to me. Not all of that was the fault of GQL, but, it definitely provided more room to mess things up. Caching nightmare. Heavier client library. And on and on. Grass is not greener IMHO.