Replies: 1 comment 3 replies
-
I think the aim should be that a new non-technical user should not need to use the file-manager at all to accomplish the things they are interested in, tbh. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First!!!
Intro:
So it seems that the idea of messing with the way that the user home directory looks isn't very popular.
However, since elementary's approach is UX first, you have to consider this from the perspective of someone who doesn't know, want to know or care what a 'leenooks' is.
Le problem:
A new user right now has an almost an entire OS that is uncharted territory to them. They will quite literally latch on to anything that feels familiar (a la people immediately searching where the minimise button is), which of course includes the file manager.
I don't particularly like file managers or the idea that 'modern computing' involves the digital equivalent of stacking shelves, but if it exists and is available to the user by default, so be it.
There are xserver config files stored in a user's home, so are their flatpak apps, runtimes, repos and cache.
Possible solutions:
Prevent deletion of critical stuff by default (muh dotfiles)
macOS does not have any of the crucial components of it's system on the same partition (or capsule, whatever the new apfs thing is), let alone in the user's directory.
Files could easily have a gsetting for whether to throw a messegedialogue telling them items meant for the OS are undeletable (for blacklisted files like .Xauthority and .local/share/flatpak/repo)
@cassidyjames I hope this place suits this kind of discussion better, you might want to pin things that gain tracktion for better visibility
Beta Was this translation helpful? Give feedback.
All reactions