<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nojvek</author><text>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.&lt;p&gt;With the weird syntax, now you need a parser and checker, and you need to write some boilerplate for doing mutation syntax.&lt;p&gt;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.&lt;p&gt;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.</text><parent_chain></parent_chain></comment><story><title>Show HN: Curl for GraphQL with autocomplete, subscriptions and GraphiQL</title><url>https://github.com/hasura/graphqurl</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>peterjmag</author><text>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&amp;#x27;s GraphQL API, and it took me less than a minute to get going.</text><parent_chain></parent_chain></comment><story><title>Show HN: Curl for GraphQL with autocomplete, subscriptions and GraphiQL</title><url>https://github.com/hasura/graphqurl</url></story>