this post was submitted on 26 Apr 2024
467 points (93.0% liked)
linuxmemes
21622 readers
1465 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
sudoin 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
Once worked for a software company where we could run Linux on our machines if we maintained them ourselves and wouldn't ask admins for support since they were only supporting the default windows installations. Right before Christmas new coworker joined, early twenties, got into a project that was apparently hard to get it set up locally, we told him get the project running and then spend time to configure your laptop the way you like it to be. Low and behold, he spends Christmas setting up and configuring some fancy desktop environment on Kubuntu, returns to work, shows off the fancy looks and within a week fails to get the project set up and everyone else in the project was using windows. So one week later he was back using windows and super pissed that he wasted like 5 days configuring his desktop. My heart is still bleeding for that poor guy :(
That’s why I’m sticking to Windows at work even though I hate it. I couldn’t stand the glares of the others when I fail to fix even a noob distro.
A lot of people did this at that company as well. But mainly my point was that it might be better to first get productive, or verify you can be productive with the OS you installed before you waste tons of hours configuring it in some obscure ways.
Especially since it was usually the ones straight outta university who did the fancy configuration, tons of alias, custom theming and so on stuff while most senior Devs using Linux just used default Ubuntu, Fedora or whatever installations. Something that just worked.