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 😜
So, I don’t like the guy either, but for a little devil’s advocacy:
The stuff that already “just works” was developed during a very different era in terms of computing power, tasking of the computers which were running the systems, etc. Nobody (serious, and he is serious) develops something different because “why not?” they, at least from their perspective, feel that they are improving on the status quo, at least for the use cases they are considering.
one-size-fits-all mentality is
being decided by the distro maintainers, not the developers. Sure, developers promote their product, but if a distro thinks that multiple flavors are a better path, they distribute multiple flavors. It’s not like the systemd developers are filling billion dollar war chests with profit because they’re using strong-arm tactics to coerce distro maintainers to adopt their products.
stuff everything into one bin
When one bin serves the purpose, it’s a lot easier to maintain, modernize, security harden, etc. than ten bins.
the community and its users will notalways be able to freely develop FOSS.
Fork it and your loyal users will follow.
Gnome is a good example of something that creates too much of a dependency
Agreed, I was never happy with GNOME, and starting about 5 years back I have been migrating my systems, personal and professional, off of it. That’s the nature of FOSS, no contracts to negotiate, make the choices that make sense for your use cases and execute them.
FOSS shouldn’t work like that.
FOSS, by its very nature, should be expected to work all the ways. If a particular way can’t get enough developer traction, it stagnates but never really dies, not until the ecosystem it is dependent upon can no longer find hardware to run on and users willing to run it.
IBM/Red Hat finally decide to seal the deal and lock everyone out for good.
I am very glad that I walked away from CentOS about 8 years back, its proximity to Red Hat never made me happy. I have been trying to walk away from Canonical (toward Debian) for about 3 years now, but it still has some hooks that keep our professional team happier than Debian. If the unhappy ever outweighs the happy, we’ll execute the move.
Sorry if I can’t rejoice
Never asked you to. End of devil’s advocacy. I still don’t like the guy, but I never really interact with him. I do interact with his products and the alternatives, and in my use cases the products speak for themselves. There’s nothing about systemd that makes me dig around for systemd free alternatives - they are out there, but for my use cases I don’t care. YMMV.
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 😜
So, I don’t like the guy either, but for a little devil’s advocacy:
The stuff that already “just works” was developed during a very different era in terms of computing power, tasking of the computers which were running the systems, etc. Nobody (serious, and he is serious) develops something different because “why not?” they, at least from their perspective, feel that they are improving on the status quo, at least for the use cases they are considering.
being decided by the distro maintainers, not the developers. Sure, developers promote their product, but if a distro thinks that multiple flavors are a better path, they distribute multiple flavors. It’s not like the systemd developers are filling billion dollar war chests with profit because they’re using strong-arm tactics to coerce distro maintainers to adopt their products.
When one bin serves the purpose, it’s a lot easier to maintain, modernize, security harden, etc. than ten bins.
Fork it and your loyal users will follow.
Agreed, I was never happy with GNOME, and starting about 5 years back I have been migrating my systems, personal and professional, off of it. That’s the nature of FOSS, no contracts to negotiate, make the choices that make sense for your use cases and execute them.
FOSS, by its very nature, should be expected to work all the ways. If a particular way can’t get enough developer traction, it stagnates but never really dies, not until the ecosystem it is dependent upon can no longer find hardware to run on and users willing to run it.
I am very glad that I walked away from CentOS about 8 years back, its proximity to Red Hat never made me happy. I have been trying to walk away from Canonical (toward Debian) for about 3 years now, but it still has some hooks that keep our professional team happier than Debian. If the unhappy ever outweighs the happy, we’ll execute the move.
Never asked you to. End of devil’s advocacy. I still don’t like the guy, but I never really interact with him. I do interact with his products and the alternatives, and in my use cases the products speak for themselves. There’s nothing about systemd that makes me dig around for systemd free alternatives - they are out there, but for my use cases I don’t care. YMMV.