this post was submitted on 12 Oct 2023
1218 points (94.5% liked)
linuxmemes
21599 readers
1010 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This seems like a pretty specific use case, but also pretty common. A system function to delete the file that called it should cover that entirely, but I guess psudo-malware is acceptable?
Pseudo-malware is pretty much the way to go as a developer in my experience.
I believe his suggestion of a javascript file that deletes itself works only works because javascript gets sandboxed and doesn't suffer from Windows "flaw" with file locks.
https://devblogs.microsoft.com/oldnewthing/20230911-00/?p=108749
While Raymond does offer a solution he's also completely side stepping any responsibility on Microsoft's part in creating and perpetuating this problem without offering their own native solution.
That last bit IMO is one reason to argue against him being the best software engineer. He might have the skills, but they are offset by his conflict of interest with MS.