@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.
-
-
Replying to @kornelski
@pornelski that assumes your timeout semantics are the best & what everyone should be using. Could be, but too early to tell.2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@pornelski I mean, Object.observe was what everyone needed, until they decided they didn't, in the space of a year.2 replies 7 retweets 10 likes -
Replying to @jaffathecake
@pornelski and now everyone's saying we should put a virtual dom into the platform :D3 replies 3 retweets 6 likes -
Replying to @jaffathecake
@jaffathecake@domenic@pornelski Are people really saying that? :|3 replies 0 retweets 0 likes -
Replying to @KoryNunn
@KoryNunn@jaffathecake@domenic@pornelski agree with the sentiment of implementing low level only, think stuff like fetch is too high even2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@KoryNunn@jaffathecake@domenic@pornelski there are other reasons for adding high-level APIs: reduces wire weight of the Web.2 replies 0 retweets 0 likes -
Replying to @csuwildcat
@csuwildcat@KoryNunn@jaffathecake@domenic@pornelski function to promise is a 1-liner, don't think file size is a strong argument there2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@KoryNunn@jaffathecake@domenic@pornelski "fetch" was previously a 5k of code on every dynamic page of the Web, now it's gone2 replies 0 retweets 0 likes -
Replying to @csuwildcat
@csuwildcat@KoryNunn@jaffathecake@domenic@pornelski 5k as in 5000? I... no. Just no.1 reply 0 retweets 0 likes
@csuwildcat @KoryNunn @jaffathecake @domenic @pornelski perhaps fetch itself, but xhr doesn't require that many lines
6:55 AM - 7 Nov 2015
from Sydney, New South Wales
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.