I agree with the author that REST is not as great as people seem to imply. Yes, it's easy to setup and get started, but the main problem is the lack of control. If I need a certain piece of data along with sub elements, and their sub elements - and the API doesn't already expose this exact object (or a way to request it, using custom query params for instance) - I'm left with the only option of issuing query after query (N + 1 query problem mentioned in the article)
GraphQL looks extremely promising in that sense, as finally the client decides what they will consume, and I can't wait to use it at some point.
My issue with it though (which has been a show stopper so far) is that complex authorisation for subsets of data and business rules around updates to the data seem (very)hard to achieve, but I'd still like to see an architecture that supports this easily.
I'd love to hear other's experiences with it, or other tools that solve the problems outlined here!
Edit: Improve writing a bit