[object Object]Mar 13
I’m hoping this doesn’t come off as an “I told you so” post, but a number of the people you dismissed as systemd haters were trying to warn you about the longstanding technical and structural issues that make something on the level of slop code in systemd an instant and catastrophic issue with no easy solution
Show threadsarah tonin Mar 13

@zzt honestly it doesn't even feel like a gotcha or "i told you so" moment, people got tricked into abandoning redundancy for their systems, and now are left to pick up the pieces with the guilt that they helped push something that ultimately ended in a disaster.

it's all just sad

Show threadbean
@SRAZKVT @zzt i do still kind of like systemd, and if there was a maintained fork i might try it again in the future. but slop is a pretty big red line and i'm excited to try the alternatives and see how wrong i was :3
Mar 13 at 4:10pmWeb
Show threadsarah tonin Mar 13

@uproot4269 @zzt i'll be extremely honest, the chance of a succesful systemd fork is close to 0. project forks only work when you have people who already at least somewhat know how the project works, preferably existing recurrant contributors (because if you did one contribution 5 years ago that fixes a typo somewhere, you don't know anything about the project's concrete structure) and maintainers, but if the maintainers themselves are pushing for things harming everyone else, they're not going to be on board.

also, the very architecture and design of systemd, aka, taking every component and putting them, tightly coupled, into a single mostly homogenic slab of code is exactly the reason why we got into this mess, a fork will not fix that