I don't see why using something like GraphQL should push REST out of the way. I want to create and manage my resources, publish them on the web via a RESTful A

I don't see why using something like GraphQL should push REST out of the way. I want to create and manage my resources, publish them on the web via a RESTful API - and also provide a way for the user to query those resources in a meaningful way with just one call. That's exactly what I'm doing today - but with a proprietary language (and querystring - which is not ideal). I see this as the perfect companion for REST and I hope it will be standardized. Kudos