this post was submitted on 26 Oct 2025
867 points (99.0% liked)
linuxmemes
27854 readers
337 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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
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
The things is you really can't be that good with windows.
Sure you can get good with registry and group policy and other stuff that is needlessly complicated to do relatively simple stuff. You can know your way around WMI and .net and powershell...
But at some point, the software actively hides the specifics of what is wrong. You can't crack open something to see why it's showing some ambigious hexadecimal code or a plain screen. You can't add tracing to step through their code to see what unexpected condition they hit that they didn't prepare to handle. On Linux you are likely to be able to plainly see a stack trace, download the source code, maybe trace it, modify the source code.
Windows is like welding the hood shut and wondering why mechanics have a hard time with the car.
As someone who works as a sysadmin/systems engineer in a Windows environment, I find your analogy is a bit extreme. Not denying the issue, it's a constant frustration and problem. It's just that I find you can get a lot farther than most people think.
So less "hood's welded shut" and more "Why the fuck are the headlights a single unit? I just need to fix the high beams! Why is the transmission welded shut? Who in the fuck wired the radio and power steering together? And why in the hell is none of this documented anywhere?" Maybe that's worse, tbh. You can get very deep, but most of it is horrors.
Yes indeed! There are a lot of tricks old Windows admins still hold onto to get stuff done and sometimes it's so damn frustrating (like resorting to BITS to move files at times).
Guess it's a matter of degree, that was the sort of stuff I was alluding to in the first part, that you have all this convoluted instrumentation that you can dig into, and as you say perhaps even more maddening because at some times it's needlessly over complicating something simple, and then at just the wrong time it tries to simplify something and ends up sealing off just the flexibility you might need.
I do both. At home I do what you're describing for Linux but at work I do sysadmin work.
The stuff that winds up mattering on the Windows side tends to be a lot more social and resource based than it is hyper technical and digging in the weeds. If vendor software sucks, you debug it by yelling at the vendor to stop sucking (in the nicest way you can muster). You'll need to document expected vs actual behavior but most of them will hop to and provide a fix fairly quickly. The rest is just making sure you have correct configurations and a proper environment set up (including security and such). Easier said than done of course.