I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.
There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.


At least you didn’t need a 20MB executable and 700MB of RAM to perform simple tasks. Software is definitely getting worse in that respect
True, but at the time you would able to do only the simple tasks.
While it is true that software is becoming more bloated as the time pass I think that most of the people do not really remember what it was to use these software.
I consider this to be similar to industrialisation.
Like how people would make most stuff in house (eg: butter from milk) and now they order/buy premade because the milk is already treated and not suitable.
This needs a vast amount of industrial equipment to support, even something simple and the logistics allow a clean separation. This clean separation is missing in software where people end up consuming the industrial output but with the heavy machinery (RAM usage) still included
The browser is that clean separation: A unified set of capabilities offered to a server to run a reasonably low-latency GUI on while the data and actual application is on the server. You don’t have to administrate this forum. Someone else does that.
Another example is game streaming where the game runs on the server and your system only needs to be able to display the resulting rendered images fast enough. But you need really fast and stable internet connectivity for this. Wifi is too unreliable. And the network latency is killing this for fast-paced games.
There are good reasons for the mainframe and thin clients of the past going extinct. Running stuff locally comes with benefits.