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.
Well, it is not one bin.
There is no monolithic systemd bin that does everything.
There are a lot of separate bin files for all the different tasks.
Well and if you don’t want to use timers, then don’t and just use cron instead.
If you don’t want to use journald, then just don’t and use rsyslog or whatever you want.
Don’t need systemd-homed? Well, then don’t use it.
You want to configure your network with something else then systemd-networkd? Great, do it if you want.
The Poettering Army will not come and force you to enable all the options 😜
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.
Well, it is not one bin. There is no monolithic systemd bin that does everything. There are a lot of separate bin files for all the different tasks. Well and if you don’t want to use timers, then don’t and just use cron instead. If you don’t want to use journald, then just don’t and use rsyslog or whatever you want. Don’t need systemd-homed? Well, then don’t use it. You want to configure your network with something else then systemd-networkd? Great, do it if you want.
The Poettering Army will not come and force you to enable all the options 😜
Except, they are. Pottering is the front man who does the dirty work for IBM and Microsoft to take over Linux by forcing distros to adopt systemd.
Those of us old enough to remember the “vote” that resulted in Debian going to Systemd remember it was almost at gunpoint.
Death to systemd, long live FOSS culture