One thing I find funny is the problem of data loss. On macOS, it's been the norm for years that applications retain their state when quit and re-opened, including unsaved documents.
While weird when introduced, in hindsight this is exactly the right behavior, because it is the most user-friendly and it makes e.g. software updates a non-issue. Even apps like iTerm can be updated and restarted in-place, retaining all the sessions.
It's a testament to how bad Linux UX still is that this sort of idea is not only utterly alien, but instead some developers thought it was acceptable to kill running apps outright.
> Even apps like iTerm can be updated and restarted in-place, retaining all the sessions.
iTerm doesn't retain sessions at all. It just presents a facade resembling preserved sessions. Close iTerm2 while you have a tmux session open, or some SSH connections, or any long-running command. Those sessions and their processes die when you close iTerm.
Maybe iTerm can approximate some of those things if iTerm is actually running the whole show, i.e., iTerm mediates launching your tmux sessions and your SSH connections. But imo those features are underwhelming and oversold.
And browsers, too, are only semi-reliable at restoring any sort of more complex page with significant dynamic contents, because that requires the cooperation of the website itself and in practice relying on that is a crapshoot.
While weird when introduced, in hindsight this is exactly the right behavior, because it is the most user-friendly and it makes e.g. software updates a non-issue. Even apps like iTerm can be updated and restarted in-place, retaining all the sessions.
It's a testament to how bad Linux UX still is that this sort of idea is not only utterly alien, but instead some developers thought it was acceptable to kill running apps outright.