> 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).
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.)
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.
"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.
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.
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.
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.
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.
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.
You would definitely care about 200ms latency.
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.
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."
A 200 ms delay would be interoperable and a 30 ms delay would be a 25% penalty to see the characters appear.
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.
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.
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.
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.
You seem to never worked on ssh connection around the world. Typing faster than your text appears on the screen is annoying.
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?)
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.
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.
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.
* 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...
(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... )
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.
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.