not_IOsystemd moment đźâđš
LenaDamn the repo also has AGENTS.MD and CLAUDE.md files, I really didnât think systemd is vibecoded
UndauntedIf you wish to increase your sadness and dread a little more, have a look at this list
Great Blue HeronSadness and dread is a perfect description. As I started reading I was building a mental list of things to stop using - I didnât get very far before I gave up. So many projects Iâve held up in high regard.
Sadness, dread and defeat.
rozodruThere are many viable and better alternatives than whatâs on that list. thereâs really nothing there that should make you think âohâŠI donât know what to use nowâ most of the stuff listed is garbage anyways. Like take Zen Browser for example. you can essentially do that yourself on just about any fork of firefox by simply editing the userChrome.css. Librewolf is another example of âdoing it yourselfâ on just about any fork or firefox or just firefox itself.
Really?
My list of ânot trivial to replaceâ is:
firefox - desktop and android ImageMagik - I donât use it directly, but other things I use depend on it VLC - yeah, I know there are other options but VLC has so much else going for it, itâs hard to change Jellyfin - whatâs the alternative? Kodi? Oh wait⊠curl rsync .NET - I donât use it directly, but things I use depend on it python vim - Iâve been using vi for 35 years, Iâm not changing now. But Iâm happy to use old versions. Joplin - argh, just finished migrating my documentation into here KeepassXC Mastodon Lemmy systemd Linux Kernel!!
systemd is kinda trivial to replace, just look at devuan
It might be trivial for you, but not for me. I like systemd - perhaps because I came to Linux from AIX? Anyway, because I like it, I use it on all 4 of my servers - I have custom systemd unit files for applications I run that donât natively support it, Iâve removed cron and use systemd timers for all my scheduling and I use systemdâs remote journal capability to centralise logs to my monitoring server.
if you are not used to it you will have to learn it⊠that goes both waysâŠ
and all the functionality you need were already in normal initfiles, cron and rsyslogd
my main issue with systemd always has been, that it centralises stuff that does not relate to each other into one single program instead of keeping it seperate and as simple as possible
I never said I canât do it - Iâve been running different varieties of unix for over 35 years. I said itâs not trivial.
And being a bit pedantic with your terminology - systemd does not âcentralises stuff that does not relate to each other into one single programâ. systemd, systemd-journald, systemd-networkd, systemd-resolved etc. etc. are all separate programs, provided by the systemd project, with their own configuration. You are free to pick and choose which parts of systemd you use and which you donât.
All that being said - I am a bit over complexity of modern mainstream distributions and am now considering moving to Apline for my servers.