zlacker

>>taubek+(OP)
Tangent, but that's what made getting into Linux/Unix really hard. You have all these folders and files and no README.md to explain what is what. And there seemed to be no logic at all with how things were organized or named (and names often were shortened to abbreviations that I couldn't comprehend). I'm wondering what a modern system made to be readable and understandable would look like.

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.

>>baby+rq
Well, you can look at MacOS for a basic inspiration. Hide all the ugly Unix parts and expose sensible directories like Applications, Preferences, Volumes, Users.

>>skoczn+fc1
This. Although I wish Apple would follow MS's suite and remove "spaces" in directories. Right now we have something like

    /Users/behnam/Library/Application Support

which is _nasty_ when working in a terminal.

MS tried to fix this by making directories like:

    C:/Users/AppData/Local/

>>behnam+wR1
The irony is, Microsoft originally put a space in "Program Files" intentionally, to force software developers to support paths with spaces in.

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.

>>LeoPan+o32
> 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.