Matt Krick

I've had some good chats about data expiration recently (gah that sounds nerdy). There is some data that can be long lived, such as a list of countries.Typically, long lived...

@wenzowski wow, it's like you're in my head...so here's the thing with `getUserById`. That GraphQL query _supposedly_ returns the document from the DB, but we don't know if it does...

ehhh i think that's getting too apollo-ish. the meteor folks are solving this (i think) by setting up an invalidation server. Personally, i think we should keep as much logic...

I like where this is headed, but one thing bothers me: > If we are able to rewind each client's graphql subscription to the point where that client lost connectivity...

@wenzowski i considered adding in a clock offset into the socket handshake protocol, but we decided against it. At the end of the day, it's still a heuristic & that...

@wenzowski yeah, i think this convo is getting a little too abstract for me to add much value without a concrete example. let's touch base thursday.

I don't think service workers are meant for native implementations, you'd just push a new version of the app and patch it in, yeah? On Sat, Jul 9, 2016, 1:21...

Yeah, this absolutely will exist in the application layer (ie meatier). The reason is that there are a lot of things you DON'T want to persist (the router, socket connections,...

Yeah, it's a great pattern & i'm all for moving in that direction. The reasons they currently aren't functions are: - i wrote those components before functional components were a...

it goes back to the idea of smart vs. dumb components. smart ones need lifecycle methods & HOCs & all the joys of classes. Dumb ones take in props &...