[flagged]
200 Milliseconds
71–80 of 114 posts
Re: 200 Milliseconds
#72[deleted]
Re: 200 Milliseconds
#73This is magnificent! Gave me roller-coaster ride across 40 years of gathering knowledge about computers and networks. I'm very jealous of whoever created that. Well done!
You are not jealous. You are envious. Homer explains it best https://youtu.be/Tmx1jpqv3RA
Lisa's dictionary is different from widely-used real dictionaries. Here's what Merriam-Webster says[1]:
Some assert that only envious is correctly used to describe someone who feels or shows a very strong desire for something that belongs to someone else, but in truth both envious and jealous commonly carry this meaning. Jealous alone is used to describe someone who tends to suspect unfaithfulness.
Re: 200 Milliseconds
#74Great website! Seems like the web version of this book (which is highly recommended btw): https://www.goodreads.com/book/show/17985198-high-performanc...
Re: 200 Milliseconds
#75[dead]
Re: 200 Milliseconds
#76is it bad that while this does look like a really cool method to explain a complex topic, my instinct on reading mic-droppy, RLHF AI prose is to be dismissive? there's just something about the persistent mic drops and this-not-that writing that feels so cheap I think it's because the explainer is passive, there's no interiority, it tells and doesn't show. plus, stylistically, if this were rewritten in second person (…
[dead]
Re: 200 Milliseconds
#77I don’t know how much a human was involved in making this, but clearly not enough. Some parts of the timing it’s talking about make no sense, the ordering of some parts is incoherent, and it promptly goes into unreasonable and irrelevant detail while completely missing other actually relevant aspects of that detail. For example, “HSTS preload”: it’s utterly irrelevant, because you already know it’s HTTPS; and even if it were HTTP, you should talk about HSTS, the preload list is effectively just a prefilled cache; it then adds more to that cache as you visit sites that have HSTS headers.
I’m very confident that if I looked further I’d find it riddled with errors. I just skimmed it and looked at a couple of the bits I’m most familiar with and immediately found notable errors.
Re: 200 Milliseconds
#78Am I crazy if for something like an online purchase, I kind of expect it to take a second or two to process the payment, so I would assume something went wrong if it was 200ms?
I think it was a poor choice of example, because people will expect payment to be involved. They’re actually just inserting a row into a database for the order; presumably payment is to be handled out-of-band.
Re: 200 Milliseconds
#79“On the wire, each label is stored with its length in front, 3 api 11 thenodebook 3 com 0, and the final 0 marks the end of the name, where the last dot would go.”
Am I the only one that doesn’t think of this as ‘api.thenodebook.com.’? What does the LLM mean by the zero after .com marking where the last dot would go?
Re: 200 Milliseconds
#80is it bad that while this does look like a really cool method to explain a complex topic, my instinct on reading mic-droppy, RLHF AI prose is to be dismissive? there's just something about the persistent mic drops and this-not-that writing that feels so cheap I think it's because the explainer is passive, there's no interiority, it tells and doesn't show. plus, stylistically, if this were rewritten in second person (…
Dismissive is appropriate-- "By the time the confirmation renders, the request and its replies will have crossed North America six times"
35ms times 6 is 210ms-- so just about physically possible with current infrastructure. But: this leaves no time for any of the hosts to do anything, or the wifi in the cafe, or whatever.