4 ms·
"But systemd is not some monolith" It. Does. Not. Matter. Still to much code in one place. Not enough review and unrelated subproject bitrot at different rate
by ldng 4y ago
"But systemd is not some monolith"
It. Does. Not. Matter.
Still to much code in one place. Not enough review and unrelated subproject bitrot at different rate without visibility.
- lazyier 4y agoThat is like saying Apache project is subject to not enough review and unrelated subproject bitrot. https://projects.apache.org/projects.html https://projects.apache.org/projects.html or GNU https://directory.fsf.org/wiki/GNU https://directory.fsf.org/wiki/GNU Or FreeBSD or OpenBSD.... Having a single large overall project that manages a diverse number of individual software products is a common pattern and certainly something that isn't remotely unique to Systemd. There is no reason to denigrate systemd for that.
- ldng 4y agoYou're making an Apple to Orange comparison here. Your examples are not released to the outside world as a single product "take-it-or-leave-it" and painting it so is borderline bad faith.
- throwaway82652 4y agoPainting systemd in that way is also bad faith, because it's not a single product "take-it-or-leave-it" either. If you think it doesn't have enough review for your purposes then it's time for you to step up and start reviewing, either in systemd or in another project. Part of the reason why people seem to (falsely) think systemd is monolithic is because distros have been historically bad at packaging it and haven't split up the components, but that's been improving over time.