yosh

@jaffathecake I still think hooks for UI are a separate problem (we implement UI progress using different handlers than for network timeout)

@pornelski I dunno, sounds like the thing that tracks progress could be the same thing that tracks lack of progress

@jaffathecake so UI hooks to just read percentage, and xhr wrapper hooks to time progresses, but these are separate independent libraries.

@pornelski I disagree here, the low level should be done first, and both progress and lack-of-progress are ident streams that observe

@pornelski the higher level can be built on top of those concepts

@jaffathecake I'd prefer timeout semantics like I've described to be built in, so that I don't have to wrap and pipe everything myself.

@pornelski that assumes your timeout semantics are the best & what everyone should be using. Could be, but too early to tell.

@pornelski I mean, Object.observe was what everyone needed, until they decided they didn't, in the space of a year.