To be honest, I find graphql syntax really weird. What you get back is json, why not make the query language json itself? So all the existing json processing tools on the frontend just work.<p>With the weird syntax, now you need a parser and checker, and you need to write some boilerplate for doing mutation syntax.<p>There’s a reason why everyone and their dog invented ORMs. So you could live in an object world and everything would just work. SQL translation magic would be just an abstraction.<p>GraphQl has some nice things, I.e you only fetch what you need, and the fact that that it exposes a service as a graph. However I’m not sold that it’s a big improvement over simple REST.
Hi HN. We built this when we realised we needed a few nifty bash scripts that need to talk to a GraphQL endpoint, especially piping subscription events to run a bash command.<p>We also use it as a node library from some lambda functions and then while we were at it, we realised a GraphiQL on demand to test a GraphQL endpoint would be nice too :)
This is awesome! I particularly like being able to spin up a local instance of GraphiQL against any endpoint (with auth headers and everything). I tried it with GitHub's GraphQL API, and it took me less than a minute to get going.
that Hasura company has really been cranking up dev tools lately. Seems there are some serious brains behind the company. I hope you'll find the equivalent business people to keep you going.
I'm interested in trying it with yelp <a href="https://www.yelp.com/developers/graphql/guides/intro" rel="nofollow">https://www.yelp.com/developers/graphql/guides/intro</a>
CLI looks neat, but these apps really require things like saved queries to be really useful. I'm pretty happy with using Insomnia app for Graphql / REST so far.