Technology

These aren't feature requirements. They're memory leaks that nobody bothered to fix.

Yet all those examples have been fixed 🤣. Most of them are from 3-5 years ago and were fixed not long after being reported.

Software development is hard - that’s why not everyone can do it. You can do everything perfectly in your development, testing, and deployment, and there will still be tonnes of people that get issues if enough people use your program because not everyone’s machines are the same, not everyone’s OS is the same, etc. If you’ve ever run one of those “debloat windows” type programs, for example, your OS is probably fucked beyond belief and any problem you encounter will be due to that.

Big programs are updated almost constantly - some daily even! As development gets more and more advanced with more and more features and more and more platforms, it doesn’t get easier. What matters is if the problems get fixed, and these days you basically wait 24 hours max for a fix.

I don't trust some of the numbers in this article.

Microsoft Teams: 100% CPU usage on 32GB machines

I'm literally sitting here right now on a Teams call (I've already contributed what I needed to), looking at my CPU usage, which is staying in the 4.6% to 7.3% CPU range.

Is that still too high? Probably. Have I seen it hit 100% CPU usage? Yes, rarely (but that's usually a sign of a deeper issue).

Maybe the author is going with worst case scenario. But in that case he should probably qualify the examples more.

Don’t give clicks to substack blogs. Fucking Nazi enablers.

That's been going on for a lot longer. We've replaced systems running on a single computer less powerfull than my phone but that could switch screens in the blink of an eye and update its information several times per second with the new systems running on several servers with all the latest gadgets, but taking ten seconds to switch screens and updates information every second at best. Yeah, those layers of abstraction start adding up over the years.

I've not read the article, but if you actually look at old code, it's pretty awful too. I've found bugs in the Bash codebase that are much older than me. If you try using Windows 95 or something, you will cry and weep. Linux used to be so much more painful 20 years ago too; anyone remember "plasma doesn't crash" proto-memes? So, "BEFORE QUALITY" thing is absolute bullshit.

What is happening today is that more and more people can do stuff with computers, so naturally you get "chaos", as in a lot of software that does things, perhaps not in the best way possible, but does them nonetheless. You will still have more professional developers doing their things and building great, high-quality software, faster and better than ever before because of all the new tooling and optimizations.

Yes, the average or median quality is perhaps going down, but this is a bit like complaining about the invention of printing press and how people are now printing out low quality barely edited books for cheap. Yeah, there's going to be a lot of that, but it produces a lot of awesome stuff too!