2 ms·

Totally, this is put better than I could have, but is exactly how I feel watching and experiencing the systemd thing play out. I'm old enough now that I (I'm su

Totally, this is put better than I could have, but is exactly how I feel watching and experiencing the systemd thing play out. I'm old enough now that I (I'm such a nerd) don't really want my init system messed around with, but I do get there may be better ways in general. In practice though, to me that would mean something that while looking pretty and being better automated would come with many fewer hidden parts and many fewer interactions between parts than sysvinit. That is, I'm looking for simplicity, composability, editability. The implied technical debt of one system to rule them all is a lot over 20 years, and you will inevitably have to get into line with a dominant system as a developer downstream from it. At any rate, happily this behaviour was publicised enough that I won't spend a day googling it when it happens to me. :)

AnonymousPlanet 10y ago
> Totally, this is put better than I could have, but is exactly how I feel watching and experiencing the systemd thing play out. I'm old enough now that I (I'm such a nerd) don't really want my init system messed around with, but I do get there may be better ways in general. Thanks. I'm kind of in the same boat, age wise. I have the impression (and this comes from a number of comments online and a podcast with Poettering I listened to lately) that any criticism from the experienced crowd is seen as a sort of elitism of people entrenched in their abilities they honed over many years. This might be the case for many critics, and Poettering may be right to dismiss them. But I'm afraid that the very valid criticism regarding overall design goals is lost in all of this. The systemd team steams on, believing that all naysayers are just stuck in their ways.