I use plasma, BTW

  • Abnorc@lemm.ee
    30·
    2 years ago

    While you blissfully ignore it, systemd is planning the downfall of humanity. Don’t fall for its lies.

  • Rooty@lemmy.world
    231·
    2 years ago

    I am not interested in being preached at unless you have a workable alternative and a good reason why should I switch over.

  • PeterPoopshit@lemmy.world
    17·
    2 years ago

    I just use systemctl because I know how to use it and know all the ins and outs of any bullshit I might encounter. No way I’m switching. I like not being stumped on issues I can’t fix for weeks.

  • ilovetamako@lemmy.dbzer0.com
    12·
    2 years ago

    As an OpenRC user, Systemd is fine. I prefer openRC but I have systemd on my server and all its LXC containers and I have had no issues with it.

      • MigratingtoLemmy@lemmy.world
        1·
        2 years ago

        Wtf, I didn’t know that Libreboot wasn’t fully libre any more. I agree with the FSF’s ideology here. The only reason to run Libreboot over Coreboot was 100% FOSS, and if that’s not the case, then there is no point to it anymore.

        Thanks for mentioning the other projects, I’ll take a look

      • ZephrC@lemm.ee
        1·
        2 years ago

        The point isn’t just pragmatism. The point is that you’re running closed source software either way. Even ideologically, running out of date closed source software because it’s built into the chip isn’t actually any better than running a current version of the same software from a drive. Maybe that distinction made sense in the 90s when mircocode updates weren’t a thing most people dealt with, although honestly even back then it was a little weird. Now it’s complete garbage. The FSF is an important organization, which makes it all the more important to call them out when they’re wasting time and money on stupid nonsense.

      • The Octonaut@mander.xyz
        11·
        2 years ago

        Yeah, I wish someone released software to my exact requirements out of spite. They can release it out of race hate if they like

  • Gunpachi@lemmings.world
    7·
    2 years ago

    I just use whatever that does the job. Sometimes I switch to systemd free distros just to know what it’s like (currently checking out dinit version of Artix)

    I think most of the discrimination arises from a way of thinking which puts minimalism, simplicity and speed as the first priority and starts a unhealthy obsession over it. Sometimes keeping things too minimal can require more work than doing the actual work. This can also be seen in people who rave about WMs vs DEs and Wayland vs X.

    Oh and I use XFCE btw. I feel like that’s the DE which gives me enough control over everything while not bombarding me with a truck ton of settings. I started using DEs again because I was spending all my time ricing away with window managers (and none of my rices were not even that good).

    • cley_faye@lemmy.world
      4·
      2 years ago

      I sure love journalctl -u taking five second to give me ten lines of logs. Which I have to use because older, more robust services got replaced by default and the replacements got tightly integrated into everything else making it a pain to switch back, AND these replacement exhibits all the flaws that were fixed in older solutions.

      Granted, this will only improve going forward, but why reinvent everything just to put systemd- in front of the name.

  • ebc@lemmy.ca
    6·
    2 years ago

    At the level I care about, which is “I want this daemon to start when I boot up the computer”, systemd is much better. I can write a ~5 line unit file that will do exactly that, and I’ll be done.

    With init, I needed to copy-paste a 50-line shell script that I don’t really understand except that a lot of it seemed to be concerned with pid files. Honestly, I fail to see how that’s better…

      • uranibaba@lemmy.world
        4·
        2 years ago

        The only arguments against I have seen so for is systemd does a lot more than just handing system startup (systemd-resolved is one such example) and files that was previously stored as text now require systemd’s own tool to read (journalctl?).

        So not the actual startup function, just everything else.

        • CanadaPlus@lemmy.sdf.org
          3·
          2 years ago

          Based on the video someone posted, it’s not very portable either.

          I feel that little part of my brain that wants to add yet another standard itching. Easily starting something at boot is good, but I don’t see why that has to come with loss of modularity.

          • jbk@discuss.tchncs.de
            1·
            2 years ago

            Afaik they don’t care about being portable to instead focus as much as possible on being fast and whatever

    • milicent_bystandr@lemm.ee
      3·
      2 years ago

      Heresy!

      Let me tell you for the next six hours why XMonad is the only way to go.

      … And if you want Wayland you can write it yourself

  • HuntressHimbo@lemm.ee
    31·
    2 years ago

    I see way more posts that are pro-systemd than anti these days, so I think you might be tilting at windmills a bit.

    I would love to think about systemd less, but I’ve worked with it professionally since a year or so before Debian switched while I was an intern working in embedded. I got to see the flame wars and shaped my opinion of systemd by wrestling with its growing pains. Writing your own service files and working with DBus was ass back then, and while it has gotten better, my patience with it has diminished. In the end the frustration was enough that after I ditched windows, systemd was the next to go.

    That would be the end of it, but other programs keep growing annoying systemd dependencies or their projects get swallowed up by the systemd ecosystem entirely. I was so excited at the start to work with the parallel execution and dependency management, but the number of times systemd broke something, swallowed up the output, and then corrupted its own journal and lost the logs really turned me against it.

    • frippa@lemmy.mlOP
      3·
      2 years ago

      I don’t know, I’m not a power-user so systemd is just a thing in the background, I don’t have much opinions over it.

      I think you might be tilting at windmills a bit.

      No systemd love or hate for me, as for the meme, I respect both opinions (I’m still learning btw) but don’t particularly like proselitjzers. Sharing an opinion and experiences (like you did) is fine and often informative, what I don’t like are people (expecially on lower-quality places like 4chan) spamming stuff like “systemd is the devil and killed my child” or “systemd weights more than the Linux kernel” I guess I need to make up my mind, haven’t interacted with the OS at a low enough level yet.

      • HuntressHimbo@lemm.ee
        11·
        2 years ago

        I understand what you mean. If you are on the fence and not super interested in init systems, you can pretty easily get by with systemd without thinking about it. Most desktop environments have tools to manage user services in easy GUI’s, and you can find guides for anything more advanced you want to accomplish with them usually.

        If you want to dive in though, systemd is a great init system to learn. Nowadays learning systemd is a lot less of a moving target, and it’s in use virtually everywhere so the knowledge is valuable. It’s also fairly well documented at this point, which is great for learning how it works.

        My personal advice if you want to go that path is to just open up some service files. There are lots of interesting examples in /lib/systemd/system Systemd service files are just plain text, and pretty straightforward to read. Its divided into nice sections, and naming is pretty straightforward (Or the systemd brainworms are really in deep). Look for names you recognize or programs you use. Especially ones you are familiar with on the command line. I don’t recommend changing them to start, especially in the system directory, just open a couple and you should quickly start seeing the connections between what they are trying to accomplish and whats in each file. Then if you see anything you don’t understand or peaks your curiousity check the documentation. Once you’re ready try writing one of your own for something in the usr service directory. No pressure though, its not necessarily essential knowledge