6 ms·
Fast Software, the Best Software (2019)
- thewebcount 4y agoI had to laugh at this: > Similarly, I started using Lightroom around 2007 because it was so much faster than Apple’s Aperture. I had the exact opposite experience. I used Aperture because it was so much faster that Lightroom. I could apply the same changes to multiple files at once, which at the time, at least, Lightroom couldn’t do. You had to work on each file separately. If you did a burst on manual, Aperture’s workflow was waaaay faster. I’m still sad Apple end-of-life’d it. Other than that I agree with the spirit of the article. I love it when software is so fast you don’t even have to think about the software. It’s so rare these days, especially with web apps.
- jt2190 4y ago> But why is slow bad? Fast software is not always good software, but slow software is rarely able to rise to greatness. Fast software gives the user a chance to “meld” with its toolset. That is, not break flow. When the nerds upon Nerd Hill fight to the death over Vi and Emacs, it’s partly because they have such a strong affinity for the flow of the application and its meldiness. They have invested. The Tool Is Good, so they feel. Not breaking flow is an axiom of great tools. To add some hard data to this, the “eight second rule” [1][2] is the maximum amount of time a user, on average, of a system can wait for that system to return control back to the user without the user having some other thought pop into their brain, interrupting their flow. [1] Response Times: 3 Important Limits (2010) https://www.nngroup.com/articles/response-times-3-important-limits/ https://www.nngroup.com/articles/response-times-3-important-... says it’s more like ten seconds [2] Website Response Times (2010) https://www.nngroup.com/articles/website-response-times/ https://www.nngroup.com/articles/website-response-times/ [3] The Need for Speed, 23 Years Later (2020) https://www.nngroup.com/articles/the-need-for-speed/ https://www.nngroup.com/articles/the-need-for-speed/ Edit: Added reference Edit 2: Additional reference Edit 3: One more reference Edit 4: I think there are still many many opportunities to improve flow in many processes. Top of my list would be keeping compile times in the single-digit seconds.
- RedShift1 4y agoThat reference is from 1993... I think people's attention span has shortened since then...
- codetrotter 4y ago> I think people's attention span has shortened since then... Unlikely. Rather, what I think has happened is that as the internet keeps filling up with more and more trash, we have been forced into being harsher with our willingness to pay attention to any one specific thing. In other words, it’s not the attention span that has changed. It’s the signal to noise ratio that keeps getting worse and worse. And that’s why you need to demonstrate value to your audience quickly or otherwise they will move on to the next thing. But don’t blame the audience for that. Blame the producers of the content.
- jt2190 4y agoWhat you’re calling “attention span” is probably more accurately called “user expectations”, or “user patience” which, obviously, can easily change. On the other hand, there seems to be a measurably consistent maximum amount of time that one can tolerate a pause without also breaking out of flow. This might be cultural, but it seems to be consistent enough that it could be physiological.
- Tempest1981 4y agoAgreed, 140 char replies instead of paragraphs, and rapidly scrolling TikTok videos. We need that dopamine.
- kaba0 4y agoThat’s a myth: https://www.bbc.com/news/health-38896790.amp https://www.bbc.com/news/health-38896790.amp
- auggierose 4y agoA friend of mine has a very interesting view with regards to flow: It is a bad thing. You don't want to be in a state of flow, because you are not thinking hard enough about what you are doing then, but just following the flow.
- taeric 4y agoThis was quite a ride. Very stream of conscious feel. Such that I don't want to get too caught in the examples. > I don’t think I’m invoking some halcyon fantasy. That said, the above is in fact a fantasy. Isn't necessarily wrong, but your average computer image in the 90s is laughably small compared to today. Such that just opening the app is likely processing more than was even possible in the 90s. This also means strategies that were fine back then, such as indexing everything on a personal computer so that it could feel snappier, work against the goal. People want faster applications, but we don't really have a route to letting them do fewer things. And I assert that is a large part of why things were maybe faster back in the day.
- keizo 4y agoAwesome! I feel like years ago there was so much focus on speed. We’d optimize websites for 56k modems. Now day much of the saas software i started using years ago has become worse with modern spa frameworks. FreshBooks was a big one. Even Shopify I find frustrating. Last couple years I’ve been on roam research for note taking. But takes more than 8 seconds to load for me. So slow I’m diy mission to make my own solution. Will have to check out nvalt though.
- bobbylarrybobby 4y agoAlso try Logseq, which is kind of a free roam. It’s fairly fast to load once it’s built its index of your notes and once opened and loaded it’s basically instant.
- aetherspawn 4y agoIt’s my observation that only developers really notice or care about speed. As long as something is “fast enough” (and the benchmark here is pretty low), most people won’t specifically choose a fast app over a slow app with more features. This means that sometimes we put too much emphasis on speed. But it is not as important to everyone else as it is to us. A product with the defining feature “it is fast”, usually fails to get noticed except by other developers.
- californical 4y agoI understand where you’re coming from, but when you have expert users of your software, they’ll be extremely sensitive to speed. Maybe a casual user won’t care, though. For example, my company has a team of experts who use our internal tool for managing company-related tasks. They use this tool every day as a core part of their job. It’s a team of literally hundreds of people who use this tool. If we add a feature which adds a click to some step of something they’re used to doing, we’ll never hear the end of it. Their team celebrates whenever we can add any sort of speed increase to something they’ve been using for a while. Adding shortcuts to common functionality is always a big user request. It’s obviously not a core part of our job to consider only performance, we add and change lots of features all the time. But if we ever neglect performance for too long, it can really start to weigh their team down. It’s interesting working so close to the people who use the software, because they don’t hesitate to give feedback like that, which you’d never get from just an internet software release. Lots of other software will have these “expert users” too, but you won’t hear the feedback.
- alkonaut 4y agoExactly this. I develop really “heavy” desktop apps for a living and this is my experience too. End users are solving a problem and that problem might be “producing a quote for a machine for a customer”. If that took them an hour in the snappy but feature-lacking old software, and a new new software does it with enormous bloat, frustrating pauses, crashes but in half the time, then customers will love it and praise it. When there is a bug report for a performance issue it’s rarely some minor delay but usually something absurd like a 15 minute wait due to something accidentally quadratic. If you ask customers of course they won’t prefer the 2 second improvement for the function they use hundreds of times per day because it only saves them a few hundred seconds. They’d rather have one more feature that saves them 30 minutes every week instead. And the thing is there is an endless number of such features even after 200 man years of dev. At the same time, as a developer I have almost no understanding for this mindset. If I was forced to work with slow and frustrating software all day I’d quit and grow potatoes for a living instead (and I use visual studio so my treshold for bloat and frustration is pretty high).
- properparity 4y agoThere's several GB/s of bandwidth from disk to screen these days, so unless you're processing several GB of data you have no excuse for anything in your programs to take more than a second. It's an insult really, such incredible waste of all the potential processing power we all have.
- commandlinefan 4y agoAnd your boss will insist that it doesn’t matter, if optimization takes more than a day to do.
- Gigachad 4y agoThey don't need an excuse. They just spend their time adding more features instead of speeding things up. And all the users flock to their tool over yours because the extra feature saved them hours in their process while your performance optimization saved seconds but took the same dev time.
- taeric 4y agoWith how much asset sizes have also grown... this isn't that unlikely, is it? A 4k screen that is refreshing at 60hz is pushing close to that in pixels than you'd think. Granted, you probably aren't changing every pixel every refresh, but the point is that there is a lot of data that goes into your screen. Even just considering data, this is probably more true than you'd realize. Probably have thumbnails for the covers/titles. Then there is the sheer volume of media. And heaven help you it your computer is still trying to index a TB or so drive. Just check how much ram your email program is using someday. Especially if you are hoping to keep an index of all email ever locally so that you can get rapid searches. The tricks that work for smaller mail boxes start to struggle with folks that insist on keeping every email over decades. Could it be better? Almost certainly yes. Unfortunately, without taking deliberate effort to do less, I don't see it happening.
- soggybutter 4y agoThe actual data that generates those pixels is likely much smaller than the pixels themselves, at least for anything hardware accelerated
- commandlinefan 4y agoI die a little inside every time I lose an argument over whether or not we should spend time optimizing our software (I lose that argument every time I have it).
- deleted 4y ago[deleted]
- taeric 4y agoPro tip, as soon as you are arguing over the code, you've already lost. Most places are so far behind on priority tasks, that to slow down and discuss/debate the priority of tasks is likely to just cause more issues. It isn't that you are even wrong. You almost certainly aren't. But nobody will wait for things to get better. If you stall out on features while prioritizing, you will lose folks. Unfortunately, I don't have a legit answer/solution. My view is it is a lot like keeping a clean kitchen. That is table stakes and assumed. Such that folks in a kitchen have to create a somewhat self cleaning flow of things. Similarly, you have to constantly optimize and clean up the code as you go. Double down on what you have, and constantly work to improve it. Not to replace it.
- dinosaurdynasty 4y agoOr just jump ship and leave someone else to clean up the mess in 3 years.
- zmmmmm 4y ago"premature optimization is the root of all evils" has a lot to answer for
- pbourke 4y agoThat doesn’t mean “never optimize”
- commandlinefan 4y agoEverybody who quotes it thinks it does.
- trabant00 4y agoI have the same obsession for speed and I have given up on desktop environments years ago, ending up on with i3 and mostly CLI. These past years I was forced for some periods to work on macOS, Windows and Gnome. While they clearly work I simply can not stand them. My muscle memory starts an application then immediately start typing and to my surprise something else happens, because the app has not started yet and I still have focus in another window or in the desktop. Or I chain keyboard shortcuts and the same unexpected results happen because the previous command has not completed. It forces me to wait and pay attention to what the system is doing and this annoys me to no end. I know plenty of people being a lot more productive than me using slow and not very ergonomic environments. So I understand this is just an obsession of mine and not necessarily justified. But once I got used to instant everything it's so hard going back.
- kovac 4y agoSame here. Nowadays, I check out CLI applications before committing to a GUI version. All those seconds I shave off by not waiting for things to load for too long, hardly having to leave the keyboard have a lot of advantage. It just takes more time to get used to initially.
- patrulek 4y agoIm so accustomed that apps doesnt show immediately, that i would feel weird if that would suddenly changed, lol.
- kaba0 4y agoHow is starting up an application faster in i3? There is a fundamental problem of slow GUI startup on desktops solved by mobile OSs, but not much faster desktop PCs.
- deleted 4y ago[deleted]
- mbrodersen 4y agoIt is my experience as a developer that the shorter the feedback loop is, the more productive I am. Fast auto tests are really useful for this. Being able to test against an in-memory DB instead of a much slower “real” DB is another example. So it is kinda obvious to me that non-developers also will benefit from fast feedback loop software.
- robinsonb5 4y agoSpeed and responsiveness are two very different things, and the latter is, I think, by far the more important where desktop computing is concerned. My complaint with modern systems (by which I basically mean anything less than 30 years old) is that I rarely feel like I have the computer's full attention.
- Diapason 4y agoResponsiveness / latency issues on mobile are literally driving me nuts. Icons and links that move between the time my brains initiate the chain of events to press on something and the time my finger actually hits the target are causing me so much frustration :( That goes beyond loss of productivity and is literally affecting my mental health.
- heywire 4y ago> Icons and links that move between the time my brains initiate the chain of events to press on something and the time my finger actually hits the target are causing me so much frustration :( That goes beyond loss of productivity and is literally affecting my mental health. I'm looking at you, Visual Studio...
- copperx 4y agoI'm just happy to hear I'm not the only one. I wish OS developers stuck to two principles: * Once an UI element that can be manipulated is displayed, it should not be moved except by the user. * Interacting with the user should have realtime deadlines.
- stephc_int13 4y agoIt is commonly agreed that the marginal cost of software is $0. And yet, for some reason, a large part of the software that we use, is, well, not great. I don't think that we're not making better/faster software because of some economical reason. I think that, sadly, we're not collectively able to do better, even if we wanted. It is the same with all complex cultural products, the marginal cost of a book is also close to zero, and yet we're not collectively producing that much great literature...
- dan-robertson 4y agoI don’t understand what marginal cost has to do with this? The marginal cost is 0 because it is the cost of copying. The cost of creating new software is not zero.
- stephc_int13 4y agoWhen you have millions or billions of customers, the marginal cost is the limiting factor. You can put a lot of R&D behind the product to beat competition. But there is not much competition on software quality. Why?
- TeMPOraL 4y agoBecause almost no software starts with millions or billions of customers. Almost no software reaches that many users. Of the software that does, a lot of it is monetized indirectly (ads, telemetry, being a "value-add" for something else). And, importantly, because as much as it's natural for software to be commoditized (thanks to low natural barriers to entry), it's also the core goal for pretty much every software company to resist commoditization. This is especially pronounced with SaaS. One way or another, the users are to a degree a captive audience. Or, in other words, the software vendors don't give a flying fuck about performance, and ergonomics in general, because they don't have to - it's not like you can just switch to a competitor. Almost none of the software used by masses has a real alternative - there are always incompatibilities, feature mismatch, and data ownership issues that make it too big of a hassle for most people, most of the time.
- dan-robertson 4y agoI sometimes wonder what would cause software to be faster (or less buggy). Websites seem to often struggle with this despite overwhelming incentives for speed (and if you browse without an ad blocker things are even slower!) where typically any internal study will show that increased speed improves key metrics. SaaS apps also seem to suffer from often being slow or buggy. I guess part of the reason is that switching is hard and performance problems may not be obvious until it’s too late. How do you even evaluate some product like Jura without using it a bunch? A demo is surely insufficient. I think people buying software are also more drawn to features than speed and maybe they are right or maybe they need to somehow be taught that they are undervaluing quality/speed, but how do you teach that? And how do you even asses software quality – how well it actually solves your problems and whether it is full of bugs – without a significant trial. Maybe there is an argument that the software is so valuable that even awful software that is not fun to use is valuable and quickly becomes hard to cut. One solution might be more heterogeneous services but then you might be paying more per-seat as you still have lots of overlap and it also sucks to have N bug trackers and M wiki/doc systems and so on. So maybe you then want services to be more interoperable but I think that may just force them all to suck.
- Mikeb85 4y agoIf all else is equal, faster is better. But there's tons of examples of slow software that is more functional and/or easier to use winning over faster software. Look at things like Ruby and especially Rails, Python, any JetBrains product, Java (fast now but back in the day quite slow), webapps in general, probably your favourite DE, etc... Life is short, optimizing everything takes time and most people don't care as long as something is usable.
- patrulek 4y agoSlow software that does the job for you or spares you hours, days or even weeks is still better than no software at all.
- pcurve 4y agoEven JIRA would be 10x better if it were faster.
- sakras 4y ago1000x yes. I always complain how JIRA is unintuitive, clunky, and confusing. But all of that would be fine if it were fast, because at least I’d be able to try more options faster figuring out which button it is I actually wanted to press.
- a3w 4y ago"should be in english", well, I am german and I have no idea what the words in my tax return mean. So to The Layman not even that may help.
- hbrn 4y agoPerformance is a feature. Unfortunately, it's not a feature that masses deeply care about, good enough is good enough.