(I'm talking about Linux as as a complete operating system with core apps, not just the kernel alone)
- when virtual memory is running out, the kernel starts killing random processes one by one. The irony is that the process that caused the problem (Firefox with its perpetual memory leaks) has a good chance of living on while important services are getting axed one by one. And of course the kernel will make sure that user input processing is given least priority, so most of the running system will be butchered before you have a chance to intervene
- mount requires an existing folder as target. This is bullshit; it should just spawn the virtual folder where you want it, and perhaps fail by default if the folder already exists. No, seriously. Stop and think about it: is there any rationale for the current behavior, other than that it has always been like that?
- there is no such thing as "user's application settings folder". Instead there's a mess of dot-files or dot-dirs at the root of your home folder.
- there is no such thing as removing/uninstalling an app without a package manager. Every app is spread thinly over the entire file system