2014-03-04 23:30:06 +0000 <hyperthunk> just worth thinking about
2014-03-04 23:30:19 +0000 <hyperthunk> but using builder (?) is a non-starter, if it's fast and thread safe
2014-03-04 23:30:31 +0000 <hyperthunk> our serialisation (using binary) is slow atm
2014-03-04 23:30:33 +0000 <hyperthunk> very slow
2014-03-04 23:30:52 +0000 <hyperthunk> and our wire format is very very verbose
2014-03-04 23:30:54 +0000 <carter> you mean STARTER
2014-03-04 23:30:57 +0000 <carter> not non starter
2014-03-04 23:30:58 +0000 <hyperthunk> both are massively high priority
2014-03-04 23:31:03 +0000 <hyperthunk> sorry
2014-03-04 23:31:11 +0000 <hyperthunk> yeah, what I really mean is a no-brainer!
2014-03-04 23:31:13 +0000 <hyperthunk> hahaha
2014-03-04 23:31:29 +0000 <hyperthunk> yeah, not non-starter. we should do that if it's known to work and is stable and well maintained
2014-03-04 23:31:30 +0000 <carter> hyperthunk: au contrair, better types === easier docs and less "oh for that tranaspor you need that one special trick"
2014-03-04 23:31:32 +0000 <hyperthunk> and faster, obviously
2014-03-04 23:31:44 +0000 <hyperthunk> carter: you don't need that one special trick today though
2014-03-04 23:31:47 +0000 <hyperthunk> I men
2014-03-04 23:31:48 +0000 <hyperthunk> mean*
2014-03-04 23:31:52 +0000 <carter> idk
2014-03-04 23:31:53 +0000 <hyperthunk> it's got nothing to do with the transport
2014-03-04 23:31:56 +0000 <carter> well
2014-03-04 23:32:03 +0000 <hyperthunk> terminology fail here I think
2014-03-04 23:32:08 +0000 <carter> hyperthunk: lemme reframe it this way
2014-03-04 23:32:17 +0000 <carter> every time you reply to an email on list
2014-03-04 23:32:30 +0000 <carter> thrres a lot of methodologcal rules of thumb latent in those replies
2014-03-04 23:32:39 +0000 <carter> those should be reflected back in the APIs
2014-03-04 23:32:39 +0000 <hyperthunk> carter: yes, _that_ I am aware of
2014-03-04 23:33:04 +0000 <hyperthunk> if there's really a way to say "this API _only_ takes fully evaluated thunks" then that's great
2014-03-04 23:33:11 +0000 <hyperthunk> I don't see how you can do that with data families
2014-03-04 23:33:20 +0000 <carter> oh, strict data types :)
2014-03-04 23:33:25 +0000 <hyperthunk> you can say "it's got to be NFData" but that's a different matter
2014-03-04 23:33:26 +0000 <hyperthunk> RIGHT
2014-03-04 23:33:28 +0000 <hyperthunk> exactly
2014-03-04 23:33:32 +0000 <carter> well
2014-03-04 23:33:34 +0000 <hyperthunk> just use strict data types
2014-03-04 23:33:34 +0000 <carter> heres the thing