While I may not agree with most implementations, I do think GraphQL is valuable as a spec. Reduces both bytes sent, and no. of round-trips.
-
-
Replying to @yoshuawuyts
For public APIs that is. Also the fact that it sends JSON back is great imo. Tho really, the current implementations seem overly complex
2 replies 0 retweets 13 likes -
-
Replying to @mxstbr @yoshuawuyts
I've been loving the Apollo stack but it does get fairly complex the further you go in. I guess the same could be said for any big codebase?
2 replies 0 retweets 4 likes -
Replying to @mxstbr @yoshuawuyts
The reference implementation isn't too complex, IMO. You basically write resolvers for types. Not much more to it.
3 replies 0 retweets 0 likes -
Replying to @HenrikJoreteg @mxstbr
There's a lot of computer words in there tho. Also mixes sync/async styles, and has lots of imports. Not had for a ref, but can be better
1 reply 0 retweets 1 like
Would love to have individual tokenizer / parser / resolver modules. Rn everyone just seems to wrap the reference implementation 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.