3 ms·
> If a user doesn't know what .ssh/ or .bash_history are, and it can hurt them to accidentally delete or modify them, why show them by default? Because they ar
by codedokode 4y ago
> If a user doesn't know what .ssh/ or .bash_history are, and it can hurt them to accidentally delete or modify them, why show them by default?
Because they are there. To prevent accidental deletion you can show an icon with a skull and crossbones or name a directory "configuration files" so that it is obvious what's in there.
> if they do get them there is no safeguard to stop them destroying the system
If the folder are named or labeled as "operating system" then the user will probably understand that it is better not to mess with it.
> In what reality is someone developing software and building Docker containers who doesn't understand the concept of hidden files?
Hiding hidden files is annoying because you have to add -a to ls command, have to add an option in Bash to include then when matching against a star pattern and to configure Explorer so that it shows them. It would be easier without them.
- Iamreadingthehn 4y ago> To prevent accidental deletion you can show an icon with a skull and crossbones This will make users more likely to delete it thinking it's a virus. > If the folder are named or labeled as "operating system" then the user will probably understand that it is better not to mess with it. Big assumption that most people know what an operating system is.
- hrbf 4y ago> Hiding hidden files is annoying because you have to add -a to ls command Have you ever heard of aliases?
- codedokode 4y agoYou are suggesting a workaround instead of solving the original problem.
- hrbf 4y agoThe workaround is trivial and painless, whereas “solving the original problem” would require fundamental changes to decades-old systems conventions. I was responding to the “annoying” part, which is effectively solved using an alias.