125
systemd(ont)
(www.arscyni.cc)
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.
Use what works for you.
Develop what scratches your itch.
Don't tell OSS devs who are volunteering unpaid labor what they should do for you.
If you want a solution that's non-systemd go for it. If it doesn't exist make it or pay someone to do so. Write from scratch or fork a project and get to work. That's the way of the Bazaar.
I'll be in my unenlightened "things work for me good enough" Linux world using what works. Systemd is fine and rarely gives me problems. Actually, I'm not even sure I can remember any.
Huge thank you's to the devs who make this all possible. You rock!
Systemd is developed primarily by paid developers.
I think that is a good thing, isn't it?
Of course it is, I was just addressing the part about "unpaid volunteers". I think it's fair game to criticize a corporation throwing their weight around to push their tools on the ecosystem.
Its built antithetically to the unix principles, it uses binlogs, its slow and its a big ol' bloated mess on low-memory embedded devices, and seemingly is creeping into the whole system.
Also the original author has since fucked off to microslop so I don't care what he thinks or does.
It, as a project, also bent the fucking knee.
Oh hey it's the same nonsense people have been saying for a decade now.
First of all, Linux is not Unix, and Unix principles were developed in like the fuckin 80s when what a computer is and does was different from what it is and does today. I'm betting you also use other software that doesn't follow the 'Unix' philosophy all the damn time, like, I dunno, the browser you used to post this nonsense. It was a guiding principle, not meant to be a dogmatic religious ideology. Also it not being the best choice for low memory embedded devices doesn't mean anything. It was designed for the desktop. These are very different platforms with very different needs. That's like complaining that the wheels on my car don't let it fly.
Also, bent the knee to who?
Really? Okay, so curl. You use it everyday. How's that using 'unix' principles?
You're just parroting the same old tired arguments.
Curl does exactly one thing and it does it very well.
Systemd aspires to do all the things and does nothing very well.
careful! advocating against systemd in this community will get you branded for heresy. lol
That old load of bullshit again. You could swap out the logs if you want a shittier, less searchable (but text based) logging system. The rest can be countered in a similarly conclusive way, and has been repeatedly in the last decade or so.
Inform yourself before copy-pasting misinformation and misleading propaganda.
I don't know how you reach this conclusion, the format has been standardized for decades.
Can you add more fields? Is there no ambiguity in context switching? No breakage around whitespace?
If so, sure, that's fine then.
They both get ingested into Splunk (or whatever tool is used by the company) in any context where this would be a problem. It's one of those things that in practice has never been a problem in my experience.
By the point/scale that context switching, log injection (forging) whitespace is a concern, I'm not piping shell commands. It's over engineered.
Nah, the issue is accidental corruption, different parsers doing things differently, stuff like that. Happens often with “mostly text but actually some structured data also” formats, doesn't happen with formats that have well specified framing.
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.
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
Says who, lmao. Keep crying.
True, but many don't know other init systems might work for them because of the same wrong assumption I had.
Definitely. One big ecosystem with a multitude of developers working on a multitude of projects.