- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Because of the ubiquity, nay, monopoly of systemd I always assumed it was miles ahead of other init systems. Nope. I’ve been using a non-systemd environment for a while and must say I’m surprised by how little breaks, i.e., next to nothing. Moreover, boot and shutdown times are faster, and more of that good stuff. I suggest trying it out.
Oh look, someone arguing that their lived experience is different to my lived experience, therefore mine is wrong.
🤡👞
WTF. Saying “it uses binlogs” as if that wasn’t a choice is just a lie. I called it out. Deal with it.
binlogs suck ass, you can’t convince me otherwise. Its slow and shite. Continue to suck.
Read. I’m saying that you lied, not that your preferences are bad.
Systemd doesn’t force you to use binlogs.
its the default, its the default everywhere, nobody is changing that configuration because systemd is a massive blob of nonsense.
Why is it the default?
Because most people prefer it. Again: having a minority taste doesn’t mean you’re oppressed when there’s an option to have what you want.
I don’t remember anyone -asking- for systemd, I just remember being subjected to it at the time it started getting popular.
If systemd is the solution, I want my problem back.
That’s because you very clearly had nothing to do with developing or maintaining Linux distros. You’re just a user with an ego problem. There are plenty of explanations that exist now and then to explain why systemd was desirable, and why it ended up in basically every major Linux distro, including Arch and Debian, both of which are not corporate, but community developed.
Well, its getting increasingly undesirable.
Also get fucked lol.
Yeah, these people never do their research. Its very easy to find the discussions and reasoning the devs had at the time.
That especially disqualifies the conspiracy idiots who come up with myths about Red Hat or Poettering or Microsoft or so puppeteering Linux into its dooooom