Linux

I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn't make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.

Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.

Unrelated but how do people feel about the ai images when used for something like this.

The font is very telling for being DallE

It's refreshing to read to someone that actually says "I was so wrong"

I was wrong also with systemd, I hated it mainly because I already knew init.d, where files are, where configs where etc. Some years later hate is gone, I'm not a power user, but I just now know how to handle my things with systemd and all is good.

I'd say the main bad part of systemd is how it's used and now expected everywhere.

If you search for some Linux guides or install something complicated or whatnot, they always expect you to have systemd. Otherwise, you're on your own figuring how things work on your system.

This shouldn't really happen. Otherwise, yes, it's great, it integrates neatly, and is least pain to use.

I don't appreciate the attitude and arrogance of the guy behind systemd because he actually believes what he produces can replace everything that already "just works". He wants to push out systemd-homed because "why not". He wants to replace grub. He wants to replace a myriad of things that just flat out don't need to get replaced. autofs, cron, you name it! That kind of thinking and one-size-fits-all mentality is backwards and does not benefit the community in any way. All it does is stuff everything into one bin and so long as influencers like this guy continue to restrict what works or doesn't work according to their own work, the community and its users will not be able to freely develop FOSS. Gnome is a good example of something that creates too much of a dependency on systemd and so when you're trying to use something like Gentoo, it becomes very difficult to get that done and hacks have to made in order to get it working. FOSS shouldn't work like that. He'll keep stripping away legit projects from major distros until IBM/Red Hat finally decide to seal the deal and lock everyone out for good. Sorry if I can't rejoice in the woah whiplash.

I hated it and still do because for a period of years every weird, difficult to find issue on a bunch of servers was caused by systemd. It may be fine now, but I switched to Devuan and have had incredible stability. Poettering's response to security issues was also terrible and honestly the dude seems like a real piece of shit.

I still doesn't like it...

I've been using systemd on most of my systems since it was released; I was an early jumper to upstart as well.

The thing I don't like about systemd is how pervasive in the OS it is. It violates the "do one thing, do it well" Unix philosophy, and when systemd went from an init system to starting to take everything over, I started liking it less.

My issues with systemd is that it isn't an unmitigated success, for me. journald is horrible: it's slow and doesn't seem to catch everything (the latter is extremely rare, but that it happens occasionally makes me nervous). There are several gotchas in running user services, such as getting in-session services working correctly (so that user services can access the user session kernel keyring).

Recently I've been using dinit on a system, and I'm pretty happy with it. I may switch all of my systems over to it; I'm running Arch everywhere, and while migrating Arch to Artix was scary the first time, in the end it went fairly smoothly.

Fundamentally, systemd is a monolithic OS system. It make Linux into more of a Windows or MacOS, where a bunch of different systems are consolidated under a single piece of software. While it violates the Unix philosophy, it has been successful because monolithic systems tend to be easier to use: users really only have to learn two command-line tools, vs a dozen. Is it categorically better, just because the user interface is easier for new Linux users?

I'd just like to interject for a moment. What you're refering to as Linux, is in fact, GNU/systemd/Linux, or as I've recently taken to calling it, GNU plus systemd Linux.

I've never used any other init system since I'm relatively new to Linux (8 years of use). So, systemd is all I know. I don't mind it, but I have this one major issue with it. That "stop job for UID 1000......" Or whatever it says. It's hands down the most annoying thing I have ever experienced in Linux. Making me wait for 3 minutes sometimes is just insane. I know I can go in and make it wait for 5 seconds /etc/systemd/system.conf or whatever, but why? Also, another one usually pops up.

Other than that, I really like how I can make timers. I like how I can make scripts run on boot, logout or login. And I like how I can make an app a background service that can auto start if they ever crashed. Maybe all of this can be done with other init systems? I wouldn't know, but I like these in systemd

I use it because I'm frankly too dumb to use something else, but if that wasnt the case, i dont think id be speaking fondly of it.

I'm a ram usage fetishist, I absolutely disagree with the "unused ram is wasted ram" phrase that has caught on with people.

I see some of these distros running a graphical environment with only 90mb ram usage and i cream myself. All of them run something other than systemd, usually avoid GNU stuff, and...require you basically to be a developer to use them.

I already run a half broken, hacked together system due to my stubborness, I can't imagine how fucked I'd be if I tried one of these cool kid minimalist distros.

I'm over here still using OpenRC. Mostly because I want to. Some servers I run have systemd on them. systemd is generally nice. OpenRC has finally gained the ability to run user services, which is also very nice.

I totally agree.

I hate to admit I didn't want anything to do with systemd because it took me forever to get somewhat familiar with some other mainstream init systems.

Then, I didn't care for a while until I developed software that had to keep running using some sort of init system. The obvious choice was whatever the default I had (systemd) and I fell in love with the convenience of systemd (templates, timers, ..). I started shipping sample systemd with the things I provide & yes, you are on your own if you use something else.

I decided to finally lean into using systemd more while i've been using NixOS, since the OS already relies heavily on it anyway. Created targets for my window managers, starting all my programs with services instead of autostart scripts, etc. And it worked fine for the most part, except for some reason, in qtile the systray widget refuses to load the nm-applet when it's started through systemd. Waybar does not have this problem. I can't help notice that systemd is not just a little slower, which isn't the biggest deal in the world, but it also tends to hang more often when shutting down, which is a bit annoying and reminds me of windows lol. Before NixOS i used Void, and while i never really cared too much about what init system i'm running, i can't help but really appreciate runit for being so simple and fast. I'm thinking of moving back to Void but using the Nix package manager on top. I recently found a solution to the nix driver problem when using it on other distros, so now i should be able to combine the best of both worlds.