[koyote]

The scrolling behaviour also exists in Windows and in Linux.

I believe (if I understand what you mean correctly) that the file system behaviour is also a Linux thing. Deleting a file that is open is completely fine in Linux.

I think UX between the three OSs is almost completely a matter of habit and familiarity these days. I for one can't see how anyone can be productive with the (what I believe is abysmal) window management on a Mac but millions of people like it so I'd probably get used to it if I wanted to.

[microtonal]

file system behaviour is also a Linux thing

It's required by POSIX, so all modern UNIX-like systems have this behavior:

When the file's link count becomes 0 and no process has the file open, the space occupied by the file shall be freed and the file shall no longer be accessible. If one or more processes have the file open when the last link is removed, the link shall be removed before unlink() returns, but the removal of the file contents shall be postponed until all references to the file are closed.

https://pubs.opengroup.org/onlinepubs/9699919799/functions/u...

[sixbrx]

> the file system behaviour is also a Linux thing

I think the interesting part is being missed here, the behavior is that the file is being identified to apps by a uniquie identifier which is not the path, so referrering apps still find it after it's been moved, even when they didn't have it open already. More like using the inode as the identifier maybe? This is a behavior that goes all the way back through the pre-OSX macs. It was part of some sort of philosophy for Macs though I forget its name.