3 ms·

systemd is like chicken tendies -- its always been there for me.

by kris-nova 4y ago

zzzeek 4y ago
that line is in your article as well, can you explain what it means? I am missing the reference
- kris-nova 4y ago
  Its just a joke. Most folks from the U.S. who enjoy eating chicken tenders (breaded chicken breast with sauce) view it as a safe/comfort food that has never been a poor choice to eat. 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.
  - nordsieck 4y ago
    > 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. 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.
    - kris-nova 4y ago
      Good feedback. I went ahead and removed the reference and just called out my sentiment directly.
  - bee_rider 4y ago
    Ah, that's funny -- I took it to mean like... an OK in a pinch and generally unobjectionable, but not something to be excited about. Which is basically how I feel about systemd (as someone who doesn't do systems engineering or run a distro, so, probably I don't see where it becomes exciting)
panick21_ 4y ago
My first experience was with Arch Linux right when they switched to Systemd. I hated it, but I didn't really get what it was, not knowing what an init system or a process even is. 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.
- dijit 4y ago
  My first experience with systemd was similar, it was in Fedora 15 and it basically was such an incredible source of frustration. 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.
- xani_ 4y ago
  It allowed us to remove literally thousands of lines of code, including a bunch of rewritten init scripts, because apparently "simple" SysV scripts still have plenty of traps for the developers that start to rear their ugly heads when used with say Pacemaker. 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.

systemd is like chicken tendies -- its always been there for me.

zzzeek 4y ago

that line is in your article as well, can you explain what it means? I am missing the reference

kris-nova 4y ago
Its just a joke. Most folks from the U.S. who enjoy eating chicken tenders (breaded chicken breast with sauce) view it as a safe/comfort food that has never been a poor choice to eat. 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.
- nordsieck 4y ago
  > 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. 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.
  - kris-nova 4y ago
    Good feedback. I went ahead and removed the reference and just called out my sentiment directly.
- bee_rider 4y ago
  Ah, that's funny -- I took it to mean like... an OK in a pinch and generally unobjectionable, but not something to be excited about. Which is basically how I feel about systemd (as someone who doesn't do systems engineering or run a distro, so, probably I don't see where it becomes exciting)

panick21_ 4y ago

My first experience was with Arch Linux right when they switched to Systemd. I hated it, but I didn't really get what it was, not knowing what an init system or a process even is. 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.

dijit 4y ago
My first experience with systemd was similar, it was in Fedora 15 and it basically was such an incredible source of frustration. 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.
xani_ 4y ago
It allowed us to remove literally thousands of lines of code, including a bunch of rewritten init scripts, because apparently "simple" SysV scripts still have plenty of traps for the developers that start to rear their ugly heads when used with say Pacemaker. 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.