News for hackers. Stuff that matters.
Re:The X.Org Server Is Abandonware? by roenxi on Sunday October 25, 2020 @08:23AM (#24885762)
"Works for me" is a risky defence; if you are a slightly demanding Wayland user then it is fine, if you have unusually simple needs it isn't a useful contribution.

It isn't anything to do with the hardware, it is the design assumption that isolating application's input and output should be mandatory.

In hindsight; that was a design mistake. The correct design is probably something like isolation by default but optional (ie, allowing sharing). The current design means further protocols and de-facto standards are required to support, eg, streaming and screenshots. That is bad for an ecosystem that relies on low barriers to entry to get good software written.

Basically, there needed to be a security model but the developers skipped it because it seemed like it shouldn't be the compositor's job. And after a very painful couple of years, seems quite likely that it was the compositor's job.

Re:The X.Org Server Is Abandonware? by horsawlarway on Sunday October 25, 2020 @06:58PM (#24890845)
>In hindsight; that was a design mistake. The correct design is probably something like isolation by default but optional (ie, allowing sharing).

I'm not really convinced it was. Frankly, Wayland does a great job handling the tasks I want my display server to handle. I don't have to wade into config files every time I plug in a new HID, or a new monitor, and my touch pad is a joy to use.

I think how screen sharing works is actually very dependent on the system in question ( I want a different set of prompts on my desktop from my laptop from my server), and that leaving that complexity out of the display server was a rough, but correct, decision.

That said, I'm with you - I held off on Wayland for a long time because screen sharing and screen recording just weren't there. At least for me, Pipewire is now a working solution. I won't go back to X.