Sadness 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.
Edit to add - I want to be clear that I’m not judging the developers of these projects. If they’re being overwhelmed with AI generated PRs, they’re being forced to use these tools in their “real jobs” and it spills over, or they just feel that this is the way things are going or whatever reason - they’ve got to do what they’ve got to do to survive. My sadness, dread and defeat comes from the state of the world and this is just the symptom that’s currently front of mind.
There 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.
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.
Sadness 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.
Edit to add - I want to be clear that I’m not judging the developers of these projects. If they’re being overwhelmed with AI generated PRs, they’re being forced to use these tools in their “real jobs” and it spills over, or they just feel that this is the way things are going or whatever reason - they’ve got to do what they’ve got to do to survive. My sadness, dread and defeat comes from the state of the world and this is just the symptom that’s currently front of mind.
There 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:
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.
Guess you missed the one that said the Linux Kernel. 🤣 😭
~Also,
wgetovercurl? 🤦♂️~