you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 day ago (13 children)

This is fine, however I don't understand hard dependency on systemd. I wonder what will Void devs do about this.

  • source
  • hideshow 13 child comments
  • [–] 6 points 1 day ago (5 children)

    The solution is to use something other than Gnome or KDE (Wayland itself doesn't depend on systemd). Which is probably a deal breaker for many users, but life isn't obligated to be fair.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 21 hours ago (2 children)

    It just makes niche nicher (by losing the two biggest DEs). As long as it's just DEs themselves, I'm fine with that decision. I use a lot of KDE apps, so to not waste all those KDE framework I build my system around them. However looking at the direction how things go, it feels like this won't stay with DEs only.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 12 hours ago (1 child)

    I don't really disagree. But my point was sort of that you have only two options, and neither of those are necessarily zero effort: (1) Use something without a hard dependence on systemd to help show that people want something different; or (2) Build your own alternative and attract people to it.

    Personally, I don't understand the appeal of a full "desktop environment", which is probably why I have no issue being systemd-free, but I understand other people are different.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 10 hours ago

    Well, my daily drive is Niri but I still keep Plasma around because sometimes some programs expect a full DE for some reason (usually proprietary), and since I already have big part of the KDE framework it's not really a bloat for me either. My guess is probably Wayland related because I didn't have these issues when I was on bspwm. I'm on WMs for more than a decade. So it's kind of backup for me.

    By the way, an alternative to systemd especially with a Unix way is a good project. However working on low-level stuff can be tiring and I understand that. This is probably one of the reasons why systemd got so popular. No one actually want to spare extra manpower on those and they solved many issues.

  • source
  • parent
  • [–] 8 points 1 day ago* (last edited 1 day ago) (2 children)

    If there was something that provided the same services and systemd most desktops probably would support it

    The tragedy of systemd

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 21 hours ago

    Agreed. I don't blame projects that don't want to deal with bunch of low-level stuff that systemd does for them. However hard dependency means lack of portability, and that takes from the freedom of choice.

    Good video by the way.

  • source
  • parent
  • [–] 2 points 17 hours ago (3 children)

    KDE Plasma works fine with elogind.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 12 hours ago* (1 child)

    Though, the systemd project could decide one day that logind requires the rest of systemd and make it more difficult to disentangle/extract elogind. They've said explicitly that nothing is stopping them from doing exactly that with udev, other than they just haven't yet.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 15 hours ago

    Yeah, it works fine with elogind. Currently as far as I know only a couple parts of KDE requires systemd, one is KDE Login Manager. Aside from GNOME, I talked about future more likely, because they can also take it further than couple parts.

  • source
  • parent