News for hackers. Stuff that matters.
Re:Latency matters by pasbesoin on Sunday August 20, 2017 @04:25PM (#15060103)
300 baud --> 1200 baud. Now there was a noticeable difference.

And yet, many years later, I had an impossible time explaining to a the more pointy-haired end of a large development division, why IBM Rational products might not work so well when accessed from halfway around the world. (They are/were very "chatty" between client and server, and the cumulative latency of all those round-trips simply killed you.)

Latency's still a sticking point, and a lot of people don't understand/believe it until they see it for themselves.

P.S. It may sound like I'm talking about something else -- apples and oranges. But no. What I mean is, in many domains, people don't get latency until they experience it.

I suppose that decades ago, that typewriter was just fine. Until you got fast enough. Then, as the stuck key mashes and/or other physical limits started to cap and impact your performance, you realized what people meant about "better" mechanisms.

I wonder whether in some cases, people like musicians have a better natural perspective on it. Domains where it's more readily apparent and dealt with.

Sorry, my mind's a bit all over the place, today...

Re:Latency matters by aidenn0 on Sunday August 20, 2017 @04:54PM (#15060216)
Ugh; one site I visited had the requirement that all developers work from clear-case dynamic views. The server (yes, singular server) was in a different building.

The developers had turned build-parallelism up to 99 simultaneous jobs to try to keep the CPU busy while waiting for the network, but a build was still only using about 10% of a single CPU. An incremental build would take over a minute for dependency checking, and a full rebuild would take hours.

Re:Latency matters by majewsky on Sunday August 20, 2017 @04:50PM (#15060198)
> What I mean is, in many domains, people don't get latency until they experience it.

Exactly. That's also precisely what I was going for in the article.