• hoppolito@mander.xyz
    link
    fedilink
    English
    arrow-up
    20
    ·
    14 days ago

    It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

    I think that’s exactly it for most people. The socket, mount, timer unit files; the path/socket activations; the After=, Wants=, Requires= dependency graph, and the overall architecture as a more unified ‘event’ manager are what feels really different than most everything else in the Linux world.

    That coupled with the ini-style VerboseConfigurationNamesForThatOneThing and the binary journals made me choose a non-systemd distro for personal use - where I can tinker around and it all feels nice and unix-y. On the other hand I am really thankful to have systemd in the server space and for professional work.

    • passepartout@feddit.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      14 days ago

      I’ve started doing podman quadlets recently, and the ini config style is ugly as hell compared to yaml (even lol) in docker compose. The benefits outweigh that though imho.

      • cecilkorik@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        ·
        14 days ago

        I agree that quadlets are pretty ugly but I’m not sure that’s the ini style’s fault. In general I find yaml incredibly frustrating to understand, but toml/ini style is pretty fluent to me. Maybe just a preference, IDK.