Comment by asdff
17 hours ago
I think the biggest thing isn't really whatever it is but the act of changing and forcing everyone to change into the new ui that is the disruptive part. It is a combination of window dressing changing but also sometimes functions breaking. It is ironic because software written for developers prides itself generally on maintaining compatibility with say depreciated flags, or if things will be depreciated plenty of notice ahead of time. But that only holds for cli software. GUI software and the OS that all goes out the window. Stuff breaks, workflows break, you have no recourse and in fact they might make it genuinely difficult to go back to an older version. Like this part of it is the shitty part. Never mind how it happens to look. It is the forcing effect.
I think it’s also because these UI changes are always designed to improve first-impression and first-usage. They are outright hostile to anyone who wants to go fast and get faster — the power user. At minimum the re-arrangement resets any gains you had, and at maximum its irrecoverable because the UI is now fundamentally designed to slow you down.
This eventually becomes awkwardly precise complaints about information density and general change; but the underlying issue is I want to go fast and the system says no
I think the only real solution to this is to switch to an OS with a backing org that has optimization for power users as a first-class goal. I've been liking Omarchy and NixOS for that. I say this as a Mac user since 1989.