Anton Orlov
Jul 25, 2017 · 1 min read

A nice article. The only problem I have with graphql atm — is lack of adoption. Like even GitHub doesn’t allow you to do everything you can with rest through graphql. For example no way to get and read repo contents. Which is the place where I perform 90% of the requests.

I get the value and pros of graphql, but I guess we’ll all just have to wait when producers and consumers will be ready to switch. Until then I’ll keep to REST or both.

Anton Orlov

Written by

Full-Stack JS Dev obsessed with React and Vue