‹ BackHN Continuity

Thread

Systemd is a suite of basic building blocks

37 points · 71 comments · Bluestein

  1. badatnames · · focus · HN ↗
    Where "basic" follows a highly nuanced alternate definition, where if you step out of line without realising it, you lose 3 days debugging a complex undocumented interaction between 4 enterprise crapware daemons only to find out the answer is "you're wrong and won't fix" buried in a 6 year old bug report, when all you did was plug in a USB mouse or try to set the default audio output device, or something else.

    Total and utter propaganda, it's underdeveloped steaming garbage

    1. ux266478 · · focus · HN ↗
      I think the problem is that it's overdeveloped rather than underdeveloped.
      1. 9dev · · focus · HN ↗
        The reason for seeing overcomplexity in systemd components is usually that you never considered the use cases of other people or proper server management - mostly because in the days of olde, everyone cobbled together their shell script Jenga towers in seclusion.
        1. kqgnkqgn · · focus · HN ↗
          If they don't have the problems that other people are having...maybe they don't need that complexity. Different use cases can use different solutions.

          An Army unit crossing rocky and muddy terrain might want tracked vehicles and tanks. I don't need that in a vehicle I drive 10 minutes to the office in the city.

          1. fragmede · · focus · HN ↗
            Analogies only go so far. Driving an actual tank with a cannon to the grocery store 10 minutes away is ludicrous, but my smartphone has gigabytes of both ram and storage and a CPU that runs at gigahertz frequency, but weighs about the same as a dumb phone that does far less. It's not the 1970's anymore. We can be inefficient and stop counting every single little bit where it doesn't count. Yes, where it counts, we still want to be efficient and mean and lean, like in transcoding, but for starting up services on a laptop with gobs of ram and CPU cycles to spare, the added expense of the tracked vehicle to the grocery store is what, an extra 100 milliseconds of loading data from nvme storage to RAM? Yeah, don't port kubernetes to a microcontroller. Focus on the interface you have with it and let the complexity just sit there, being harmless.
            1. zdragnar · · focus · HN ↗
              > Driving an actual tank with a cannon to the grocery store 10 minutes away is ludicrous

              And here's me thinking it would be a lot of fun...

              1. doubled112 · · focus · HN ↗
                I think it’d really help on the highway with traffic.

                I don’t need it all the time, but that doesn’t stop it from being useful.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.