• @[email protected]
    link
    fedilink
    English
    751 year ago

    Does too much for one tool (against unix philosophy) and has poor interop with other tools (binary logfiles).

    • @[email protected]
      link
      fedilink
      651 year ago

      That’s not really true. systemd is split up into many different, independent binaries, and each of those does one job and does it well.

    • @[email protected]
      link
      fedilink
      211 year ago

      That’s not really true. systemd is split up into many different, independent binaries, and each of those does one job and does it well.

    • @[email protected]
      link
      fedilink
      121 year ago

      Btw. The Linux kernel does more than one thing. But monolithic kernels are much better for small student projects that won’t be relevant anymore, when Gnu Hurd comes out

      • nickwitha_k (he/him)
        link
        fedilink
        21 year ago

        Monolithic kernels are also generally more performant, compared to micro-kernels, it turns out. A bit counter-intuitive at first but, makes sense when you think about it.

        Micro-kernels in general-purpose OSes suffer from a death of a thousand cuts due to context switching. Something that would be a single callback to the kernel in a monolith turns into a mess of calls bouncing between kernel and user space. When using something like an RTOS where hardware is not likely intended for general-purpose computing, this is not an issue but, when you start adding all of the complexity of user-installable applications that need storage, graphics, inputs, etc, the number of calls gets huge.

    • thelastknowngod
      link
      fedilink
      -131 year ago

      Does too much for one tool (against unix philosophy)

      This tired, old argument needs to die already.

      Do you use browser extensions? That breaks unix philosophy too.

      • Mike
        link
        fedilink
        81 year ago

        You just compared a browser extension and an init system that takes proc id 1. The unix philosophy is about what runs as processes at the system level.

        • thelastknowngod
          link
          fedilink
          -31 year ago

          The unix philosophy is about what runs as processes at the system level.

          I don’t know what you mean by “system level” (cat is userspace) but I don’t believe there is any clarification about what kind of applications should apply to the unix philosophy or not. It doesn’t say that applications “should do one thing and do it well only if it is a system process or terminal based program built for purely shell environments.”

          Also, if the argument was exclusively about OS processes, dbus should be in the firing line of everyone in the anti-systemd camp too. That never gets the same level of hate.

          The unix philosophy is old and, while nice to have, is insufficient to fully address the needs of the modern world. It’s not as simple today as it was in the 1960s and 70s and we need to embrace change to progress.

          • Mike
            link
            fedilink
            71 year ago

            I’m honestly not sure what you’re talking about here. The unix philosophy is something informal that applies to compiled utilities that run usually in a bin/ directory. The philosophy isn’t attempting to apply to all software that exists and certainly doesn’t intend to apply to browsers or browser extensions.

          • @[email protected]
            link
            fedilink
            51 year ago

            Dbus does only one thing: relays messages.

            as it was in the 1960s and 70s

            You will be surprised, but Turing machine was created during WW2, and we still say turing-complete today.

      • Mike
        link
        fedilink
        11 year ago

        You just compared a browser extension and an init system that takes proc id 1. The unix philosophy is about what runs as processes at the system level.