News for hackers. Stuff that matters.
Re:How much your computer can do in a second (2015) by markstos on Saturday July 11, 2020 @03:23PM (#23805006)
Computers are also slow and sometimes getting slower, because real world applications are built with increasing layers of abstractions. while the hardware in the bottom layer is getting faster, the top layer is sometimes slower because there are so many layers and so much complexity in the stack.

Take this review of terminal emulator benchmarks: https://lwn.net/Articles/751763/

Uxterm, released in 1994 is the clear winner.

A "modern" terminal like Gnome Terminal has more than 10x the latency.

Booted an Electron app lately?

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @03:41PM (#23805206)
A few extra seconds of app startup time or an extra frame of latency in your terminal is a small price to pay for the absolutely massive difference in functionality of newer apps.

It’s fun to see how fast apps were when everything was extremely simple, but you can’t dismiss the fact that it was orders of magnitude less capable than modern software.

The bottom line is that modern apps are fast enough. I’ve never once thought that my terminal latency is too slow or that a few extra seconds of app startup time made a any impact on my day whatsoever.

The difference between the fastest and slowest terminals on that list is less than 30ms, or 3/100ths of a second. Literally less than a blink of an eye. It’s a fun study and enjoyed the article, but the reality is that it just doesn’t matter at all.

Anyone suggesting that computers felt faster a decade ago is misremembering the past. Try using a 2008-era computer with a mechanical HDD and you’ll quickly realize that apps did not launch faster back in the day.

Re:How much your computer can do in a second (2015) by antepodius on Saturday July 11, 2020 @03:45PM (#23805253)
Modern programs are 100 times slower, but they definitely aren't 100 times more functional. And speed is a part of functionality and UX! I don't want to have to use a high-powered workstation or a gaming laptop to get reasonable responsiveness in my text editor. Many Javascript-powered websites with 'fancy' canvas features are janky and slow as shit on hardware that's only 10 years old, where as websites that use HTML are still snappy and fast.

That 'nothing at all' matters when our current culture involves building layers and layers and mountains of stacks on top of software. That 30 ms compounds, because everyone working on each layer thinks 'hey, this is a bit slow, but it doesn't matter because it's only milliseconds.' Given this, it's obvious that modern software will be as slow and inefficient as it possibly can be before normal people notice and complain (usually only because they've used other equivalent software that's smoother and faster- it's easy to get used to jank, like low FPS in a video game.)

I think that people undervalue the cost of all these layers of abstraction.

Re:How much your computer can do in a second (2015) by 8organicbits on Saturday July 11, 2020 @05:37PM (#23806272)
I think users have a performance budget and once you are inside that budget, there are rapidly diminishing returns for faster speed.

> it's obvious that modern software will be as slow and inefficient as it possibly can be before normal people notice and complain

Thats sort of circular. If people don't complain there's probably better places to spend engineering effort. Besides, the slower speed is traded off for something: a safer abstraction, faster development, features the users are requesting, better security, etc.

I think some of us on HN have higher expectations for software performance than "normal" users, so we are the first to complain (or use alternate, faster software).

Re:How much your computer can do in a second (2015) by Narishma on Saturday July 11, 2020 @05:44PM (#23806332)
That's because "normal" users don't know any better. They don't know what their hardware is capable of, so they don't know that their software is slow, so they don't complain about it. If they do they usually blame hardware.
Re:How much your computer can do in a second (2015) by userbinator on Saturday July 11, 2020 @06:57PM (#23806895)
Unfortunately, from some of the other comments in this discussion, it seems a lot of developers don't know any better either --- they've never seen what real "fast" is, so they think the amount of latency they experience is normal.
Re:How much your computer can do in a second (2015) by edeion on Sunday July 12, 2020 @02:37PM (#23813605)
I sympathize to your comment... But at the same time I'm likely to be in the crowd of the unknowings. Could you suggest examples or a way to get an idea how fast computers can be.

I've recently been amazed when cracking an old cryptanalysis puzzle at what Python can do in very little time. But I have no idea what a responsive OS feels like on a general standpoint. Should I try to compile Firefox on Windows 3.1? (Just kidding on this last one, obviously.)

Re:How much your computer can do in a second (2015) by boring_twenties on Saturday July 11, 2020 @07:05PM (#23806957)
Right. Normal users think things like, "my computer is slow, it must be getting old, time to buy a new one."
Re:How much your computer can do in a second (2015) by paulie_a on Sunday July 12, 2020 @12:30AM (#23808827)
That's because normal users simply don't care nor have a reason to care.
Re:How much your computer can do in a second (2015) by abjKT26nO8 on Sunday July 12, 2020 @05:11AM (#23810032)
Just because an average user isn't able to quite put a finger on their frustration and its source, doesn't mean it isn't there. Studies show that even though users often won't be able to see that it's the performance of the program that is infuriating, they will be more nervous using it anyway and will prefer to use a faster alternative.

When phones with touch screens entered the market, we'd often put up with the latency of touch interaction, but these were irritating nevertheless. Then the early iPhones showed how low the latency could be and how much more pleasant using it is. iPhones degraded in this regard since then and Android phones didn't catch up even to the current iPhones. And I'll never use an Android, one of the main reasons being exactly this: latency.

Re:How much your computer can do in a second (2015) by fouric on Monday July 13, 2020 @02:28AM (#23817663)
> I think users have a performance budget and once you are inside that budget, there are rapidly diminishing returns for faster speed.

"Budget" is kind of a strong word. For non-hard-real-time systems, there are various points of diminishing returns on an exponential curve. However, very few interactive programs I've ever used have ever gotten to an acceptable point on that curve, given their features and the performance of my hardware. Android should not take three seconds to drop down the top drawer on a Snapdragon 617. Flutter should not introduce a noticeable latency for typing ASCII characters. Emacs should not take several seconds to display my which-key bindings. Gmail should not take ten seconds to load.

> If people don't complain there's probably better places to spend engineering effort.

For the majority of software, what's actually happening is that people don't realize that "better" is even possible.

> the slower speed is traded off for something: a safer abstraction, faster development, features the users are requesting, better security, etc.

You can make better tradeoffs, and you can make worse tradeoffs. The vast majority of modern software trades off an unacceptably large amount of performance for an unacceptably small amount of all of those things, to the point where those aren't tradeoffs - they're excuses for abysmal engineering discipline.

Additionally, most of those tradeoffs aren't actually necessary. Rust gives you speed, memory safety, and some better security all at once. Common Lisp gives you speed, memory safety, better abstractions, and faster development time. The vast majority of features shouldn't actually have a performance penalty if not being used - for instance, if I don't use the "export to PDF" feature in an office suite, there's absolutely no good reason for it to have any performance impact aside from possibly a few milliseconds of startup time. Finally, the vast majority of software slowdowns that I've experienced have had nothing to do with security at all.

> I think some of us on HN have higher expectations for software performance than "normal" users

Or we're much more aware of what hardware is actually capable of.

Re:How much your computer can do in a second (2015) by wyattpeak on Saturday July 11, 2020 @10:51PM (#23808346)
> Modern programs are 100 times slower, but they definitely aren't 100 times more functional.

I don't know if this matters. My terminal is fast enough that I've never thought about its latency. If my computer doubled in speed, I'd be happy for all of that to go to a 10% increase in terminal functionality, because otherwise it's getting wasted speeding up a task I can't tell is taking any time at all.

Re:How much your computer can do in a second (2015) by tuatoru on Sunday July 12, 2020 @12:50AM (#23808916)
Fine, your computer can render textual characters quickly enough for you. OK.

People do other things with computers. Draw. Make music. Edit music and video. Play twitch games. Get them to understand and respond to speech.

The extra layers of abstraction--specifically, the latency caused by the layers--really hurts these activities.

Saying that today's computers are better than those of the 1980s is very weak tea. They weren't good enough then, and they're still not good enough now.

Re:How much your computer can do in a second (2015) by kranner on Sunday July 12, 2020 @01:51AM (#23809186)
> People do other things with computers. Draw. Make music. Edit music and video. Play twitch games. Get them to understand and respond to speech.

But these compute-intensive tasks are more often than not implemented in lower-level, highly optimised code like BLAS, CUDA, etc. I think your overall point is valid though -- I'm looking at the Gmail tab in Chrome -- but maybe not for these particular examples.

Re:How much your computer can do in a second (2015) by adrianN on Sunday July 12, 2020 @01:04AM (#23808983)
If your software doubled in speed you could use a processors that needed only a fraction of the power your current processor needs. Computers consume on the order of 1% of all global energy.
Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @03:55PM (#23805337)
> Modern programs are 100 times slower, but they definitely aren't 100 times more functional.

My IntelliJ IDE is easily 100 times more functional than early text editors.

As for slower: Any relative comparisons are still missing the point. It’s not a relative question. It’s an absolute question: Is this fast enough?

Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.

Likewise, I don’t care if it takes 100ms or 10s to open the IDE because I’m not quitting it and re-launching it all day. I launch it, leave it open, and that’s that.

People like to glorify the good old days when apps were supposedly faster to launch, but they forget the convenience of simply leaving apps open with our oodles of RAM and letting our computers rely on suspend/wake. The longest delays in my workflow are getting my laptop out of the bag and typing in the password, or maybe downloading things from the internet.

Terminal latency or app launch time just don’t even register on the list of delays during my day.

Re:How much your computer can do in a second (2015) by justin66 on Saturday July 11, 2020 @04:11PM (#23805471)
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.

Waiting longer for a character to render to the screen than it takes to send an IP packet to a different continent and receive a reply may make you happy for some reason, but UI research indicates most people will react negatively to this.

It's worse than that. With something like Visual Studio, for example, we are sitting around waiting for local variables to update in the debugger's watch window, if we're experienced enough to know that we need to do that. This kind of thing is a genuine user interface bug: if a person doesn't realize what a slow, awful piece of software they're dealing with, they'll step step step past a variable update in the debugger, never see it happen on their screen because that only works when you pause and give the watch window time to catch up, and assume it's their program that has the problem.

People can get acclimated to dealing with very slow software, but they shouldn't have to when all the hardware performance to make it better already exists.

Re:How much your computer can do in a second (2015) by aardvark291 on Saturday July 11, 2020 @05:47PM (#23806360)
> No one really cares if it’s 1ms or 30ms or even 200ms.

You would definitely care about 200ms latency.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @10:02PM (#23808048)
Have you looked at actual end-to-end latency numbers for common operations? I’m not talking about theoretical transfer times between buffers or carefully structured synthetic benchmarks.

Using fast-twitch PC games as the gold standard, most people are looking at 60-80ms of latency on a local PC. The online game streaming services hover around 150ms, which is noticeable but still entirely usable. (Source: https://www.pcgamer.com/heres-how-stadias-input-lag-compares... )

That’s why I say that 1ms vs 30ms of terminal latency is a non-issue. When I’m typing, I’m not on a tight feedback loop with each character. I know what I’m typing, so I’m not waiting for specific letters to appear on the order of a blink of an eye.

Most of us are using 60Hz monitors (17ms per frame) with terminals that have 20-30ms of lag, with OSes that introduce slightly more delay, and so on. Then we SSH into remote servers with 50ms, or 100ms, or 200ms of latency or more. The total delay between hitting a key and seeing the letter on screen could easily be 200ms on the regular for an SSH session, yet our typing isn’t falling apart.

Re:How much your computer can do in a second (2015) by justin66 on Saturday July 11, 2020 @10:35PM (#23808249)
That PC Gamer article is not an endorsement of the idea you're pushing that all this latency doesn't matter. "Singleplayer games are mostly fine to play through the cloud, but any cloud gaming platform is going to be a no-sell for people who only play multiplayer games, even with a good connection."

I don't want to give that magazine article too much credence, but when it comes to user experience, we as an industry ought to try for more than "mostly fine" or "isn't falling apart."

Re:How much your computer can do in a second (2015) by markstos on Saturday July 11, 2020 @06:28PM (#23806699)
Typing at 100 wpm is a character about every 120 ms.

A 200 ms delay would be interoperable and a 30 ms delay would be a 25% penalty to see the characters appear.

Re:How much your computer can do in a second (2015) by 6510 on Saturday July 11, 2020 @08:03PM (#23807345)
Stella Pajunas 1946 record of 216 wpm (54,000 strokes per hour, 900 per min, 15 per second, 66 ms) is on average. She must have typed considerably faster some of the time. Anything over 40 ms is probably noticeable.

https://www.pond5.com/stock-footage/item/75268195-miss-stell...

Most wouldn't get near 1/3 of that but when the professionals say your shit doesn't work it does mean something. Trying to increase your speed using a system that cant keep up adds unacceptable annoyance.

I hereby coin the Pajunas rule at 40 ms.

Re:How much your computer can do in a second (2015) by formerly_proven on Saturday July 11, 2020 @04:09PM (#23805455)
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.

I actually do, because I'd like for IntelliSense and clones to save me some typing, but often that doesn't quite work out, because they're too slow (inconsistently slow, too). I'd also like it if my IDE or Word editor could highlight errors in realtime, but in reality it's more like a couple seconds delayed, so I have to navigate a significant distance back to correct them, instead of being able to fix it almost on the spot.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @04:13PM (#23805487)
That’s a different topic, thought. The OP posted about typing latency, not the latency of additional complex features.

It’s not exactly fair to claim that software is “slower” than old software when the software you’re comparing to doesn’t have those features at all.

Re:How much your computer can do in a second (2015) by justin66 on Saturday July 11, 2020 @04:48PM (#23805812)
UI latency is UI latency, and the problem in both cases is due to what markstos mentioned in his initial comment: the increasing internal complexity of the software stack used to develop the software. It's not like modern hardware isn't fast enough to do literally everything that needs to be done locally with minimal UI latency.
Re:How much your computer can do in a second (2015) by 6510 on Saturday July 11, 2020 @08:05PM (#23807364)
I'm guessing 1000x
Re:How much your computer can do in a second (2015) by marcosdumay on Saturday July 11, 2020 @05:00PM (#23805925)
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters onLet’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. the screen.

I see you are not much into modern IDEs.

Visual Studio used to be a great perpetrator here. The 2017 version doesn't do it much, but I'm not rolling the dice on the 2019 one as far as I can avoid.

I do sit around waiting for Atom to interpret my keystrokes all the time, but it's never much more than a couple of second.

Oracle's SQL Developer is another one that can't keep-up with the keyboard. It's also not as slow as Visual Studio, but it does break a flow. And it loses characters when it's blocked.

Re:How much your computer can do in a second (2015) by llukas on Saturday July 11, 2020 @04:38PM (#23805712)
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.

You seem to never worked on ssh connection around the world. Typing faster than your text appears on the screen is annoying.

Re:How much your computer can do in a second (2015) by wolco on Saturday July 11, 2020 @07:44PM (#23807231)
Or played with a 300 baud modem
Re:How much your computer can do in a second (2015) by lowercased on Saturday July 11, 2020 @09:22PM (#23807813)
> Let’s be honest, none of us are sitting around waiting for our complex IDEs to render characters on the screen. No one really cares if it’s 1ms or 30ms or even 200ms.

I do regularly on my 2019 MBP - I 'only' have the basic SSD and 'only' 16 gigs of memory. Usually Jetbrains stuff, but things freeze up/pause on VSCode and Eclipse as well too.

I'll then be told "oh, must be your hardware", but this is a "feature" I've noticed of... not just JVM software, but probably MacOS in general - sporadic system pauses. SSD makes it more bearable, certainly, but it's not "this" hardware - I've had probably 8 different mac systems since 2008, and they all do this. But... in the 15+ years of Windows and Linux systems before that, similar issues. I see it on other peoples' systems too, but they seem to be able to bite their tongue, or genuinely don't notice (or don't care?)

Re:How much your computer can do in a second (2015) by Retric on Saturday July 11, 2020 @04:01PM (#23805387)
Are you talking pre 1980’s as early? Because IntelliJ vs EMACS is hardly a 100x improvement.
Re:How much your computer can do in a second (2015) by xaedes on Saturday July 11, 2020 @04:43PM (#23805748)
If you don't care, that is fine. But please don't spoil it for the ones caring. Don't argue against it if you don't care
Re:How much your computer can do in a second (2015) by flukus on Sunday July 12, 2020 @01:18AM (#23809031)
> My IntelliJ IDE is easily 100 times more functional than early text editors.

Maybe more than text editors, but I doubt it's even twice as functional as eclipse circa 2005. As slow and bloated as it was for it's time it had all the modern features and ran on machines with (I think) 128MB of RAM.

Re:How much your computer can do in a second (2015) by adrianN on Sunday July 12, 2020 @01:08AM (#23808994)
The OOM killer regularly kills IntelliJ on my 16GB RAM Macbook pro when I have the audacity to leave it open while I try to compile something else. That really sucks, so I use vim whenever I'm familiar enough with the code to not need very intelligent autocompletion.
Re:How much your computer can do in a second (2015) by mlyle on Saturday July 11, 2020 @10:05PM (#23808069)
I can definitely feel the difference getting my terminal echoes over 40ms of latency and feel impeded. Not ridiculously impeded, but...
Re:How much your computer can do in a second (2015) by blackrock on Sunday July 12, 2020 @03:18AM (#23809519)
Is the browser able to render all that JavaScript code in parallel on multi-core CPUs?
Re:How much your computer can do in a second (2015) by 2OEH8eoCRo0 on Saturday July 11, 2020 @05:04PM (#23805967)
The market decides how much latency is acceptable.

Computers are made to do work, not stroke some purist programmer ego. Computers and the software they run today enables us to do far more than we used to. If they didn't we wouldn't bother.

Re:How much your computer can do in a second (2015) by csande17 on Saturday July 11, 2020 @05:20PM (#23806113)
> Computers and the software they run today enables us to do far more than we used to.

This is true in the broadest sense -- certainly calc.exe is better than an abacus! -- but I'm not sure it's true on the 10-to-20-year timescale people are usually thinking about when they say software is declining. I use exactly zero features of my computer that were not available in Windows Vista, released in 2006.

Re:How much your computer can do in a second (2015) by 8organicbits on Saturday July 11, 2020 @06:10PM (#23806574)
Look at Thunderbird since 2006 to see how the product has grown. Sure, we all used "email" in 2006, but email clients were terrible.

* 2007 - message tagging https://website-archive.mozilla.org/www.mozilla.org/thunderb...

* 2009 - search result filtering https://website-archive.mozilla.org/www.mozilla.org/thunderb...

* 2010 - mail account setup wizard https://website-archive.mozilla.org/www.mozilla.org/thunderb...

* 2012(ish?) Support to send large attachments via 3rd party, I.E. box.com https://website-archive.mozilla.org/www.mozilla.org/thunderb...

* 2013 - ignore threads https://website-archive.mozilla.org/www.mozilla.org/thunderb...

* 2014 - attachment reminders https://www.thunderbird.net/en-US/thunderbird/31.0/releaseno...

* 2016 - subject line spell check https://www.thunderbird.net/en-US/thunderbird/45.0/releaseno...

* 2018 - message templates https://www.thunderbird.net/en-US/thunderbird/60.0/releaseno...

* 2019 - mark all folders for account read https://www.thunderbird.net/en-US/thunderbird/68.0/releaseno...

Re:How much your computer can do in a second (2015) by csande17 on Saturday July 11, 2020 @06:47PM (#23806835)
I'm not saying that newer versions of Windows than Vista don't include additional features. Off the top of my head, Windows 10 includes Cortana and Paint 3D. I just don't ever use or care about them, just like how I've never had occasion to "mark all folders for account read".

(And wow, I guess I was right to buy Microsoft, because they were eleven years ahead of the curve on message templates: https://support.microsoft.com/en-us/office/send-an-email-mes... )

Re:How much your computer can do in a second (2015) by 8organicbits on Saturday July 11, 2020 @08:06PM (#23807372)
Hmm, now I'm curious. What does the software stack you are using in 2020 that hasn't had a new feature (that you use) since 2006 look like?

I can't tell if you are a linux user running a command line mail reader or if you use Win10 to run modern web sites in the browser.

Re:How much your computer can do in a second (2015) by phist_mcgee on Saturday July 11, 2020 @07:06PM (#23806964)
This smacks of capitalist supply theory that is completely reductionist, and doesn't include outside concepts like vendor lock-in, price-tiers etc
Re:How much your computer can do in a second (2015) by userbinator on Saturday July 11, 2020 @06:44PM (#23806807)
Try using a 2008-era computer with a mechanical HDD and you’ll quickly realize that apps did not launch faster back in the day.

I'm still using one! And it's fast enough for what I do with it --- mainly native development in C, but also the usual communications: email, IM, watching videos, reading content-focused web sites (not web apps), etc. Since I don't use anything bloated, 4GB of RAM is more than enough and the HDD remains silent most of the time.

I experience far more delay and frustration using a much newer, ~1-year-old work laptop with much faster CPU and several times the RAM, but with Electron apps or any other "modern crap" that has a fraction of the functionality. The most vivid recent example is the YouTube "new design" --- it is disturbingly slow and dumbed-down. On this new machine I still experience lag often when interacting with bloated JS web apps, which can't even keep up with my typing speed (web-based Outlook is a notable example of this.)

Even presumably-native applications are not immune to this cancerous growth. UWP is another example; the Win10 calculator somehow needs a loading screen, and so does the Settings app, whose featureless pathetic excuse of a UI somehow manages to be less responsive than the classic Control Panel, which opens basically instantly and is just as responsive to input.

Related: https://news.ycombinator.com/item?id=18506170

Re:How much your computer can do in a second (2015) by abjKT26nO8 on Sunday July 12, 2020 @05:04AM (#23809999)
> the Win10 calculator somehow needs a loading screen

This right here made my day. No further comment on the state of technology today needed.

Re:How much your computer can do in a second (2015) by Junk_Collector on Saturday July 11, 2020 @03:58PM (#23805359)
A really good typist runs around 100 words per minute. 30 millisceonds of delay vs 2 is enough that the terminal won't keep up with the person working on it. And these are TERMINALS, other software has gotten much worse in typing latency.
Re:How much your computer can do in a second (2015) by onion2k on Saturday July 11, 2020 @04:57PM (#23805896)
No one is typing 100WPM in a terminal though. If you're writing a document use a word processor that's optimised for input speed more than your terminal app, or use a faster terminal app with fewer features that slow it down. Leave the terminal apps that can only handle 50WPM alone so the rest of us can have the useful stuff.
Re:How much your computer can do in a second (2015) by markstos on Saturday July 11, 2020 @06:32PM (#23806713)
I prefer Vim for writing. Plenty of writers prefer text editors to word processors for writing.

No need to be either/or. Fast AND useful is possible.

Re:How much your computer can do in a second (2015) by adrianN on Sunday July 12, 2020 @01:10AM (#23809003)
Are you saying that Microsoft Word has a lower latency than Emacs in a terminal?
Re:How much your computer can do in a second (2015) by userbinator on Saturday July 11, 2020 @06:49PM (#23806848)
I can type prose at ~150WPM pretty much continuously, with bursts of 200+ in short phrases.

I have never measured how fast I type in a terminal, but it's definitely far more bursty, and that's when lag becomes far more unacceptable.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @04:02PM (#23805396)
I think you’ve misinterpreted these results. The delays don’t mean that the terminal will start missing keys or won’t keep up with the operator.

Humans don’t type on a tight feedback loop of waiting for characters to pop up on the screen, obviously.

We also need to keep the big picture in mind. If you’re using a 60Hz monitor, it’s only going to update every 17ms anyway. Add buffering and even pixel transition latency to the equation and the end-to-end latencies are even higher.

You’re not going to notice the difference between a terminal editor with 20ms of latency and one with 15ms of latency.

Re:How much your computer can do in a second (2015) by kqr on Saturday July 11, 2020 @04:43PM (#23805750)
> Humans don’t type on a tight feedback loop of waiting for characters to pop up on the screen, obviously.

Actually, yes, they do. I can't dig up the reference right now, but evidence indicates that for touch typists, error rates rise as input latency increases.

Apparently, seeing your characters appear on screen is a cue the brain uses together with mechanical feedback and other things to do small muscular corrections on the fly.

So there's nothing obvious about a claim to the contrary.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @10:09PM (#23808095)
> Actually, yes, they do. I can't dig up the reference right now, but evidence indicates that for touch typists, error rates rise as input latency increases

On what magnitude, though? Can you please share the actual paper?

My claim was that 15ms vs 20ms input latency (actual numbers from the parent comment’s link) won’t make a difference. That shouldn’t be controversial, because all of our standard 60Hz monitors only refresh the frame every 17ms anyway.

For reference, blinking your eyes takes about 100ms. The difference between 15ms and 20ms latency is only 5ms, or literally 1/20th of the blink of an eye.

That difference isn’t going to change your typing error rate.

1 second of input latency will, but that’s orders of magnitude higher than anything discussed here.

Re:How much your computer can do in a second (2015) by formerly_proven on Saturday July 11, 2020 @04:05PM (#23805426)
Nah, I've written texts in certain Word editors and IDEs and looked up mid-paragraph for spellchecking or re-reading it, just to see the computer still spurting out letters on the screen slower than an half-asleep OM morsing it.

Sometimes these multi-core 4+ GHz fast marvels of nanotechnology simply can't keep up with a meatbag on caffeine punching keys for food. Sad in a poetic way.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @04:15PM (#23805501)
That’s an entirely different issue. The original link discussed typing latencies in the range of 1-30ms. That’s a fraction of the blink of an eye.

If your computer is so slow that it takes multiple seconds for letters to appear, something else is happening. Even old “fast” software is going to feel laggy if your system is so bogged down that it can’t keep up with typing inputs on that level.

Re:How much your computer can do in a second (2015) by Junk_Collector on Saturday July 11, 2020 @04:34PM (#23805667)
I'm taking issue with latency in general and it's dismissal. There are reams of ergonomic targets, data, and guides on user interface latency that are just completely ignored these days. A terminal is close to the simplest possible interface whose job is to provide input and output to a user with as little disruption as possible. 30 ms is in fact noticeable.

Here is a short video from Microsoft (about 10 years old now) on the experience of using a touchscreen with 100ms of delay vs 1ms showing the steps in between. The difference is extraordinary for the user even if the end result is the same. https://www.youtube.com/watch?v=vOvQCPLkPt4

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @10:34PM (#23808246)
> Here is a short video from Microsoft (about 10 years old now) on the experience of using a touchscreen with 100ms of delay vs 1ms showing the steps in between. The difference is extraordinary for the user even if the end result is the same.

That’s additional input delay, not absolute latency.

More importantly, the visual effect you’re seeing isn’t the perception of input delay. It’s the positional difference between the finger location and the box location. Typing in a terminal doesn’t have the same visual difference. In fact, using a mouse doesn’t have the same visual difference because your finger isn’t right next to the screen for comparison. Try dragging a window across your screen right now. The “lag” is easily on the order of the 100ms shown in this demo, but you won’t find it anywhere near as disorienting because your finger isn’t on the screen for visual reference.

It’s not possible to have 1ms lag unless you have a 1000Hz screen and zero processing time for the inputs.

Compare that to the standard 60Hz displays that most laptops and cellular phones use. At 60Hz, the screen only updates once every 17ms. Add input lag, processing lag, rendering delay, buffering delay, and other delays and it’s nearly impossible to go from input to screen action in under 30ms. Most games are on the order of 60-80ms.

The individual pixels in your LCD can’t even toggle from black to white in 1ms.

A lot of the HN comments here are misunderstanding the time scales involved in all of this. For reference, a blink of an eye is about 100ms

Re:How much your computer can do in a second (2015) by chmod775 on Saturday July 11, 2020 @04:47PM (#23805803)
> The original link discussed typing latencies in the range of 1-30ms.

30ms is close to extremely annoying. You will notice a 30ms latency in a video game when moving around, turning etc.

Having that kind of latency on mouse movement can make it close to impossible to hit fast targets in a shooter for instance, because it will destroy perceived synchronicity of input with the response, confusing your brain and destroying immersion.

The same can be said about navigating in a terminal based text editor. A few milliseconds of delay can take your brain from "I am the cursor" to "I am controlling this cursor, which respond a short time after I execute a certain action". Frustrating.

What is also super frustrating to me when using vim in a slow terminal is that I will consistently overshoot the line where I meant to place the cursor. I realize most of the latency probably comes from my brain and nervous system, but a few ms can be just enough to make the cursor end up in the next line instead.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @10:12PM (#23808124)
> 30ms is close to extremely annoying. You will notice a 30ms latency in a video game when moving around, turning etc.

That’s not true, though. It takes more than 30ms just to render your frame, deliver it to the monitor, and wait for a screen refresh.

PC Gamer recently measured some actual latency results. They found 60-80ms was fairly standard for lag between input and on-screen events: https://www.pcgamer.com/heres-how-stadias-input-lag-compares...

Notably, the online game streaming services have on the order of 150ms of latency. It starts to become noticeable, but it’s still entirely playable for many. If the gamers can handle 150ms of input lag, certainly we can deal with 30ms while typing in our consoles.

Re:How much your computer can do in a second (2015) by formerly_proven on Sunday July 12, 2020 @09:31AM (#23811169)
> PC Gamer recently measured some actual latency results. They found 60-80ms was fairly standard for lag between input and on-screen events: https://www.pcgamer.com/heres-how-stadias-input-lag-compares....

So, I just made the following experiment. I filmed my screen and mouse at the same time, then grabbed a window and flicked as fast as I could.

On my 120 Hz screen the window starts moving within five to six frames (at 240 frames per second video) of the mouse moving, meaning an end-to-end latency of around 20 ms.

Windows 10, nVidia graphics card with hardware scheduling, Ryzen CPU, using the cheapest 120/144 Hz screen that was available at the time (<200 €).

Re:How much your computer can do in a second (2015) by chmod775 on Sunday July 12, 2020 @12:25AM (#23808799)
> That’s not true, though. It takes more than 30ms just to render your frame, deliver it to the monitor, and wait for a screen refresh.

For cheap non-CRT screens you are correct. Otherwise, not so much. And even if you're using a cheap screen, latencies of 50ms vs 30ms (typical numbers for vsync on vs vsync off) definitely have an impact on player performance besides just feeling more/less sluggish. See also my post here: https://news.ycombinator.com/item?id=23806493

> https://www.pcgamer.com/heres-how-stadias-input-lag-compares...

That PC gamer article is horrible and amateurish. There's no mention of what vsync/nvidia driver settings they used etc. Also games like Destiny are pretty far from being optimized for low input lag.

With CRTs and properly optimized/coded games like CS you can achieve input lag as low as 5ms (though that's just the time until the monitor begins drawing the first rows of pixels after the change).

Here's a few links on input lags measurements:

http://www.esreality.com/post/2691945/microsecond-input-lag-...

https://forums.blurbusters.com/viewtopic.php?f=10&t=1381&hil...

http://esreality.com/post/2640619/input-lag-tests-ql-csgo-q3...

People doing A/B tests:

https://forums.blurbusters.com/viewtopic.php?f=10&t=1134

And a demonstration that even input lag as low as 10ms can be noticeable:

https://www.youtube.com/watch?v=vOvQCPLkPt4

Re:How much your computer can do in a second (2015) by occamrazor on Saturday July 11, 2020 @05:23PM (#23806137)
30ms is the video refresh latency with a typical 60fps monitor and a double framebuffer, without any latency from the application itself. Most videogame players have a similar setup and they evidently don’t find it “extremely annoying”, ot they would have stopped playing a ling time ago.
Re:How much your computer can do in a second (2015) by chmod775 on Saturday July 11, 2020 @06:02PM (#23806493)
>Most videogame players have a similar setup and they evidently don’t find it “extremely annoying”

I do. And it's not just me. There's a reason many players of fast twitchy shooters are playing either without vsync, or vsync + uncapped FPS[1] (+ the newer "low latency" modes of modern drivers, but mileages vary).

This stuff has already been well understood, A/B tested, and documented back in the CS1.6 days. A CS player who hasn't at least put some thought into it or doesn't care is extremely rare. And CS is still topping the steam charts daily at up to a million or more concurrent players.

People have no issues noticing vsync ON vs OFF (well that's easy) or vsync + uncapped vs capped FPS in blind tests. I challenge you to get a friend to perform a blind test with you to try this for yourself.

There's also a reason that reduced input lag is part of the sales pitch of everything from monitors and GPUs to input devices. It's because people do care (irrespective of the effectiveness of what vendors try to sell you). Hardware manufacturers, driver developers, and game studious aren't putting time and money into this because nobody gives a damn.

[1]: vsync + uncapped FPS is called "fast" vsync in nvidia driver settings

Edit: I'm going to give an example of why these numbers matter in fast shooters.

Suppose you pit two players of equal skill against each other, each having a reaction time range of 300ms - 400ms, and whoever reacts first wins. One player is playing with a total input latency (mouse to screen) of 50ms, and the other with a latency of 30ms (these are typical numbers of vsync on vs vsync off).

The player with 20ms less latency is going to win about 70% of the time.

Re:How much your computer can do in a second (2015) by formerly_proven on Saturday July 11, 2020 @08:58PM (#23807687)
"30 ms here", "one frame of latency there" is exactly how Android (and some PC apps) end up with touch latencies in the triple digits.

FWIW most people who semi-seriously game don't use 60 Hz screens and don't use normal V-Sync. They use 120-155 Hz screens, or increasingly 240 Hz screens and fast v-sync (=driver-managed triple buffering combined with a frame queue length of 0 or 1). They also try to run the game with as high FPS as possible.

Re:How much your computer can do in a second (2015) by 65536 on Saturday July 11, 2020 @04:04PM (#23805418)
I have definitely used software where it started lagging behind significantly while I was typing. That kind of stuff is absolutely infuriating.
Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @04:06PM (#23805434)
That’s a very different problem than the 15-30ms latency discussed in the link above.
Re:How much your computer can do in a second (2015) by MaxBarraclough on Saturday July 11, 2020 @05:51PM (#23806399)
> absolutely massive difference in functionality of newer apps

As antepodius already said, this isn't really true.

Slack has a few more features than the chat applications of 15 years ago. I suspect it may also lack a few of their features. It uses vastly more resources.

Visual Studio is a full IDE, with more features than the Electron-based Visual Sudio Code.

Re:How much your computer can do in a second (2015) by PragmaticPulp on Saturday July 11, 2020 @10:06PM (#23808077)
> Slack has a few more features than the chat applications of 15 years ago. I suspect it may also lack a few of their features. It uses vastly more resources.

Yet Slack has massively more adoption than any previous chat app. That’s not by coincidence: They made it at least an order of magnitude more useful for their target audience.

Slack is, without a doubt, orders of magnitude more complicated than previous-gen chat apps. It’s not like they could have built it with a handful of engineers operating some IRC servers.

However, I was specifically referring to text editors (responding to the OP) vs modern IDEs. As you said, full IDEs have vastly more features than a simple terminal program or basic text editor. That’s where the order of magnitude more functionality comes from.

Re:How much your computer can do in a second (2015) by flukus on Sunday July 12, 2020 @01:26AM (#23809074)
> Yet Slack has massively more adoption than any previous chat app

Maybe just, by virtue of there being more internet users these days. But you're underestimating just how ubiquitous IRC was, it was near universal. Sure there was no single app that everyone used, but that was a feature. With slack we've gained a few features but regressed in so many other ways.

Re:How much your computer can do in a second (2015) by wolco on Saturday July 11, 2020 @07:37PM (#23807185)
I still use a machine like that. They were faster hands down.

Even faster a commodore 64. Flick a switch the os is ready. Load geos now you have a basic windows.

Re:How much your computer can do in a second (2015) by tonymet on Saturday July 11, 2020 @10:07PM (#23808085)
Sorry the opposite is true here . Desktop gui apps from the 90s were much more advanced , with more features and more responsive
Re:How much your computer can do in a second (2015) by deiznof on Saturday July 11, 2020 @05:04PM (#23805968)
At this point I'm not even sure what people mean when they say "slow" or "poor performance", since I have a mid-tier PC and have no problems with VSCode or anything else. Everything starts fast and I have no latency issues when typing. Imperceptible differences in time are not something I would ever consider a performance problem, certainly not in the case of UX.

Same thing with memory usage. If I'm not even using a third my RAM with my browser, editor and a few other random things open I'm not going to complain about something being a "resource hog".

Re:How much your computer can do in a second (2015) by atq2119 on Sunday July 12, 2020 @02:36AM (#23809360)
There are two possible reasons for this.

One, you simply may not know better. If you've never experienced the typing latency of an 80s or 90s style system, you may not have a reference point for low latency. Not saying this is necessarily the case for you, but I suspect it's the case for some people.

Second, people genuinely have different perception. The most stark example of this in practice for me was the perception of flicker on CRTs. Many people claimed to just not notice flicker at 60Hz, while for me going back from 100Hz to 60Hz was unbearable for longer amounts of time. I'm sure similar differences exist with our perceptions of latency.

Re:How much your computer can do in a second (2015) by FpUser on Saturday July 11, 2020 @04:46PM (#23805791)
>"few extra seconds of app startup time"

This is atrocious. Barring the cases when the application loads and deciphers some massive dataset upon startup normal application should start instantly or close to that.

Re:How much your computer can do in a second (2015) by hedora on Saturday July 11, 2020 @08:53PM (#23807657)
My desktop is about 10 years old with an old SSD, but /home is on a btrfs raid NAS on spinning disk (over WIFI). It runs a minimalist WM. I paid about $1000 for it (and a few hundred later for the boot SSD, a new video card, and a 802.11ac pcie card)

It is significantly faster at all mainstream tasks than my late 2018 $2700+ work laptop running $VENDOR_DEFAULT desktop environment.

Re:How much your computer can do in a second (2015) by znpy on Saturday July 11, 2020 @05:12PM (#23806043)
I would be okay and favour the tradeoff... But I recently decided to eradicate gnome-calculator in favour of xcalc because gnome-calculator (probably due to being packaged as a snap) was taking 5-10 sec to show up whereas xcalc is literally instantaneous.
Re:How much your computer can do in a second (2015) by pjc50 on Sunday July 12, 2020 @06:10AM (#23810274)
Quite a lot of the new functionality is "value subtraction": adware or spyware that makes the user experience worse.

The recent fiasco where Facebook accidentally broke startup for all apps using their toolkit is a good example.

Re:How much your computer can do in a second (2015) by drew-y on Saturday July 11, 2020 @03:55PM (#23805340)
VSCode, an Electron app, is my favorite application of all time. It starts up quickly and is incredibly responsive in use.

It's easy to customize, there are loads of community extensions, and it's free. When abstractions allow software to have a flourishing community like that, to me its worth the cost.

Re:How much your computer can do in a second (2015) by GuB-42 on Saturday July 11, 2020 @04:19PM (#23805542)
Still slower than Sublime Text. I gave VSCode a try and this is the reason I went back to Sublime Text. I already have a ST3 license so I didn't care about "free". Feature wise and community wise they are both very good, with maybe a small advantage for VSCode.

It isn't slow but it has noticeable micro stuttering. Enough to be annoying when coming from an editor that doesn't have this problem.

EDIT: Emacs feels surprisingly slow for such an old software, though not in the same way as VSCode. Vim is fast but I never really got into it.

Re:How much your computer can do in a second (2015) by drew-y on Saturday July 11, 2020 @07:46PM (#23807244)
I was actually a Sublime Text user before VSCode. I'll be the first to admit Sublime Text is faster. VSCode still wins for me in a landslide. Sublime text's performance is just not enough of an advantage over VSCode's feature set and extension marketplace.

VSCode is free as in freedom, which is pretty important to me for a tool that I completely rely on for work.

Edit: I'll also add that I've never found VSCode's performance to be a problem. It's pretty rare for me to find a file that's big enough to make VSCode choke. I suppose it might happen with multi-gigabyte log files. But usually I just use journalctl to browse those.

Re:How much your computer can do in a second (2015) by ahelwer on Saturday July 11, 2020 @09:39PM (#23807922)
Easy way to make vscode choke: hold down ctrl+alt+up/down to enable multi-line editing. Let the cursor run up or down the screen for a bit. It lags a lot.

This might be because of the vsvim plugin though, itself the source of a lot of lag.

Re:How much your computer can do in a second (2015) by drew-y on Sunday July 12, 2020 @03:56PM (#23814259)
Yeah that's very odd. I use that feature a lot and have never had it choke. But I also don't use vsvim.
Re:How much your computer can do in a second (2015) by blackrock on Sunday July 12, 2020 @03:50AM (#23809652)
The killer-app feature for me on VSCode, is the ability to auto save over SSH.

I tried other things like Emacs, in Tramp mode, terrible. Gawd, it’s so terrible. It took me several days to figure out how to set it up. The documentation and examples were poor or non-existent. And when I finally got it to work, I was thoroughly underwhelmed.

I looked for something else, and found VSCode had a feature for SSH. I downloaded the module, connected to my SSH server, and I was operational in a few minutes. The difference between this and Emacs, was night and day.

And VSCode had all the other nice features, like code folding, syntax highlighting, and especially, function definition lookup, which makes it so convenient to work with your functions library.

Re:How much your computer can do in a second (2015) by Smithalicious on Saturday July 11, 2020 @04:00PM (#23805375)
Emacs has all those properties except fast startup and it's like 40 years old. Added layers of abstraction aren't to thank here.
Re:How much your computer can do in a second (2015) by usr1106 on Saturday July 11, 2020 @04:19PM (#23805545)
Re:How much your computer can do in a second (2015) by jsrcout on Saturday July 11, 2020 @05:23PM (#23806140)
Wow, thanks for that link! Great stuff.
Re:How much your computer can do in a second (2015) by millimeterman on Saturday July 11, 2020 @04:22PM (#23805574)
Emacs is just the VSCode of yesteryear - there's a reason people used to joke about "emacs" standing for "emacs makes a computer slow".
Re:How much your computer can do in a second (2015) by wwright on Saturday July 11, 2020 @05:34PM (#23806246)
Eight megabytes and constantly swapping
Re:How much your computer can do in a second (2015) by Retric on Saturday July 11, 2020 @03:59PM (#23805362)
Meanwhile I find VSCode to be a slow resource hog. I can only assume your simply so used to terrible applications that your standards have slipped.
Re:How much your computer can do in a second (2015) by drew-y on Saturday July 11, 2020 @07:35PM (#23807177)
It's ok to have a different opinion. But you shouldn't assume your experience invalidates my own.

I've used a large number of text editors. Vim, Sublime Text, TextMate. I loved them all, and they are of course much faster and less resource intensive. I would still pick VSCode over each of them when given the choice.

VSCode strikes a great balance. Ironically I find it far more performant and smoother than Visual Studio itself.

Re:How much your computer can do in a second (2015) by dijit on Saturday July 11, 2020 @09:10PM (#23807744)
> Ironically I find it far more performant and smoother than Visual Studio itself.

it does so much less that it's like comparing notepad to pycharm.

Your exact use-case may not be impacted too much, which is great - but I know a lot of programmers who use Visual Studio's entire feature set including a lot of custom C# plugins and it's not comparable at all. (Intellisense, and native step-through debugging/disassembly to begin with).

VSCode is a text/code editor that has some nice bolt-ons.

Visual Studio is a fully fledged IDE with advanced feature sets for large shared projects.

Re:How much your computer can do in a second (2015) by FpUser on Saturday July 11, 2020 @04:49PM (#23805826)
>"Meanwhile I find VSCode to be a slow resource hog"

Same here. It does start instantly on my laptop though

Re:How much your computer can do in a second (2015) by hinkley on Saturday July 11, 2020 @04:12PM (#23805475)
I wish I had a reference for this. I should probably go looking for it.

Someone claimed that the speed of software doubles every 18 years. I presume they meant this from a theoretical/algorithmic standpoint, rather than median behavior of software systems.

As computer speed progress slows, we should expect more effort to go into this kind of work. It seems like we are paying a good bit of attention lately to extracting the embarassingly parallel parts of our code, and chipping away at the easy end of the shared state spectrum. Amdahl tells us there is gold to be had but the digging gets harder very quickly, so I'm curious to see what will be next, after the great artists steal more of the lessons of Elixir/Erlang, Rust and friends.

Re:How much your computer can do in a second (2015) by cellularmitosis on Saturday July 11, 2020 @04:18PM (#23805541)
I believe that quote refers to compiler optimizations producing a net doubling of performance every 18 years. In effect, “software” doubles in performance.
Re:How much your computer can do in a second (2015) by hinkley on Saturday July 11, 2020 @04:36PM (#23805691)
Could be.

But then like adding lanes to a highway, having more supply just leads to a disproportionate increase in demand, frittered away in a million dependencies that nickel and dime us to death.

Re:How much your computer can do in a second (2015) by CyberDildonics on Saturday July 11, 2020 @10:05PM (#23808062)
Bill Joy talked about scientific computing software advancing like that. Academic papers and new techniques filter down and the same things can be done faster.
Re:How much your computer can do in a second (2015) by seangrogg on Saturday July 11, 2020 @10:26PM (#23808202)
You don't get promoted for removing actions.

And now to drink away that depressing thought.