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
Why is it big? Why is it opinionated? I think we could do with lower level primitives, and like none of the marketing fanfare
3 replies 0 retweets 2 likes -
Replying to @yoshuawuyts @mxstbr
We need something like the leveldb ecosystem (or browserify ecosystem) but for GraphQL, so you can build your own GraphQL stack.
2 replies 0 retweets 5 likes
Yes please! Should we make an org and just start pushing modules? Always wanted to work on parsers from scratch 
-
-
Replying to @yoshuawuyts @mxstbr
I'll cheer for it, but no time to invest
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.