4 ms·
> 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
by masklinn 8y ago
> 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.
Netflix's JSONGraph is that. In my opinion it's… kinda shitty to write requests for, it's noisier than graphql queries and offers little in the way of benefits.
> 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.
Simple as in trivial? No if you're only exposing an API to fetch an integer over the network it's not an improvement. If you're fetching complex data structures however, most RPC-over-HTTP (as I assume you don't actually mean REST-as-in-what-Fielding-defined) don't do the distance. They're add-hoc, less convenient to mess with (few have explorer) and commonly ill-defined.