I’m hoping this doesn’t come off as an “I told you so” post, but a number of the people you dismissed as systemd haters were trying to warn you about the longstanding technical and structural issues that make something on the level of slop code in systemd an instant and catastrophic issue with no easy solution

are some of the supposed systemd alternatives run by fascists? yes they are. a do-everything init ecosystem is an irresistible lever of power for them. init should be thin and independent enough that it isn’t an ecosystem at all, but if we must have an init ecosystem then we must be very careful who controls that power. again, ideally, there should be no power to control.

with that said, can we please stop fashjacketing all of the people who recognize systemd and wayland as levers of power?

@zzt where does wayland come into this at all ??? how is that a level of power ?? the point of wayland makes it even less centrally controlled than x11 was , witj pretty much only one working implementation . i agree with the sentiment of this posts but wayland has many competing implementations both toolkitwise and composotor(library) side , it does NOT suffer from this
@zzt not liking wayland and freedesktop is fair but like . lets not pretend your point wouldnt stand even stronger in an xorg controlled situation , please
@zzt wayland puts more power in the hands of developers
@zzt whicj is also a fair criticism of wayland : “i dont want to implement so much stuff just for what would be a simple window manager under x” is a fair argument !!
@fiore @zzt to be fair, that's not the protocol's fault per se. a compositor can decide to outsource the window management bits to a separate process. in fact, it already exists codeberg.org/river/river
river

A non-monolithic Wayland compositor

Codeberg.org
@kopper @zzt indeed , i love river ! the point is , there is more choice on “who has power” when it comes to wayland