All of these sound good to me. The thoughts are in contradiction with some terms of the current IT developments and programming.

About the current state of the software:

• it is getting slower as demonstrated by the latency. A computer from 2015 is 2-5 times slower than an Apple 2e from 1986 just at reading a keystroke and displaying it on screen. https://danluu.com/input-lag/
• putting all-in-one software increase complexity, and maintenance costs. They become untrustworthy.
• they are more a liability than an asset

I take some quotes out of it.

Humanity didn't get good at building houses by building the same house a million times. We built lots of different houses and learned from each other's failures.

As a programmer, I've tried multiple times in the past decade to create services just for myself and a few friends. Each of them has fallen away after a year or two. And a big reason for that was the burden of keeping up with updates for all the tools they depend on.

My initial plan had been to create clones of apps for myself and take out lots of features. [...] I didn't expect to find myself wondering what a web browser for memory palaces might look like.

Solutions

• making forks instead of all-in-one software. It keeps them lighter.
• we can have a huge amount of softwares. It is ok. Prefer software with thousands rather than millions of users, that seldom requires updates, that spawns lots of forks, that is easy to modify, that you can modify.