There are situations where I don't exactly care how far something has progressed but I want to see that it at least has not hung. Fedora's dnf doing SELinux autorelabeling for two hours without any indication of progress is one of those things I hate with passion.
But we apparently chose to make things complicated in other ways.
The timer also jumps. Once I had ~40 minutes update that was hope-feeding me with "2 minutes left" for most of the time.
My guess is that it's not worth optimizing, but nowadays I shy from updates if I don't have 2h of time buffer (not because I am afraid something will break, but because I know I'll be locked out).
Funnily, Linux (KDE) got very good at their estimations for some time now. Better behaving storage also has a role, I presume.
A window is a program window not an actual window. A folder is not the same as a folder in a filing cabinet and a save icon is a save icon not a floppy disk.they dont have to stand for or emulate physical things
The Xerox demo was definitely trying to make near-as-possible 1-to-1 correspondences because their entire approach was "discovery is easier if the UI abstractions are couched in known physical abstractions." UIs that hewed very closely to the original Xerox demo did things like pop open one window per folder (because when you open a folder and there's a folder inside, you still have the original folder).
As time went on and users became more comfortable with computerized abstractions in general, much of that fluff fell by the wayside. MacOSX system 7, for instance, would open one window per double-click by default; modern desktop MacOS opens a folder into the current window, with the option to command-double-click it to open it into its own... tab? (Thanks browsers; you made users comfortable enough with tabbed windows that this is a metaphor the file system browser can adopt!).
I always found MacOS Finder's spatial file placement a good example (Non-MacOS users - Finder has this thing where it remembers windows locations and file locations in window, so one can arrange files as they please and they stick). Given that that feature is removed the UI stays the same (there are file icons, some windows, same layout), but it does remove some of the cognitive load.
UX is impacted by many non-UI things: load times, responsivity to input, reliability (hello dreaded printer dialogs that promise to print, but never will).
Anti-pattern I hate with passion is MacOS update bar. I want to do some work in the morning, I open my computer and it's friggin' updating. This sucks, but happens, we got forced into this. And then there's this progress bar that jumps: 20%, 80%, 50%, 30%, 90%. Colleague asks when I'm going to be online - "oh, 10% left, probably soon" - ding - progress bar backs to 30%.
UI is the same from observers point of view (it shows the progress, which I suppose is correct and takes into consideration multiple update phases) but UX is dropping ball here.