4 ms·

I don't really like Systemd neither - but Wayland and Systemd are pretty much opposites of each other. Systemd does (too) many things, many of them badly. Wayla

I don't really like Systemd neither - but Wayland and Systemd are pretty much opposites of each other. Systemd does (too) many things, many of them badly. Wayland does well what it does, but it (still!) does too little. Wayland is adding features and is pretty close to doing "everything necessary". Systemd keeps accreting worse replacements for existing services.

josephcsible 5mo ago
They're similar in that they're both new things that are worse than what they're meant to replace.
- chlorion 5mo ago
  They are actually both much better than the things they replace, but a bunch of whiner babies can't stand the thought of anything changing and will claw and scream while being dragged into the future.
  - ahartmetz 5mo ago
    Systemd-resolvd is a bad DNS resolver and journalctl makes logging needlessly complicated and log files slow to read. Also, socket activation is basically xinetd and we got rid of it because it's a brittle hack, also slower than starting stuff as soon as possible if you actually need it.
    - l72 5mo ago
      I’ll agree with some parts of this as I have some big issues with parts of systemd. But writing service files with systemd is so much better and having a unified interface into logs is really really nice.
      - josephcsible 5mo ago
        Sure, there are a few things it's better at. I don't think it's entirely bad, just that the good things are way outweighed by the bad.
account42 5mo ago
Its similar in that Wayland assumes responsibility for all interactions between programs instead of providing unrestricted interfaces that can be used to implement accessibility, automation and whatever other tools people can think of. It's the systemD way or the highway and it's the wayland way or the highway. But yes the situation is also different in that there is one SystemD but many little incompatible wayland compositors.

josephcsible 5mo ago

They're similar in that they're both new things that are worse than what they're meant to replace.

chlorion 5mo ago
They are actually both much better than the things they replace, but a bunch of whiner babies can't stand the thought of anything changing and will claw and scream while being dragged into the future.
- ahartmetz 5mo ago
  Systemd-resolvd is a bad DNS resolver and journalctl makes logging needlessly complicated and log files slow to read. Also, socket activation is basically xinetd and we got rid of it because it's a brittle hack, also slower than starting stuff as soon as possible if you actually need it.
  - l72 5mo ago
    I’ll agree with some parts of this as I have some big issues with parts of systemd. But writing service files with systemd is so much better and having a unified interface into logs is really really nice.
    - josephcsible 5mo ago
      Sure, there are a few things it's better at. I don't think it's entirely bad, just that the good things are way outweighed by the bad.

account42 5mo ago

Its similar in that Wayland assumes responsibility for all interactions between programs instead of providing unrestricted interfaces that can be used to implement accessibility, automation and whatever other tools people can think of. It's the systemD way or the highway and it's the wayland way or the highway. But yes the situation is also different in that there is one SystemD but many little incompatible wayland compositors.