linuxmemes

Man, wait until these people hear about the filesystem and kernel.

It's also "infectious" software. The way systemd positions itself on the system, it can make it more difficult for software to be written in an agnostic way. This isn't all software, and is often more of a complaint by lower level software, like desktop environments.
https://catfox.life/2024/01/05/systemd-through-the-eyes-of-a-musl-distribution-maintainer/ This isn't a terrible summary of some of the aspects of it.

Another aspect is that when it was first developed, the lead on the project was exceptionally hostile to anyone who didn't immediately agree that systemd definitely should take over most of the system, often criticizing people who pointed out bugs or questionable design decisions as being afraid of change or relics of the past.
It's more of a social reason, but if people feel like the developer of a tool they're forced to use doesn't even respect their concerns, they're going to start rejecting the tool.

For me it’s 3 things

• Do one thing and do it well
• Everything is a file in Linux
• human readable logs

Systemd breaks all three of though by being monolithic and binary. It actually makes you have to jump through more hoops to do things in certain cases. I understand it’s a mindset shift but it really starts making it feel more like Windows with how it works and the registry and event log.

Your comment summarizes my entire programming career.

These steps:

1. Be taught that there's a specific way to do something because the other ways have major issues

2. Find something that goes against that specific way and hate it

3. After a lot of familiarity, end up understanding it

4. Have a mix emotion of both loving it because it functions so well and hating it because it doesn't align with the rules you've set up

Debian, Arch, Fedora, Mint, Ubuntu, Redhat, Manjaro all have docs and wiki on their primary websites. Slackware has docs, Gentoo has a wiki. Anything that's not on a distro's site needs to be carefully considered before tampering. Almost all of those distros have a warning in their installation instructions to only listen to the information in their docs and wiki, and to a lesser extent their forums. Hell, even nosystemd.org tells you what systemd is, what it's for, what replacements there are, and the proper way to get rid of it in bold text under the header "How do I get rid of systemd?"

Listening to hackneyed advice from unvetted sources just because they have strong opinions is a problem that any and every computer will face. That's not a problem with linux anymore than the hoardes of trolls on random social media sites telling you to "delete System32" is a problem with Windows.

I want Linux to be customizable AND safe. But safe in the way that someone takes the time to learn how what they plan to do will effect their system, not safe in the sense of "impossible to bork"

As for elitism: if it's "elitist" to indirectly poke fun of someone who deleted a core system component without understanding what it does without a backup, then so be it. It feels more like that word is levied by people whose ego is too big to take respobsibility for the mistakes they made, and instead blame others for laughing when it bites them in the ass.

Idk where these swaths of elitists that refuse to help are. OOP went to stackexchange and likely got a helpful answer complete with explanations, as that is the community standard. Over on [email protected] , I see people offering help with problems all the time without shitting on them. If I go to the aforementioned OS forums, or really any software-specific forums, I see people helping or pointing people to where they can get help.

And I'm not denying that assholes who say shit like "did you even bother googling?" exist. They're nasty people with no patience, but they're by no means the community standard unless they're the only ones you pay attention to...

Or unless you see a screenshot of a question from a different website posted in a meme-sharing forum and expect the comments to offer advice, instead of laughing at the person who shot themselves in the foot and went to a hospital instead of seeking help at the DNC HQ

He is less technically inclined

He read a prompt asking if he wanted to remove his system and said yes

Then complained about it

Putting pure diesel into a clearly labelled petrol V8 type situation

Nah, more like deleting explorer.exe.

There's isn't really a Windows equivalent for this, as Windows doesn't give you control on this level.

It'd be as if you could delete services.msc but also the runner behind it.

I don’t think you’ll get a cli if you delete system32.

I don't want to be in control of starting up all the services during boot.
I want the init system to do that.