Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

200 Milliseconds

200ms.thenodebook.com

Post reply on HN
Print view View original

31–40 of 114 posts

Re: 200 Milliseconds

#31

Post by thenthenthen »

p-e-w wrote: post #6
zahlman wrote: post #5

Earlier quoted context omitted.

I learned three thresholds over the years. Well, one of them decades ago and the others recently. Basically: At 50ms, you notice. At 400ms, you care. At 2000ms, without output, you wonder if it crashed. (That was the old one.)

> At 2000ms, without output, you wonder if it crashed. (That was the old one.) That must have been a really, really long time ago indeed, because there are very few websites now that take less than 2000ms to load. The linked site didn’t even come close on my phone (probably 3-4 seconds), and I most certainly didn’t wonder whether it had crashed.

I dunno man, i am In China.. everything outside of it takes at least 2000-5000 ms to even start responding on a good day

Re: 200 Milliseconds

#32

Post by joshstrange »

> Violet marks the data as it moves, always top to bottom. Nothing else on the page uses that color.

Proceeds to use that color for tooltips, text color, headers, and more

This was a really cool visualization but that ^ bothered me way more than it should have.

Re: 200 Milliseconds

#33

Post by mittermayr »

LeBit wrote: post #23
beders wrote: post #4

This 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

thanks for posting this, I just shared this with everyone in the room here and nobody knew the difference.

Re: 200 Milliseconds

#36

Post by Retr0id »

> Violet marks the data as it moves, always top to bottom. Nothing else on the page uses that color.

I'm seeing 3 violet elements on my screen. "ms" in the top left, the dot next to that text, and a dot on a horizontal timeline at the lower edge of the screen. Scrolling down I see yet more violet UI elements, I assume the one on the vertical timeline represents the data, while all the others represent... other things.

It seems violet is just the accent colour used for everything, which makes it an especially perplexing comment. I can only assume the "author" never even read the LLM's output before posting it.

Re: 200 Milliseconds

#37

Post by mrloop »

antonymoose wrote: post #26
jonahrd wrote: post #14

Am 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’ve definitely had in the UX side a situation where the PM/Owner types asked me to introduce a delay in the “disabled button with loading spinner” such that the user sees it for a visible amount of time because our API was too fast for their taste.

Yes similar here, async operation that could be quick enough not to warrant a busy state, but not all the time. So rather than show a flash of busy state, that makes the ui look janky when the operation is quick, show the busy state for a minimum amount of time

Re: 200 Milliseconds

#38

Post by anon7000 »

Retr0id wrote: post #36

> Violet marks the data as it moves, always top to bottom. Nothing else on the page uses that color. I'm seeing 3 violet elements on my screen. "ms" in the top left, the dot next to that text, and a dot on a horizontal timeline at the lower edge of the screen. Scrolling down I see yet more violet UI elements, I assume the one on the vertical timeline represents the data, while all the others represent... other things…

Yeah this smells like the type of comment an LLM leaves when it gets a really specific instruction. “use one consistent color for the data timeline. Right now we’re using multiple which is confusing.” Then the LLM writes some comment that’s a mini retrospective on what happened to justify itself.

Re: 200 Milliseconds

#40

Post by Sesse__ »

inerte wrote: post #11

Back in the day "what happens when the user types a url in the address bar and press enter" used to be an interview question, and I remember nobody has ever mentioned the hardware and keyboard keys and interrupts. This post does! Pretty awesome detailed view of a request lifecycle.

I once got that question, started with the keyboard switches and the interrupts, and the interviewer sighed and asked me to get to the stuff in the browser.
Post reply on HN