Tobias Hunger <tobias.hun...@gmail.com> writes: [...]
>> on the same grounds, because systemd covers so much ground >> and does so many things (that *it should not* be doing) that any good >> engineer who wants to design an alternative will see a lot of insane >> features and immediately say "Nope, I'm not doing that, it's not the >> init system's job"; and systemd proponents will always answer "See? >> systemd is the only one that does that stuff, and all the competition >> is inferior". > > Go talk to other developers, find out what bothers them about the > non-systemd and systemd status quo and address those issues one by one. > Then blog about that solution and try to get developers to use it. Act on > their feedback when they provide it. > > I do not see that happening anywhere at this time. So far it is mostly > claiming everything used to be fine before systemd. It was not. Considering just the discussions on this list during the last couple of weeks, this is obviously a strawman. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
