I don't agree with this one. When I name my script without extension (btw, .sh is fine, .bash is ugly) I want my script to look just like any other command: as a user I do not care what the language program is written in, I care about its output and what it does.
When I develop a script, I get the correct syntax highlight becuase of the shebang so the extension doesn't matter.
The rest of the post is great.
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? It's like training wheels on a bike.
>For example the folder might look empty but in fact it could contain thousands of hidden files. You want to delete it as it is empty but accidentally delete important system files.
If it is possible for a regular user to accidentally brick a system like this, it was doomed to begin with. If a user doesn't know what a dotfile is they shouldn't have administrative privileges, and if they do get them there is no safeguard to stop them destroying the system. It's not a dotfile issue.
>Imagine if you have a project and want to edit an .env file. But as dotfiles are hidden in Linux you don't see this file and cannot open it. It turns out that Windows Explorer which doesn't hide dotfiles is much better for developing projects with Docker!
In what reality is someone developing software and building Docker containers who doesn't understand the concept of hidden files? Seems awfully contrived.
You have permissions to prevent from accidental deletions.
Also this is called "крокозябры" (read: kro-ko-zya-bry, nonsense word, no translation) especially when reading a binary file in a text viewer.
I have seen stuff like "defendant had TOR installed - a popular program for criminals" in court filings. ...and judges and juries accept that as fact because they just don't understand the technology. For example, having a bookmark for "Hacker News" would absolutely show up in court. Crazy stuff meant to bias judges and juries that don't know tech.
The point is that the situation is 100x worse in tech where prosecutors, judges, and juries simply do not understand the evidence. ANYTHING can be painted as incriminating evidence.
I have seen saved credentials on automation jobs being used to incorrectly establish people's network activity. I have seen routine maintenance being used to establish obstruction charges just to intimidate possible witnesses... Like stuff you would not believe happens, happens.
It's even worse in civil suits, where opposing counsel will subpoena as much as possible (mountains of data) just to give you more work and fish for trade secrets or anything they can twist in court.
When I was junior, I proudly told my legal team "good news, I added space to keep our transaction records for 20 years!" and was aghast when they said they wanted files deleted THE DAY the legal requirement to hold it expired because it increased legal liability.
Now I totally get it. Today we only store the bare minimum - everything else is deleted immediately. ... and I have to re-explain this to junior employees each year to their disgust.
I was punished in school for having NetHack source code in my home dir. And it was not because it was a game but because it allegedly was a hacking tool.