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.
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.
Essentially, what could depend on shared standards and implementations in X11, can't do so in Wayland, and there are two major forks when it comes to protocol extensions, as well as major fork between GNOME and everyone else on topic of Server-Side decorations.
"We know better" could be their motto.
We've seen, again and again, that popularity has absolutely nothing to do with technical merit or even lack of overt user-hostility.
The IBus case is classic example - There was high-handed declaration that having one single global IME state is "easier" for users. The problem is when you regularly have to use languages that are incompatible in writing systems and input methods. Whether its one of the CJK or switching between one of the cyrillic variants and latin, life is much easier when you can have separate input state between let's say an Instant Messenger and your IDE.
For me, I recall the "canary in the coal mine" was when they refused (despite earlier promises and roadmaps) to re-implement certain things related to printing, again in a way that probably didn't bother the developers.
A similar case involves all the very deep integration with systemd, where they essentially declared that there's one Operating System under the Sun and its name is Fedora.
And it might feel more polished than Windows 10 on surface, yes. But then it's much less capable and the resources in Windows go towards things like not breaking people's software and behaviours.
Honestly, the current state of mainstream desktop environments -- open source or proprietary -- is pretty awful with the exception of perhaps KDE and little ones like XFCE and LXDE. It kind of makes me glad I didn't hop on the GNOME train in the late 90s -- I could see the awful coming even back then -- and just stuck with a bare WM.
It sounds like screen sharing is a known problem area? Does anyone know if they have fixed these issues in later versions of Zoom or Ubuntu?
That said, Pipewire is a working solution for Zoom today on Wayland. I'm not on Ubuntu, so I don't know if the Chromium package they ship has Pipewire enabled by default, but my guess is that they do.
I use a small extension to automatically default Zoom to opening calls in the browser (https://chrome.google.com/webstore/detail/zoom-redirector/fm...) and there I can share screens just fine (Full desktop, application window only, etc - For the most part, things work fine).
I'd give it another 12 months if you don't want to have to think about it at all, but I'll be honest, Arch/Gnome/Wayland is the happiest I've EVER been on desktop linux.
I see that there are a lot of complains about Wayland here on HN. About input, screenshots and other stuff. But I have not experienced any of that. Input works perfectly and I have no problem with screenshots or screencasts.
Maybe it's that I have well supported hardware (Thinkpad X1C7) or is it something that I'm missing?