systemd is like chicken tendies -- its always been there for me.
But I was then quite surprised a few years later when it was just the normal thing for me when people in Debian were basically fighting a war over it.
Seems to be quite serviceable on the happy path, and I quite like it for desktop linux honestly.
But I find it's usually a bit too opaque and "magic" for servers; even if it's causing less and less issues.
I liken the issue to the same one pulseaudio had: a software ecosystem that is poorly designed but foisted together into a perfectly serviceable product by incredible amounts of effort for all involved in its development and release to public.
I dislike its "let's just reinvent features that worked entirely fine" (like journalctl binary logs WITH NO FUCKING INDEXING, so they are slower than text files for usual operation somehow), but at its core competence it's extremely useful.
I feel the same way about systemd, its safe, reliable, and always a good choice for "dinner".
Basically I am saying that systemd has withstood the test of time and has never disappointed me.
> Basically I am saying that systemd has withstood the test of time and has never disappointed me.
IMO, when you make a reference specifically to chicken tenders, there is an implication of childishness - implying that systemd is a bit of a toy implementation. It doesn't sound like you mean that particular interpretation.
It would be the same if you mentioned red jello, milk boxes, capris suns, fruit snacks, or any other stereotypically children's food.