I feel like the author has never used graphql. We're also just finally graduating past REST to something more meaningful. This advice feels 15 years late and no

I feel like the author has never used graphql. We're also just finally graduating past REST to something more meaningful. This advice feels 15 years late and now totally wrong. An API shouldn't be tied to a protocol like http, it should be able to move on to other things. Ahh I was correct: > I have never used GraphQL, so I can't endorse it, but you may want to evaluate it as an alternative to designing and implementing your own API query capability. You really shouldn't write this giant article without having tried that.