@jmoiron hopefully someday google maps will understand that despite being only 1km away, Astoria takes ages to get to from UES
@jmoiron either all this tinnitus spam I get is oddly specific or I'm missing out on some newfangled euphamism
@jmoiron need to add this emoji to unicode, it means "system wide failure at catastrophic scale" https://t.co/1hDwnlDIBO
@jmoiron @dgryski I've used redeo in production for over a year and had no issues with speed or reliability.
@jmoiron @peterbourgon this survey felt like it was asking "how much like npm/pip/gem should we make dep management" and my answer is "not very"
@jmoiron @PreetamJinka "lots of redirtying of already dirtied pages" is TSDB 101 but sure why not postgres
@jmoiron RT @jeffbarr: New from @datadoghq - #AWS Lambda Integration / support for Serverless Arch - https://t.co/qkgoNrBQzq https://t.co/6UJ5dyMIkA
@jmoiron @sdboyer but you're right, the edge weight is a measure of coupling, and existence may be too rough an estimate.
@jmoiron @sdboyer there are _definitely_ other heuristics to be had here, eg. don't want to pull in lib upon lib upon lib for 1 func
@jmoiron @sdboyer Yeah I think the edge existing implies a coupling, how tight it is would be how many different exported things it uses..
@jmoiron @sdboyer eg, you use a big framework, but a standalone lib can be simpler in the long run than an add-on, because no relationship to sync
@jmoiron @sdboyer also 2 deltas might be useful, one for what it adds new and one for the complexity it adds to your existing graph
@jmoiron @sdboyer delta is more useful I think, esp if you consider the case of replacing one lib with another
@jmoiron @sdboyer it would be interesting to see if it's useful, there's not a lot out there to help you determine the cost of pulling in a new lib
@jmoiron RT @johnbarton: Reading https://t.co/D7PURMk00I from @jmoiron and I think we really need to make the "Moiron Score" a real thing.