i find it ironic when people who finally realised systemd is flawed because it puts everything in a single bunched up place are now pushing for projects to use a "modern" development workflow, which is done by moving the project's code to a platform which serves as contribution tracker, bug tracker, code reviews, automated testing, wiki, release platform, and feature planner, and probably even more i don't know about.
like. im no genius but that's going the same direction
and no, something like forgefed isn't a solution to this
adding a component has never decreased complexity and never will
@stilic @SRAZKVT yeah, but either of these basically implement either the same or a subset of #SystemD or #SysVinit.
sarah tonin 
Kevin Karhan 
init by just running whatever script is under /etc/init…But that's because essentially doing either manual (SysVinit) or hierachical-automated (SystemD) dependency resolution is the only way to make it any #Linux or #Unix'esque system work…
@[email protected] @[email protected] There isn't just SysVinit and systemd in this world Now we have OpenRC, dinit, runit, s6, finit...
@stilic @SRAZKVT and no, I'm not "suspended" cuz that would've meant that I could neither follow or be followed from said instance.
But you do you, feel free to fight imaginary enemies so you are too preoccupied to tackle the real ones (or maybe that's just too hard/easy for you? IDK, there's a shitton of issues more important…)
@[email protected] oh that guy responded ? he's suspended on tech.lgbt so i didn't see lmao but while i use runit right now, i wouldn't recommend it, and would instead recommend something like openrc or s6 (the devs of both are really really nice people and that's something we need in these trying times)