Not entirely sure your analysis passes muster. While it is true pigs like chrome and slack are the norm, computers still have many orders of magnitude more memory than 20 years ago and even if a large GUI app keeps state on disk most of it should be hot in some kind of cache whether an explicit cache or just the OS page cache.
There are other forces at work.
For instance on my primary workstation after a period of time from cold boot, pretty much everything is sitting comfortably in 32 GB of memory. A lot of time is more due to the
1) sheer volume of crap that has to be shuttled in memory, because memory accesses still aren’t free
2) there’s a surprising amount of repetitive CPU intensive tasks just to get a program started up on merely bookkeeping tasks like linking, conversion, parsing.
In addition to all the built in latencies already mentioned.
To prove this you can setup a system using a RAM disk and notice that responsiveness is often still subpar.
I strongly suspect there are issues related specifically in how not just the OS, but also various applications, handle input events.
Special example for me is Chrome, which has a huge singleton in the form of Browser Process that can make your experience a hell even if all other chrome processes are idling - simply because it's the central hub that handles among other things all of Input handling and UI.
This compounds with other latencies, where often I can start building patterns of "if a windows containing that kind of content is on, expect macOS WindowServer to start lagging insanely despite being under low load)
There are other forces at work.
For instance on my primary workstation after a period of time from cold boot, pretty much everything is sitting comfortably in 32 GB of memory. A lot of time is more due to the
1) sheer volume of crap that has to be shuttled in memory, because memory accesses still aren’t free 2) there’s a surprising amount of repetitive CPU intensive tasks just to get a program started up on merely bookkeeping tasks like linking, conversion, parsing.
In addition to all the built in latencies already mentioned.
To prove this you can setup a system using a RAM disk and notice that responsiveness is often still subpar.