>>32921The thread also shows a perfect example of the tactics these projects use to reject unwanted code.
>This pull request is not for implementing non-specific age groups. Make your own.<We don't want age groups, because they would need to be manually updated.<Also that would mean like a gorillion groups about drinking and driving (ad absurdum).Mind you, they said "userdb shouldn't arbitrarily edit any sort of field" before this.
>SystemD is not load bearin' to Linux, nor was X, as shown by it's near complete replacement by WaylandWayland has XWayland and i'm still not using it, due to my window management setup. For systemd there is a lot more infrastructure and opiniated design:
Consider the binary logs that would need to be migrated. A systemd successor would require a .unit parser at least on the level of nosh's (
http://jdebp.uk./Softwares/nosh/) and extend it to serve as a generic migration tool or preliminary frontend. And most importantly of all, systemd continues to control the dbus project. I imagine debian and suse ripping out systemd would just make them double down on the all the world's redhat attitude, that is already painful for the BSDs to deal with.
I also occasionally use the archiso for testing and have been slowly seeing formerly seperate programs, like grub or wpa_supplicant, replaced with their systemd equivalents. If this really comes to past, most distros will probably rally around an "esystemd" fork or just copy gentoo's homework and regress to sysvinit/openrc. None of the current maintainers would want to replace systemd init with daemontools or runit (because doing service management with them is a hack honestly) and s6 or others with a modular, well-thought out design get barely any adoption even within the systemd-less community.