he/him 
@rreverser Token retrieval APIs are trivial to implement. @ben336 @slicknet
-
-
Replying to @RReverser
@rreverser Because if I was going to do linting then it wouldn't be on tokens, it would be on some other data structure.@ben336@slicknet2 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck@ben336@slicknet Again - why reinvent that? (except as of https://en.wikipedia.org/wiki/Not_invented_here …)2 replies 0 retweets 0 likes -
Replying to @RReverser
@rreverser I don't really follow. I've listed the clear advantages and reasoning.@ben336@slicknet1 reply 0 retweets 0 likes -
Replying to @RReverser
Sebastian Retweeted Ben McCormick
@rreverser You jumped in without reading all the other tweets. https://twitter.com/ben336/status/619664165335113729 …@ben336@slicknetSebastian added,
1 reply 0 retweets 0 likes -
Replying to @sebmck2 replies 0 retweets 0 likes
-
Replying to @RReverser
@sebmck@ben336@slicknet If the answer is Flow, it can be very well integrated with escope in the same way as babel.1 reply 0 retweets 0 likes -
Replying to @RReverser
@rreverser No it can't. You need a data transmission layer which means async io, completely changes the architecture.@ben336@slicknet2 replies 0 retweets 0 likes
@rreverser You would communicate with the flow server over an RPC. @ben336 @slicknet
5:42 PM - 10 Jul 2015
0 replies
0 retweets
0 likes
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.