this post was submitted on 07 Dec 2023
1480 points (91.8% liked)
linuxmemes
21453 readers
880 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Jose1234, SHUT THE FUCK UP!
Fix your fucking comment and don't ever blame OP.
Whoa WhoaWhoa, SHUT THE FUCK UP!
It's a mistake alright - by the boss. How long have you been an employee? And you still haven't learned the first rule of employment?
We never EVER blame the employee. How hard can this be to understand?
So Linus should have sided with someone who in regression report of KDE using 100% CPU starts blaming pulseaudio and opensuse and double down on blaming pulseaudio? Instead of fixing syscall returning completely unrelated error code. It's like if your router crashed with message "there is no milk in your fridge".
uis, SHUT THE FUCK UP!
There's a difference between disagreeing with someone and insulting and attacking someone, and if you can't tell that there's a difference you can go fuck yourself with a cactus, you cumdrowned dicksphincter.
if only this were true.
fingers will always be pointed at us developers even as management takes full credits for the success every other time. :(