I’m starting to think Wayland is the systemd of desktop graphic environments. Might be amazing eventually, but pushed onto the community too soon by opinionated devs who have fallen victim to the second-system effect.
Mod me down, don’t care.
Edit: Woohoo, into the ground! Mod me down further, and I will become more powerful than you can possibly imagine :p
I don’t troll often, but when I do… it’s about Wayland and systemd. Nyah nyah.
Honestly if Wayland will work 100% on my next setup and apps appear as expected, I won’t give a damn what system I’m using.
:) I’ll try it again, promise. I just didn’t have a good experience around two years ago. I do hear it’s much better now.
I’ll confess I’ve avoided systemd to this day however. Devuan/Funtoo are fine, and I don’t miss any of the supposed improvements systemd brings. So I’ll probably be rocking Wayland/open-rc or Wayland/sysv-init until I drop dead.
I don’t think you can change foundational architectural things like that in a fork. A lot of systemd’s strengths also come from the integration of doing many things, e.g. process management and the sandboxing features together are certainly easier to read and write than having the process management call some sort of external sandboxing tool (potentially multiple nested ones) with a bazillion parameters all in the ExecStart line of the systemd unit.
Name one init system that boots as fast as systemd on a modern distro with many services. Then name a display server that’s actually easy to maintain and to develop client applications for
The current issues with Wayland are due to it being new, X11 fanboys not wanting to explore the idea of contributing to Wayland, and client applications that are poorly designed
X11 fanboys not wanting to explore the idea of contributing to Wayland,
People have tried that, those projects are all dead for 3-5 years now because Wayland’s design turned out to be so much more flawed than originally expected with its “Oh, you know all that stuff the X server used to do, you now have to do all of that yourself in your compositor even though you don’t care about any of it and there is no benefit from having multiple implementations” approach.
I’m starting to think Wayland is the systemd of desktop graphic environments. Might be amazing eventually, but pushed onto the community too soon by opinionated devs who have fallen victim to the second-system effect.
Mod me down, don’t care.
Edit: Woohoo, into the ground! Mod me down further, and I will become more powerful than you can possibly imagine :p
I don’t troll often, but when I do… it’s about Wayland and systemd. Nyah nyah.
Honestly if Wayland will work 100% on my next setup and apps appear as expected, I won’t give a damn what system I’m using.
I actually quite like Wayland. I have not had a problem. Except with the discord application cause they are too lazy to fix their screen recording bug
:) I’ll try it again, promise. I just didn’t have a good experience around two years ago. I do hear it’s much better now.
I’ll confess I’ve avoided systemd to this day however. Devuan/Funtoo are fine, and I don’t miss any of the supposed improvements systemd brings. So I’ll probably be rocking Wayland/open-rc or Wayland/sysv-init until I drop dead.
Systemd is great for process management. It’s fault is trying to do too much.
Is there a Systemd fork that is unix philosophy compliant?
I don’t think you can change foundational architectural things like that in a fork. A lot of systemd’s strengths also come from the integration of doing many things, e.g. process management and the sandboxing features together are certainly easier to read and write than having the process management call some sort of external sandboxing tool (potentially multiple nested ones) with a bazillion parameters all in the ExecStart line of the systemd unit.
Wayland is the complete oposite of that crap.
I like both Wayland and systemd
Name one init system that boots as fast as systemd on a modern distro with many services. Then name a display server that’s actually easy to maintain and to develop client applications for
The current issues with Wayland are due to it being new, X11 fanboys not wanting to explore the idea of contributing to Wayland, and client applications that are poorly designed
People have tried that, those projects are all dead for 3-5 years now because Wayland’s design turned out to be so much more flawed than originally expected with its “Oh, you know all that stuff the X server used to do, you now have to do all of that yourself in your compositor even though you don’t care about any of it and there is no benefit from having multiple implementations” approach.