@ssylvan @Jonathan_Blow I've now watched to 1:08:00 and still no mention of I$ being blown out?
-
-
Replying to @rygorous
@ssylvan@Jonathan_Blow He mentions that there *is* an I$, but I don't see him saying that this is actually a problem on this code.1 reply 0 retweets 0 likes -
Replying to @rygorous
@ssylvan@Jonathan_Blow (In fact he just specifically said "let's *pretend* this was the problem here")1 reply 0 retweets 0 likes -
Replying to @rygorous
@ssylvan@Jonathan_Blow I'm now around 1:14:00 and he's doing the outro... still not sure what you mean?1 reply 0 retweets 0 likes -
Replying to @rygorous
@ssylvan@Jonathan_Blow Closest is https://youtu.be/nXaxk27zwlk?t=1h6m40s … which he then immediately follows up with "If this was the real problem we had.."2 replies 0 retweets 0 likes -
Replying to @rygorous
@rygorous@ssylvan@Jonathan_Blow He rather specifically says, "Why is this code slow? It's slow because it is waiting for cache..."1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@ssylvan@Jonathan_Blow where? I have watched through this thing and haven't noticed that. Timestamp please!1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@ssylvan@Jonathan_Blow It's the one you just sent! You linked to it. He immediately says, "Why is this code slow?"1 reply 0 retweets 0 likes -
Replying to @cmuratori
@rygorous@ssylvan@Jonathan_Blow "Code is slow because it is waiting for caches. And one of those caches is..." etc.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@ssylvan@Jonathan_Blow 1:06:47 "If this was the real problem we had" implies it's not!1 reply 0 retweets 0 likes
@rygorous @ssylvan @Jonathan_Blow That's very misleading - I mean I didn't even take it that way...
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.