my kingdom for a graphql advocate that actually understands what REST is
-
-
Replying to @steveklabnik
anyway i shouldn't shit-talk, honestly i'm mostly mad that I didn't do more to advocate and educate here
4 replies 0 retweets 1 like -
Replying to @steveklabnik
Oh man, would love to hear more on how 2 rest as intended. Between validation, err handling, docs and overfetching it seems v tricky
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
i wish i had more than jargon-dense stuff to point you at
2 replies 0 retweets 1 like -
Replying to @steveklabnik
Haha, no worries - maybs next time we hang Ill swap you a beer for an explanation on The One True REST

1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
seems good :)
1 reply 0 retweets 1 like -
-
Replying to @yoshuawuyts
here's something to chew on in the meantime: many problems occur when you design around data instead of designing around actions
2 replies 1 retweet 6 likes -
Replying to @steveklabnik
I'm like 90% sure that if we sat in a room and I explained how Diesel is designed to be used, we would just be shouting "yes!" at each other
3 replies 0 retweets 6 likes -
Replying to @sgrif
YES!
1 reply 0 retweets 3 likes
-
-
Replying to @sgrif
TOTALLY
1 reply 0 retweets 2 likes -
New conversation -
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.