I am struck by the resemblance between this logic and the logic behind drinking. I remember back in my 20s one of the devs would come over at the end of the day and go, "Coming to the pub?" The standard answer was, of course, "I might come for one." The word "one" was a kind of punchline all on its own of course, a running joke.

That's part of the philosophical change that led to GNOME 2.0

https://ometer.com/preferences.html

This is good, but I think it's missing a discussion of the business logic, which is IMO the mechanism behind the gravity we're discussing here. And really it's just about the fact that you always get more positive attention in an org (and therefore a better shot at promotion etc.) for suggesting and implementing new stuff than pruning what's already there. Pruning only becomes possible when there's a coherent vision, for which you need a small-to-medium team (at most) and one person with the vision in charge of it.

This reminded me of a 20 year old 'viral' video "Microsoft Designs the iPod Package":

https://youtube.com/watch?v=EUXnJraKM3k

The minimalist approach is great until it isn't. You can cover 98% of use cases with a single button is a great motto, until you are in the other 2%. I often fail to find basic functionality in software today, because some smart product manager decided that nobody really needs it. For example, it is now often impossible to load all elements from a list and filter/sort it along basic properties.