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

51–60 of 114 posts

Re: 200 Milliseconds

#51

Post by inigyou »

thenthenthen wrote: post #31
p-e-w wrote: post #6

Earlier quoted context omitted.

> 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

That is your government trying to block you

Re: 200 Milliseconds

#52

Post by pennomi »

foolswisdom wrote: post #42
anon7000 wrote: post #38

Earlier quoted context omitted.

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.

Claude seems to do this all the time. That, the empty words and the increased self initiative of claude were all reasons I decided to just use codex (now merged into GPT).

Claude using documentation and comments as its personal diary is one of the most infuriating behaviors it exhibits.

Half the time it’ll record some temporary implementation quirk, which later sessions interpret as infallible product design requirements. Absolutely unsustainable.

Re: 200 Milliseconds

#54

Post by jameshart »

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?

It only inserts a sku and a quantity into a Postgres database - yeah, there’s a few things missing from this purchase scenario.

Might have been better to have made it clicking a ‘like’ button.

Re: 200 Milliseconds

#55

Post by taneq »

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…

Also “the clock at the top is exact” but the clock (on my phone, at least) is at the bottom. Still cool though!

Re: 200 Milliseconds

#57

Post by jameshart »

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’ve always wanted a version of this sort of a timeline that really lets you zoom out and in to the fractal complexity of it all. Right at the end we’re talking about updating the DOM and rendering… there’s a whole Unicode and font stack and rasterization process happening in there.

Re: 200 Milliseconds

#58

Post by taneq »

felooboolooomba wrote: post #2

> The person who clicked noticed no delay. Just to be the "actually..." guy: People notice 200ms delay. It's just that in cases it doesn't cause any bad feelings."

I was expecting the site it’s talking about to have faked an instant response. Ironically, sometimes it goes the other way and UIs have to fake a small delay otherwise the user won’t believe it’s actually done anything (although arguably the real issue there is lack of positive feedback, not response time.)

Re: 200 Milliseconds

#59

Post by clickety_clack »

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 don’t think a visa transaction can go faster than about a half second so definitely something off there.

Re: 200 Milliseconds

#60

Post by stratts »

foolswisdom wrote: post #42
anon7000 wrote: post #38

Earlier quoted context omitted.

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.

Claude seems to do this all the time. That, the empty words and the increased self initiative of claude were all reasons I decided to just use codex (now merged into GPT).

Codex does this too, I've noticed. LLMs seem to love documenting irrelevant implementation details in what should be user-facing text. I guess because the context is overwhelmingly the technical side of things, so without a later directive to steer it, that's what's most likely to come out.
Post reply on HN