The other thing, coming from windows, was not understanding where to install things. In windows there's like a single place where you install all your stuff.
Side note, calling the file system layout "hier" has got to be the stupidest naming choice. Did they want this to be lost forever so that nobody ever finds it?
In the old days, I read books for that.
One wasn't intended to call man directly, instead calling apropos first, finding the appropriate page to open.
HISTORY
A hier manual page appeared in Version 7 AT&T UNIX.Markdown is a novelty. Back then, it would be just README (with no file extension at all).
> In windows there's like a single place where you install all your stuff.
Windows was even worse. Whenever you installed something, parts of it were in a new directory at the root of C:\, and parts of it were dumped in C:\WINDOWS\SYSTEM together with all the rest that's already there, often overwriting files of the same name (and the names were limited to 8 characters plus the extension, so they were quite opaque) used by other software you had installed earlier (that's the original scenario of what is now called "DLL hell"). On later Windows versions, instead of a new directory at the root of C:\ it was a new directory within "C:\Programs Files" (or is it "C:\PROGRA~1"? Or perhaps "C:\Arquivos de programas" aka "C:\ARQUIV~1"? Or something else?), and instead of C:\WINDOWS\SYSTEM it was now C:\Windows\system32, and there's also the "Common files" directory somewhere. And since there's no package manager (actually there is one, but not everything uses it, and it's very complex), you don't know which file came from which software. Oh, and if the program you installed overwrote a "protected" system file, the operating system overwrites the file again with its own copy.
Open a cmd box and type
PATH
But I completely agree with everything you said about Linux!
/Users/behnam/Library/Application Support
MS tried to fix this by making directories like:
C:/Users/AppData/Local/I don't know why developers have apparently collectively decided to go backwards. If your software doesn't support spaces there's a reasonable chance it doesn't support more exotic characters either, which really sucks if you are not natively English speaking.
The problem with space is that it's often a separator, which will not be the case for exotic characters. Fixing issues with exotic characters will not necessarily fix issues with spaces, and vice versa.