Re:Systemd Wants to Expand to Include a Sudo Replacement
by riddley on Tuesday April 30, 2024 @06:05PM
(#40216989)
Same thing is happening with Wayland. It reduces features adds complexity and solves no new problems but here it comes.
[ Parent
| on HN ]
Re:Systemd Wants to Expand to Include a Sudo Replacement
by roenxi on Tuesday April 30, 2024 @07:43PM
(#40217835)
Wayland was a mis-fire in terms of user friendliness for the first decade or so. But it is still a big step up from the mess that was a typical xserver back in 2010.
> It reduces features adds complexity...
The irony here is Wayland is part of a huge effort to decomplex an xserver into component parts. A really commendable initiative; the path forward while maintaining the X protocol probably was impractically hairy.
The Wayland protocol design had some glaring flaws, but saying that it adds complexity is unfair. It oversimplified; it would have benefited from some flexibility in providing a standard mechanism to let people inspect the buffers graphics buffers to be composited.
Re:Systemd Wants to Expand to Include a Sudo Replacement
by themerone on Tuesday April 30, 2024 @06:55PM
(#40217464)
How is Wayland more complex than X?
Re:Systemd Wants to Expand to Include a Sudo Replacement
by gmueckl on Tuesday April 30, 2024 @08:27PM
(#40218136)
The resulting wayland environments are more complex because wayland itself refuses to define/include features that desktop systems are expected to have. This results in a sprawling mess of competing and incompatible interfaces for those gaps that other parts of the implementations (desktop environments) now have to compensate for by including multiple implementations of the same thing based on all these different interfaces.
Re:Systemd Wants to Expand to Include a Sudo Replacement
by imtringued on Wednesday May 01, 2024 @05:35AM
(#40221194)
Stop using the wrong words. You're saying Wayland is too simple and feature incomplete.