10 ms·
"Software is getting slower more rapidly than hardware becomes faster."
- sambapa 3y agoI'm really waiting for The Great Hardware Stagnation. We have accumulated too much cruft. This stagnation could last for, idk, 20 years, to really optimize everything. Then we could start Another Era Of Hardware Progress.
- myself248 3y agoI've been saying for a while now, that developers and their managers should use a low-spec machine, let's say the 5th-percentile of whatever their users are using in the field, at least one day a week. This might force some reprioritizing of performance and efficiency goals. As long as devs spend their days with bugattis while writing software for corollas, this will continue to get worse.
- lasereyes136 3y agoThat was true when most software was desktop software. Most software now are Web Apps so the local speed of the development computer means less. 30 years ago there was a big difference between the performance of a current computer and a 3 year old computer. These days there isn't a huge difference and a well maintained older computer can still perform well as compared to a current computer.
- playingalong 3y agoIs it the devs who need to ride the Corollas? Or is it the managers and/or the testers?
- stcredzero 3y agoThe devs. They have the true power to do something about it. Basically, that way you tighten that iteration loop for optimal efficiency to nearly nothing.
- btbuildem 3y agoHave testers not suffered enough?! It's the devs that need the slow machines -- they're in the tightest feedback loop, and directly empowered to optimize performance.
- threatofrain 3y agoOptimizing performance is very nontrivial and often means writing custom stuff, which will deeply affect TCO. It’s fine for devs to sympathize with users, but in the most ultimate perspective the users are actual or potential customers of the business and not your clients. In other words, the business should have ultimate authority and responsibility to structure incentives and pursue priorities. Up until the engineer crosses over a boundary and becomes part of leadership.
- loglog 3y agoIn enterprise software, optimizing performance usually means removing the custom stuff.
- deleted 3y ago[deleted]
- threatofrain 3y agoI think it's the opposite. With exception to startups like Bun, it's big businesses that can marshall enough financial justification to do high-performance rewrites and maintain custom code. A common complaint on HN is bloated web performance. Surely we don't think the web is bloated because of too much custom code as opposed to too many off-the-shelf components?
- nirvdrum 3y agoIt may be non-trivial to dig yourself out of a performance hole if you didn’t account for performance at all in the design. The pervasive idea that you can make it fast later virtually never pans out. In many cases, taking performance into account up front adds little overhead and won’t appreciably affect the design. But, if you codify some algorithmically inefficient approach into your public API, you’re going to find that hard to unwind. The engineering team should advocate for that when designing the product.
- striking 3y agoIf you'll still pay for the software I write, why should I care?
- wanderr 3y agoI hate this for developers. I got to experience this first hand because I had a boss who thought like you. Developers generally need to run a bunch of resource intensive tools to build the application in the first place, so an underpowered system will already be choking. It means their app will feel slow no matter what. So then when they run it and it's slow, they will shrug and say it's just slow because their system is slow. There might be a case for specifically running testing on a slower machine, though.
- cuu508 3y ago> It means their app will feel slow no matter what. How so? Do the heavy tools need to run alongside the app? Are you thinking of something like Android emulator? For that scenario, keep the beastly workstation, but switch to a $150 phone.
- _heimdall 3y agoI think its reasonable to say anyone evolved in the product should regularly use the end product on low end hardware. I wouldn't expect devs to run full development environments on low end hardware unless they themselves are building dev tools.
- toast0 3y agoI think it's reasonable to have a separate machine to do building on. You can include a push to the target in the build script, or use network mounts or something. Remote debugging is a thing, if you need to use a debugger but don't have the resources to debug on the target. But I disagree with your basic assumption that > It means their app will feel slow no matter what. If you can make it feel fast or at least responsive on your underpowered machine, it should feel super fast on everything else. Even today's slowest machines can run some things fast. It does depend a bit on your market though; it might not be worth the effort, but there's a lot of applications out there that could use some speed.
- kayodelycaon 3y agoDocker is slow enough without giving me crippled hardware.
- ryandrake 3y agoFully agree. Developers should regularly dog-food their software and they should have to do it on the lowest-spec machine/phone that the software claims to be supported on. Too many developers run their creations on their fully-maxxed-out development workstation beast machine, observe it runs fast enough, and call it a day.
- SubjectToChange 3y agoIt's a tremendous waste of money for a business to spend expensive developer time waiting on garbage workstations. Simply targeting benchmark/latency metrics is enough.
- myself248 3y agoPrecisely, but how well is that working out in practice? Forcing them to CARE about targeting benchmark/latency metrics is the sticking point. And that requires shoving their face in it for long enough that it becomes unbearable.
- AA-BA-94-2A-56 3y agoAs a web developer, it’s less about me caring and more about my boss caring. If anything, give the C-suites the shitbox laptops.
- eviks 3y agoIt's only a waste if it doesn't lead to better performance driven by personal negative experience
- Timon3 3y agoIs there some way to reliably simulate this, e.g. using a VM? It would be nice to have IDE, build tools etc. using all available speed while running the output as if it was on slower hardware.
- dist-epoch 3y agoAssign a single core to the VM, 8 GB of RAM. Surely you can also bandwidth limit the storage.
- _heimdall 3y agoI've had better success with VMs for performance dogfooding in a desktop environment. On mobile I've always gone back to testing on low end hardware, there are just too many inconsistencies when trying to simulate slower performance, outdated OS problems, touchscreen drivers, etc.
- testless 3y agoFor Webapps, chrome can emulate slow network and/or devices. For Kubernetes or Docker compose, you can restrict resources, I believe.
- apienx 3y agoDev Containers are cool. There’s a VSCode extension.
- kevingadd 3y agoSometimes developers and managers can't fix it. (second-hand information) Android was at a smoothness disadvantage vs iOS for a long time, because it was never an organization level priority for devices to scroll at >= 60hz without stuttering. Then some executives went "why is scrolling so bad on our phones but not on Apple's?" and suddenly it became a priority. I remember before the priorities changed, some of their graphics programmers were very frustrated that they didn't have the freedom to invest in fixing it.
- testless 3y agoFor Web apps, I think using lighthouse and the chrome tools to emulate slow devices goes a long way.
- londons_explore 3y agoIdeally they have a fast machine to run compilers and shit on, but then the actual product they are developing runs on a slow machine. Luckily, Chrome has a feature to deliberately throttle the CPU and network speed for precisely this reason. Sadly hardly anyone uses it.
- groestl 3y ago> Sadly hardly anyone uses it. It would be great if Chrome's Developers would use something similar to run Chrome itself.
- londons_explore 3y agoBy the way... For anyone reading this wanting to solve exactly this problem... This feature is currently part of devtools. But if it could be enabled as part of Chromes policy engine, then IT departments could enable it by default for all developers, managers, and everyone working on the product, specifically for only web URL's of the product itself. So: If you want to help solve the fact computers are slow for everyone, probably one of the most impactful things you could do is to send a PR to the Chromium project to let the network and CPU slowdown code[1] be possible to activate from the policy code [2]. [1]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/network/network_state_notifier.cc;l=209;drc=e036a8e7200d41afa08898ccede1324355ed5741 https://source.chromium.org/chromium/chromium/src/+/main:thi... [2]: https://source.chromium.org/chromium/chromium/src/+/main:chrome/updater/policy/service.h;l=83;drc=e036a8e7200d41afa08898ccede1324355ed5741 https://source.chromium.org/chromium/chromium/src/+/main:chr...
- hinkley 3y agoThis may end up being a place where some of the newish ideas in IDEs can help. You want the fast machine because you want the code-build-test cycle to be fast, but for immediacy reasons we want a little more hardware than we really need so that we don't get bogged down too badly in worst-case scenarios. So when we run the software on the machine along side this behemoth, we may or may not see something comparable to the users. And then we also like for interactions to go faster for us so that we can quickly get to the end of a thought without having to drop everything and fix the slowness first (also, too few of us actually know how to fix the slowness instead of papering over it). As we lean into multiple machines, or at least virtual machines, I can see a sliver of hope here where we offload rather large chunks of the IDE to resources the application itself cannot 'see', due to partitioning, remote calls, or both. Things like running the language server elsewhere, or the application in a container.
- alkonaut 3y agoI use a reasonably beefy machine to develop “heavy” desktop software. It’s definitely the kind discussed in this article. I find it frustrating that it has noticeable input lag even with moderate workloads for exactly the reasons mentioned. But then you talk to end users and it turns out they work 80 hours on one big document with input lag of several seconds. Some actions can take 15 seconds. It’s mad. It’s larger than anything we imagined anyone to work on. It must be infuriating. And they don’t get beefier machines despite it being an instant cost saving. Because software is seen as magical anyway. They do in two days what would take 50 days to calculate by hand! That’s fast! So when you ask them what to prioritize surely they say “make it faster with heavy documents”? No, they want more features. Because a feature can save then days or weeks or months. A faster program just saves them hours. So I sort of understand them (and why we build software that grows slow).
- HeyLaughingBoy 3y agoAnd this is exactly why you talk to users. You get the most unexpected feedback that you'd never have guessed in a million years.
- Xeamek 3y agoThe problem is how we (devs) slowly but surely conditioned users (and even other, new coming devs) so that people don't even know how fast computers actually are and how crazy it is that those things are as slow as they are. So when it comes to performance, people don't even know that things could (should?) be exponentially faster.
- alkonaut 3y agoImagine the first bank where a monthly job took a roomful of smoking people took four days complete with calculators. In comes IBM and says "we can sell you a machine that does this in five minutes". Sure it'll weigh a ton and cost a fortune, but you'll see it's worth it. So they buy it. The machine performs half of 12 boring jobs at the bank needed every month. But there is still another half dozen jobs the IBM still cannot do. It doesn't have the punch cards. So the roomful of smokers does the rest of the jobs in a couple of weeks, ready just in time to start over with next months tasks. Should IBM make the machine or its programs twice as fast, or have twice as many features, even if the programs are half as fast? They should double the amount of features. And double it again, and again, and again...
- Neikius 3y agoPlease go and do what you suggest for 8 hours a day then come back. Giving bad tools to any professional is a bad idea for productivity. We have other ways of checking if software is slow. It is all a question of company priorities as there are no professional standards whatsoever established. And companies ofc go for spend the least they can get away with.
- butz 3y agoIn some big business companies this is solved by pre-installed "security software" that usually takes up about half of the RAM, sometimes even more, and is using a measurable chunk of CPU all the time.
- metalliqaz 3y agoI totally feel this comment, myself being a corporate drone that has to deal with this software. Between disk encryption, anti virus, IT asset management, data custody tracking, etc; my PC is as slow as molasses. Unfortunately I think its slow in a different way that low-spec machines are slow. Mine is very slow on IO ops, but I have 32GB of RAM and a 20-core i7, so plenty of resources available even after all the BS.
- rahkiin 3y agoI could use some tips on talking with IT about this as it cripples work performance
- toolslive 3y agoYou think it's IT pushing this? They are just executing orders.
- theatomheart 3y agoYes and no. Businesses have cyber insurance policies. In a world of frequent ransomware attacks, many security policy changes have been mandated by insurance companies, and for legitimate reasons.
- hulitu 3y agoThe attacks are not frequent enough. And the IT is already outsourced (because cheaper).
- MichaelZuo 3y ago
- JodieBenitez 3y ago> As long as devs spend their days with bugattis while writing software for corollas, this will continue to get worse. That's BS. Like there was no such things as featuritis and unreasonable schedules.
- myself248 3y agoWhen performance is a non-issue enough that schedules and features are ALLOWED to be the priority, they will always win. When performance HURTS so much that they are forced to care about it ABOVE the pressure of features and schedules, then we get somewhere. Which is why browser emulation doesn't work -- it doesn't inflict enough pain. They wince through it, say "well that was awful, back to rushing more features out the door" and forget about it.
- JodieBenitez 3y ago> When performance HURTS so much that they are forced to care about it ABOVE the pressure of features and schedules, then we get somewhere. That won't happen because management people are the ones with Bugattis. You got the wrong target.
- dijit 3y agoI work in video games. My Lead QA recently accosted me regarding the low-spec machine being unusable. (it's an 11th Gen i5, 16GiB Ram and an Intel ARC A750). He wanted me to get a better machine. I politely declined indicating that this is the low spec machine, he made a fuss and I said if we can't make it run on that then we should stop making video games. For context: The weak part for us was the CPU; the ARC A750 is a pretty poor GFX card but it should never be unplayable, it's around RTX 2060-2070 in speed, not unreasonable for a low spec machine. It's very easy just to say yes to creeping performance demands, even in video games that are historically highly optimised. (obvious caveat here: sometimes things are not well optimised and hugely neglected)
- Xeamek 3y agoGames are lightyears ahead of 'common use software' when it comes to usability. Sure, there are bad, poorly optimized or simply unplayable games out there. But still, even the lowest of them are still insanely complex when compared to the software we are complaining here, ie. text communicators.
- alentred 3y agoAgree. And there is also actual progress in the rendering engines. Modern AAA games are incomparable with what they were 10 or 20 years ago. Most desktop apps on the other hand... Yes, of course they have more features than their predecessors. But still they have the same core functionality, though. A word processor is still a word processor, but modern ones come with a latency on an every button, including the old ones that didn't have it before.
- timw4mail 3y agoThe A750 is not that poor of a GPU either. If that's considered low-end, then gaming on a Steam Deck, or a budget gaming computer is impossible.
- Ekaros 3y agoTo me those specs sound pretty decent... i5 isn't Atom or Celeron... Intel Arc is bit weird, but not iGPU...
- Euphorbium 3y agoThe issue is not the difference in machines, the issue is that I need to run multiple apps and not just dedicate all of the resources of my machine to your app.
- vikingerik 3y agoAnd don't forget phones in all of this as well. Mobile developers have the latest and greatest and fastest, but half your users will be on $60 Android pre-paid or entry-level phones that can be a factor of four or more slower than what you've been developing on.
- scruple 3y agoWe have minimum specifications we meet for our software (games) and a suite of old desktops (that I occasionally have to go kick) that run CI performance tests for us. It's not much investment, outside of the initial setup and generating test cases / automation, but it's been worth it for us. It's helped us find a lot of problems over the years.
- deleted 3y ago[deleted]
- jiggawatts 3y agoGenerally I’ve found that the biggest causes of performance issues are network latency and missing database indexes. Slow laptops for developers test neither of those scenarios! The solution is to use network emulators that can buffer packets and simulate latency. (Or just put servers in a remote cloud region instead of the local LAN.) For databases, the trick is to give developers a slow database server with full-sized data. Don’t use empty databases (schema only) during development!
- lucas_membrane 3y ago> "developers ... should use a low-spec machine" That is exactly what Michael Brown, founder of Central Point Software, insisted on back in the 1980's when they were producing the #1 selling PC software according to PC magazine. An informed market also helped. A little bit earlier there was a comparison review published (same publication, IIRC) of the top spreadsheet programs (spreadsheets being the reason office workers were getting PC's). MBA Analyst was the best, in everything except speed, much better functionality than Visicalc, MS Multiplan or Lotus123, and only slower by a difference few users would notice without a stopwatch. MBA Analyst vanished in a flash after that article came out, and it found such a stable oblivion that it doesn't even show up on google nowadays.
- PaulHoule 3y agoBut software developers do builds on that machine. I’ve quit workplaces because they wouldn’t upgrade my computer, in one case I just bought my own. It”s a chronic problem that software developers get a hand me down craptop from a salesman who couldn’t sell.
- 1vuio0pswjnm7 3y agoAs a user of "low-spec" computers, I try to avoid software written by teams of developers working under managers. Most of the programs I use day-to-day are (a) decades old, from the distant past before so-called "tech" companies existed and/or (b) written primarily by single authors, often as a hobby or as a result of itch-scratching. Some of them are written by me. When I occasionally compile and run the scripts and small programs I write on more powerful computers, I am amazed at the speed. Everything I write is compiled on "low-spec" computers. Today's hardware is amazing.
- earthling8118 3y agoWhere are all of you people working where you get crazy machines? I've gotten a laptop at every job that didn't let me use my own computer. They're never fast at all even when they use supposedly higher end hardware. Not even a fraction of the speed of my regular workstation.
- Log_out_ 3y agoBut it's easier to optimize something to good on best in class, then to go to that from rest in case. Might even expose a developer as incompetent when it comes to hardware optimized software. Slow software bad developers.
- mananaysiempre 3y agoAka “craptop duty”[1]. [1] https://css-tricks.com/test-your-product-on-a-crappy-laptop/ https://css-tricks.com/test-your-product-on-a-crappy-laptop/
- gregors 3y agoI don't think developers are the problem here. Most developers I know would love time to work on optimizations. "When can we get this shipped???? We need it yesterday", I suspect business attitude plays the greatest role.
- ado__dev 3y agoI feel like nobody really cares about optimization anymore. It's just "ship, ship, ship, move faster, ship." So there's a lot of tech-debt, a lot of unoptimized code, and a lot of "just make it work", at the expense of writing software that utilities the hardware properly. On the flip side of that though, hardware has gotten fast enough, where this is possible.
- ymerej 3y agoDoesn't it all boil down to economics in the end? When I worked at AOL, QA was very important/valued because our SW was shipped on CDs (I know, I know), and every bug/update cost us users because we had to download an update at modem speed. Now that I work on a web development team, bugs are easily fixed by an update. So who cares if there's a bug? We can just update the site. There are other costs, of course -- if we tolerate lots of bugs and tech debt, making development slower, we will evenually have our lunch eaten -- that's economics too. Users/customers accept a certain level of quality, and it doesn't make short-term economic sense to provide more.
- ado__dev 3y agoAbsolutely. It really is a double-edged sword and there's so many factors that play into. Do you spend a ton of time writing beautifully optimized code, but ship less features, or do you ship a ton of features that mostly work. I feel like if you take too long to ship, a competitor will eat your lunch. But if everything you ship is trash, then a competitor will also eat your lunch. All about finding that balance I guess.
- strangattractor 3y agoTotal agree. There was a time when the deployment cycle was so long it was painful to ship poorly performing buggy software. Now people let their users do the testing.
- wredue 3y agoIt’s actually worse than you think. Functional programmers have been in a massive propaganda campaign to actively paint optimization not just as “usually not necessary”, but actually as a negative thing. Ask any developer what they think of optimization, and the vast majority will respond “optimization is the root of all evil” or some other nonsense variant. Now that they’ve successfully paint optimization as bad, they’re working on painting any profiling or measurement at all as bad. They need this because the performance characteristics of pure functional programming is pretty dogshit. You also find hordes of developers that selectively care. Watching Python developers shit on Java for “being too slow” is getting pretty old.
- wanderr 3y agoI recently switched an old PHP project from sending me emails directly via SMTP to using mailgun. At first I tried to use their SDK. It pulled in like a dozen dependencies. I gave up on that idea and replaced it with a simple curl call.
- testless 3y agoI had very similar experience with npm. Especially when you need to merge all the security updates for the sdk and all their dependencies. I also prefer interacting with the api, if it is straightforward.
- onion2k 3y agoIt feels true but I don't think it actually is. Especially given the fact Wirth wrote it in 1995 which is practically the pinnacle of what most of us perceive as when software was actually fast.
- trealira 3y agoIt could have been true the whole time. Perhaps software has been getting slower, and it's gotten so much slower and more bloated that 1995 software seems lean and fast by our modern standards, when by 1980s Wirthian standards, it wasn't.
- bhouston 3y agoThis has been the story since the beginning unfortunately.
- dist-epoch 3y agoI'm not convinced this is true and not just a popular argument. Just today I've processed 4 TB of JSON data, in Python, on a desktop computer. That would be crazy to imagine 10 years ago. Yes, many cores, fast SSD, etc. Maybe it should be 20 TB if ultra optimized, but the capability advance is incredible. Yes, apps maybe start slowly, but now everybody can easily edit HD video on their mid-range laptop.
- grumpyprole 3y agoA complied language can be over 1000 times faster than Python, so maybe the dual core from 10 years ago would have been fine.
- surfingdino 3y agoYes. I am writing more code in Golang for that reason. I'll take the 100x increase any day.
- xcv123 3y ago> That would be crazy to imagine 10 years ago We had this in 2013. Would have handled the job with a well written parser. https://www.intel.com/content/www/us/en/products/sku/77779/intel-core-i74960x-processor-extreme-edition-15m-cache-up-to-4-00-ghz/specifications.html https://www.intel.com/content/www/us/en/products/sku/77779/i...
- wharvle 3y ago"Computers are in fact very fast" and "certain programs do in fact demonstrate that" and "the real-world experience of using computers for most people is that performance is largely treading water or going backwards" due to a boom in software inefficiency, can all be true at the same time.
- anthk 3y agoNo, not crazy: https://adamdrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html https://adamdrake.com/command-line-tools-can-be-235x-faster-... ~10 years ago I parsed 15GB of Windows binary logs with xargs, grep and strings(1) in minutes. Minutes. Less than 1/4 of an hour.
- lbhdc 3y agoI wonder if everything becoming a saas has to do with that. Everyone has added a bunch of network hops to services that (probably) have to make a bunch of network hops. It will be interesting to see if that changes in a post zero interest rate world. Will people do more locally in their programs instead of reaching out to third party saas to save money? Will performance be a value add in competitive niche markets?
- reddit_clone 3y agoI hate how much compute/energy is chewed up by anti-virus and 'defender' software (Malware ?)
- eimrine 3y agouse FOSS
- ironmagma 3y agoSoftware does more than it used to. Try using an old PC, say Windows 98. You will be amazed how little functionality there is. It didn't even come with full-screen desktop wallpaper.
- sirjaz 3y agoNo we have the cloud and everyone just uses the web. We don't need speed ;)
- richiebful1 3y agoIs this really true that software is getting slower? I've been using a budget Windows 10 desktop lately, and I'm shocked by how fast everything is running: ESRI ArcGIS, Firefox, code editors, etc. I remember having a budget desktop PC back in the mid 2000's and it was a significantly worse experience on very basic workflows (Excel, regular web browsing, etc)
- crazygringo 3y agoAgreed. Between SSDs, blazing faster home DSL internet, and multicore processors, using a computer is much faster than it's ever been before. Sure there's more software bloat, and webpage bloat, but if anything the overall user experience has gotten faster. And that's even with resource hogs like Retina displays and 4K video. Like, go look up YouTube videos of people using older systems (not VM's). A Mac in 1989 takes forever to open an application, open a file, or save a file. The HDD clicking away... Remember how Word implemented "fast save" to shorten save times, which appended a lot of changes rather than rewriting the whole file? Nobody worries about that today.
- Xeamek 3y agoCounter argument - HN post from 6 months ago: "Windows NT on 600MHz machine opens apps instantly. What happened?" https://news.ycombinator.com/item?id=36446933 https://news.ycombinator.com/item?id=36446933
- crazygringo 3y agoBut here's a counterpoint from within that same thread: https://news.ycombinator.com/item?id=36447704 https://news.ycombinator.com/item?id=36447704 There's also the note that this person was running NT on a later system far, far faster than it was designed for: https://news.ycombinator.com/item?id=36447461 https://news.ycombinator.com/item?id=36447461 When we're trying to reproduce what older systems were like, it's important not to be combining software from earlier era on hardware from a later one.
- troupo 3y ago
- danielovichdk 3y agoI am pretty certain that if you stripped away most of the abstractions (law of leaky abstractions) and wrote software that was optimized to the hardware design per se, then you be able to write software that is blazingly fast. Look up how many steps your favorite language is going through before hitting the cpu. No wonder shit is slow when all we do is stacking abstractions and not concentrating on removing them.
- codexb 3y agoIt’s similar to Jevon’s Paradox in economics. More efficient use of a resource results in people using more of that resource, not less. Creating more efficient gasoline engines doesn’t cause people to use less fuel, they all just buy larger cars now.
- Xeamek 3y agoRelated: https://news.ycombinator.com/item?id=35351760 https://news.ycombinator.com/item?id=35351760
- kburman 3y ago"Troubleshooting performance issues is often skipped in favor of migrating applications to better hardware platforms."
- pmontra 3y agoAnecdotally this does not apply to my laptop from 2014. It was born with a HDD and upgraded to SSD a couple of years later. It still feels fast enough and, more up to the point, it doesn't feel to get any slower by the years. Actually it's getting faster and that was the feeling I had with my previous laptop from 2006. OK, I've been using Linux on them since January 2009, so no Microsoft software (but Teams is slow, I installed it a couple of years ago and uninstalled it.) I used Ubuntu until one year ago, then Debian. In all those years JavaScript browser engines got much faster for everybody, not only for me. Browsers are faster now. Some sites are slower but NoScript and uMatrix take care of most of those problems. They add others, such as fiddling with settings to enable as little of JS to make the sites work. Maybe I should account the time I spent doing that as part of the slowdown. Everything else I use is at least as fast as it used to be. Let's see what I have open right now on my screen: emacs, Thunderbird, VLC, KeePassXC, Slack, Telegram. Slack has never been fast but it's not slow either. LibreOffice is fast enough and it doesn't feel slower than what I remember it to be. And in the background: some docker containers (three PostgreSQLs, one redis,) a Rails app + Sidekiq, a Django app + Celery, one webpack for a Vue.js SPA. They are OK and this computer is a few times slower than what I could buy now. So, some software eat up all the hardware improvements of the last 10 years, some other software didn't or actually improved. Edit: of course I also have a browser open on my screen. Firefox with one window per virtual screen and many tabs per window. htop is saying 15.7/31.1GB.
- burnte 3y ago> Anecdotally this does not apply to my laptop from 2014. It doesn't apply to anyone device, this is a comparison of generation over generation changes. Your 2014 laptop is closer to a 2018 laptop than 2014 software is to 2018 software.
- Gigachad 3y agoYeah the only bit of software I’d think of as slow is Steam. Everything else is incredibly snappy. My iPhone is several years old now and it never misses a frame. My MacBook M1 is 3 years old and feels brand new still.
- anthk 3y agoUse Telega (Emacs) for Telegram, and try Notmuch with mbsync (isync) and msmtp. If you want I can tweak your ~/.emacs for that. On Slack, there's a libpurple plugin, and Bitlbee supports that. If you use Erc with Bitlbee, you could connect to any plugin Bitlbee uses (and the internal protocols too OFC).
- Apreche 3y agoSometimes software bloat is what it is. Poorly written and unoptimized. Other times, that performance loss was actually an intentional trade-off for accessibility, security, reliability, or other tangible benefits. I'm sure not everyone will agree, but in most cases I will personally prioritize those ahead of performance. A lot of the older simpler software we think of as being high performance was, or still is, severely lacking in those aspects.
- jahrichie 3y agoNiklaus Wirth died on 1/1/24 -- RIP!
- jjice 3y agoThis has proven true for a while now. My favorite example is Slack. Slack is solid software, but why do we need upwards of 300MB of memory usage to send text and a couple images. I know why, but it does seem like an unreasonable usage. Here's the thing: I'd be okay with my "primary" software to be resource intensive. In my case, that's my IDE and the surrounding tools supporting it. I don't want my supporting software (Slack, Spotify, etc) to be taking a ton of resource. But everyone thinks their software is worth the memory usage. That ends up leaving us with Spotify actively taking 300ish MB of RAM to play music I could play off of VLC instead. Who this really hurts are the users that's don't want to spend a lot on their machines. A lot of us devs have powerful and nice machines because it's a clear value win for us to do so, but then tons of users suffer because you're not even realizing you're writing insanely suboptimal code. The amount of times I've seen things that abuse network traffic to is insane. Everytime I see some SQL in a loop that should be a single query, a piece of me dies. This is probably just a natural thing we're experiencing with software development though, and I don't expect it to go away. The best we can do is to write better software and review our peer's code as well.
- stock_toaster 3y agoI think a lot of it is that Electron, as a technology, trades off cheaper developer expense (fewer devs needed to target more platforms) for much worse end user performance (slower, more ram).
- dijit 3y agoWell, certainly. Externalising the cost on users means the company doesn't have to pay it. Developers are expensive after all, and there's no material loss for slack (except negative sentiment like this) - ultimately: you still use (and pay) for the software, so why should they care?
- AlienRobot 3y agoI can't find the video anymore, but there was a team viewer video talking about a performance update on youtube, showing how it went from taking 20 seconds to start up to... 10 seconds.
- maximus-decimus 3y agoThis Casey tweet? https://twitter.com/cmuratori/status/1640827575437250561?lang=en https://twitter.com/cmuratori/status/1640827575437250561?lan... There was a lot of comment when this was posted here.
- AlienRobot 3y agoYes, this was it! ...dear God, what is wrong with this industry...
- jahrichie 3y agoNiklaus Wirth died on the 1/1/24, RIP!
- testless 3y agoMaybe this is why my Iphone seems to get slower every year.
- Literalyevery 3y agoSoftware also gets more features.
- steveBK123 3y agoI think its true, but also that we all use existing hardware kit longer than we did 5/10/15/20 years ago.
- calf 3y agoHardware is interesting now that Moore's Law (or Dennard scaling) has flatlined 10 years ago--are college courses now taught any differently because of this? It's a significant issue of computational resources in that we can't assume exponential transistor density anymore.
- MarkusWandel 3y agoHere's a little old fart story from more than 25 years ago. We'd been working on a hardware product and put a fair bit of effort into optimizing something that had to be done 1M times at startup, getting it down to a few seconds, in theory. Software comes to complain that it's grossly inefficient and takes forever. Investigate. Well. They're running a 1M iteration loop and then calling down through something like a dozen layers of object oriented subroutines, constructors and destructors and all, to execute the hardware primitive, one at a time. So I crack the PowerPC (this is ancient history, remember) manual and write a bit of assembly language. See here, I can get it done in 2.5 seconds! That's ridiculous! We can't block for 2.5 seconds in a subroutine call. Well how long can you? Oh. Well, then call it 100 times and do 10K iterations each time. So they did that, and problem solved. That's because we still had full-stack expertise. Everything was in house. These days, complexity is so vast that you simply can't afford to own the full stack any more. And so gross inefficiencies like the above creep in and there's simply nobody around to understand, much less fix them. The same thing is briefly alluded to in my brother's video about the early days at Research in Motion (https://youtu.be/GLxjXP-XCJA https://youtu.be/GLxjXP-XCJA). Talk about full stack. He spent a huge amount of time just working out how to extract every last millijoule out of an alkaline AA cell. And stopping software developers from introducing inefficiencies like the above. Full stack! And the RIM 950 really was an awesome gadget, running, if I recall correctly, for two weeks on that measly AA battery. Simply not possible if you're just bolting together re-usable pieces from different sources.
- ryandvm 3y ago"What Intel giveth, Microsoft taketh away"
- foxandmouse 3y agoYes but bandwidth is getting faster more rapidly than software is becoming slower.
- arcticbunny 3y agoWill AI tools help this or make it worse?
- burjui 3y agoI assume we are talking about LLMs. Optimistically, it could help, given an appropriate, carefully crafted prompt. Realistically, most devs are lazy asses and as soon as AI gives them working code, they would move on to pumping out the next piece of crap that works. If we consider smarter AIs, that can actually understand code and logic, it could be much better. But here we should be more concerned about alignment of such AIs.
- Joeboy 3y agoPydantic 2.x is much faster than Pydantic 1.x. Polars is a much faster replacement for Pandas. Tauri seems to be getting some traction as a much more lightweight replacement for Electron. Python's got significantly faster in recent releases, and is planning to (optionally) drop the GIL which will improve things further. From where I sit this doesn't right now seem particularly true. Developers are focusing on efficiency, not bloat. On the other hand my first computer ran at 3.5MHz so I can't deny the historical truth of it.
- sandoze 3y agoWhy am I doing all these interviews that grill me on big O(n) if they’re not even using it?!
- Tommah 3y agoIt is important to understand asymptotic complexity, but the places where it's useful in the real world are very different from textbook examples or Leetcode problems. You'll rarely have a triple loop in your code that makes you think, hmm, maybe I can reduce this to a double loop. That can happen, but these are more frequent problems I've seen: * Application code is issuing too many queries to the database. The classic N+1 problem is of this type. Another common problem is issuing one query for each item in a set, when an aggregate query could be issued instead. For example, suppose we have a database that contains students and exams, and every time a student takes an exam, a row is added to the table student_exam with the student id and the exam id. Now suppose that we want to build a dashboard that lists each exam and the number of students that took each exam. We could do this by iterating through the exam ids and querying SELECT COUNT(*) FROM student_exam WHERE exam_id = ? where we fill in the exam id as a parameter. But it will be faster to query SELECT exam_id, COUNT(*) FROM student_exam GROUP BY exam_id since this calculates the result in a single query. * Missing database indexes. A lot has been written about this, and it can cause a slowdown of N or N^2 times in some cases. Adding an index in the right place can change a linear scan into a much faster B-tree search. * Too much overhead. If your request handler is performing a small number of operations, but they include slow operations like making API calls over the network, then your handler will be slow, and network problems could make it even slower. If you’re writing Java code that has to make calls ten levels deep to get anything done, those levels of indirection aren’t free. * Using the wrong data structures, or using them suboptimally. If you want to determine whether two lists have an element in common, you could loop through both lists, but this will take O(mn) time. The faster way is to build a search structure out of one of the lists, then go through the other list and look for its elements in the search structure. For example, if your lists are A and B, you can build an AVL tree out of list A, call this tree T, then look for each element of B in T. This will run in O((m+n) log n) time. Using a hashtable works here too. Another common cause for slowdown is constructing a string by adding to its end repeatedly. This usually causes quadratic running time; it is better to build a list of strings and then concatenate them at the end. In the abstract, these cases are the same as having a double loop in your code; the difference is that the double loop isn’t in your code, it’s in library code or in the database’s code. So you should avoid writing code that is slow like this, but you should also avoid calling code in a way that will cause slowdowns. My third point is a little different from the rest; it’s not really talking about slowdowns by a factor of n, but by a large constant factor. When we’re talking about theory, we normally ignore the constant factors… but in the real world, those constants can matter a lot. This is why things like bitsets and B-trees are used. They only provide a constant factor improvement over regular sets and binary search trees respectively, but that constant factor sometimes matters a lot.
- emchammer 3y agoMy Nokia 2780 4G flip phone running KaiOS takes 8-9 seconds from pressing the send key to visibly sorting the recent calls list. My ex said that it was probably programmed in Java. Everything else is slow, including dialing digits from the home screen, and I always end up misdialing or something. My 2G Nokia 5160 and 8890 had instantaneous UIs 20-25 years ago, and those had ARM7TDMI CPUs. What if I need to call 911?
- eimrine 3y agoThis phone loves to hallucinate its input, its not the issue of productivity. KaiOs is a bad example of bloatware because this is an OS for low-end hardware.
- Phiwise_ 3y ago"Andy giveth, but Bill taketh away" (1998 and earlier): https://youtu.be/BUud1gcbS9k?t=3114 https://youtu.be/BUud1gcbS9k?t=3114
- rini17 3y agoReminded me how in game design, why the negative effects should be never gradual but use a threshold or hard limit. Because otherwise the players are prone to like, have a game character walking slowly, burdened by too much gear they are reluctant to drop, making whole experience miserable. The software development is similarly pulling itself into such misery.
- lucas_membrane 3y agoA major cause of the problem is that when a user sits at a computer or terminal or even a cellphone to do a certain task, software (and hardware) from a large number of producers is often involved between between entry and the awaited response, and so there is no way for any single software (or hardware) producer to possibly improve their particular product(s) so as to produce a time saving to the user amounting to a significant percentage of the total time. Thus, any significant incentive for the producer to do a little better is well hidden. Not to mention that if you speed up the toll booths, you may get so many vehicles bumper-to-bumper on the bridge that it collapses.
- dietr1ch 3y agoWhen developing there's tension between multiple things, and the first that's let go is performance because velocity is pushed too hard, particularly by management since their goals are rarely performance (unless the project is truly performance-critical (still second to correctness unless it's NoSQL stuff). Even if people say they value performance it's always below velocity since they assume that it can be simply fixed later, and only if it's a big issue. To make things worse, hardware keeps getting better anyway, even if it's at a slower pace.
- up2isomorphism 3y agoBecause being fast is no longer the main reason you make money from software, the platform makes money. I recently wrote a slowest piece of software I have ever written since I found a job and it is making 1M per day for the company since it owns the damn platform.
- HumblyTossed 3y agoBecause for the past decade all we've heard about is "developer productivity". The end user has no place in today's development.
- rkagerer 3y agoReading the commentary here justifying shitty code (because "economics") is depressing and makes me want to go work in rocketry or something where quality still counts. I firmly believe everyone deserves good code. And over the long run if your product sucks it's a competitive opportunity for someone to make a better one and put you out of business.