@wunsch that sounds rad. Always wished more terminal utilities used repl interfaces instead of command-line flags

@noisesmith what's the jazz with graphql? Haven't looked at it yet. Is that a general graph solution?

it's not even a graph solution, it's a query language for getting data to web clients more efficiently

yeah, the use cases didn't sound very graph-y to me

I am not sure if it even supports proper graphs of data to query - it might only do trees (but I don't know that for sure)

rgr

we have looked at graphql as a way to get better request throughput - basically treating it as a way for clients to opt out of some of the data we generate

which can mean we do less work per request, which, hey, no reason to turn that down 😄

where are you at?

which company?

graphql has nothing to do with graphs 😂

https://coreos.com/blog/introducing-zetcd is etcd better than zk? I can see maybe for ease of deploy?

Dose anyone feel like these examples insane ? https://hnpwa.com/ The react app is poorly optimised, it has server rendering and the it re renders one more time later ?

https://www.youtube.com/watch?v=IZefk4gzQt4

very interesting stuff

@john Graphql is also a good way to avoid breaking your APIs - since you can add new attributes without worrying about payload size instead of changing existing attributes

It's really not just about performance, it's about allowing clients and APIs to evolve with less coordination and breakage