systemd
cat and GNU cat hugging a Linux cat.
GNU cat
You mean GNU
cat
?macOS. I find it to be the least inconvenient for most of my needs.
OS400 (IBM i)
systemd
is fine. The only people I’ve ever heard complain about it are lonely neckbeards pretending like their opinion somehow matters.I’ve used Debian as a server system since it was using
init.d
. And do you know what I found?systemd
is easier. And the fact that Debian of all distros decided to use it says a lot.PalmOS. So simplistic yet powerful. I miss those old PDAs :(
cat
propagandaVoid Linux, although I use NixOS nowadays.
🤔Windows 🤣
System service managers like systemd, OpenRC, runit, or SysVinit often come down to user preference. While these systems are crucial for initializing and managing services on servers, where uptime, resource allocation, and specific daemon behaviors are important, their impact on a typical desktop or laptop is generally minimal.
For most personal devices, the primary functions of a service manager occur largely out of sight. As long as the system boots reliably and applications run smoothly, the underlying service manager rarely registers as a significant factor in the daily user experience.
For many, including myself, systemd simply works without much fuss. My choice to stick with it isn’t due to strong conviction or deep technical analysis, but rather the simple fact that I’ve rarely, if ever, had to interact with it directly. For my personal desktop and laptop, it reliably handles booting, service management, and shutdown in the background. If it’s not broken and isn’t hindering my daily computing, there’s no compelling reason to explore alternatives.
System service managers like systemd, OpenRC, runit, or SysVinit often come down to user preference.
And coding best-practice. And a philosophy borne of bad luck and bad software that aims to resist monoculture.
But that lennart kid is cool for a Microsoft employee.
@furycd001 @nutbutter Technically, it’s broken. If you run screen/tmux built without systemd support, it will be killed on logout. Systemd requires every program that needs daemonize link libsystemd0 only to notify systemd to keep it running. So it’s broken, but worked-around in every software which need daemonize
So, running a program incompatible with a particular system leads to incompatibilities?
Wow, who’d have thought…
That sounds like a design decision (not saying it’s good or bad here), not something broken.
Alpine Linux would be my favourite, although I only use it as a server distro. I use Artix as my daily driver for personal computers because of the AUR and glibc (Alpine is musl). I also enjoy Void but it’s not got as much software as Artix repos + AUR.
I’ve used Alpine for desktop, it’s honestly pretty good, small footprint and has most major desktops and their goodies. If you’re desperate for something out of the norm you still have flatpak.
There are few system manager (single project or a mix of components) that use linux features efficiently and none have dev resource remotely comparable to systemd. That’s why in practice systemd is the best system layer implementation on gnu/linux. Android and chromeos userland (upstart derived) are not exactly (freedesktop) gnu/linux.
EDIT: the post ask which OS though. Including userland I like android a lot, but I would say illumos distros (OI currently). illumos has a system management similar to systemd (contracts in place of cgroups for example). Actually systemd was heavily inspired by SMF too.
MacOS. I use Linux for servers, Mac for daily driver. Windows for zilch, only at my job because I have to.
launchd is pretty similar to systemd.
Alpine. It’s very lightweight.
OPNSense.
Now that Windows qualifies under the prompt, not that I’d pick it but it’s just funny that it is.
I like FreeBSD, OpenBSD, Alpine, and Devuan.