What software did you use? I have to use Google Meet, Microsoft Teams, Anydesk, and an onscreen keyboard. When I checked a couple of months ago, Anydesk wouldn't even launch. I have been dabbling with Wayland ever since it was made available on Arch Linux, but invariably have to go back to X.org after just a few hours on Wayland.

For me, it still isn't quite there for some hardware combinations.

Does the kernel log not show anything? Or maybe the steam log?

I am sure that somewhere there's a hint of what's going on.

These protocol changes appear to count as changes in the fundamentals of Wayland, because the older versions were incomplete, since features that were considered essential by the author were impossible to implement with the then-existing Wayland protocols.

In general, I think that there is no doubt that Wayland has been very badly designed in the beginning, so its fundamental features have been bad, because for many applications it has become usable only after many years of additions and changes, which have resulted in a quite different Wayland than in the limited vision of its creators.

Wayland still has fundamental choices with which I do not agree, so it is unlikely that I will ever switch to Wayland. For instance, I do not want a GUI application to touch anything outside the client area of a window. I want everything outside that area, e.g. window frames, decorations, titles, buttons, menus, etc., to be drawn by the window manager, so that they will always have an identical appearance and behavior, regardless which application is run in that window and regardless what the application does.

Personally my #1 is just that stuff still don't work properly in a out-of-the-box Gnome+Wayland setup (on Arch). I still see weird things like a Firefox extension for making websites darker has a white line rendering through the pages when in use (probably something regarding aspect ratio?), some Electron apps like Obsidian sometimes have individual lines jittering up/down by 1-2 pixels (like it can't find the right/stable position), running nvidia-smi somehow introduces a 0.1 lag to seemingly my entire desktop, running it in a loop introduces that every run, and so on.

None of those issues happens with Xorg, and it just works without having set extra env vars for specific applications, or having to change the configuration just for Wayland to be used properly.

It seems to be less resource intensive, and smoother overall drawing, but all these issues make it kind of hard to start using daily over Xorg.

Of course it's portable. Your complaint that it hasn't been ported a lot of places may be well-placed, but it's a different complaint.

> I am hoping the *BSDs get together and keep Xorg maintained instead of having to port Linux crazyness into their systems.

"Foo is crazy and isn't ported – I therefore hope that people don't port crazy foo". What?

Its been ported to FreeBSD.

Would it be more true to say Wayland on *BSDs lags Wayland on Linux? Its not tied to Linux the way systemd is, right?

Last time I tested this, which was a few years ago, it worked just fine. But to be fair, this is not part of my workflow, just something I was testing out of curiosity.

If it doesn't do what you need for whatever reason, then I understand, but it just not true at all that the Wayland ecosystem has not been addressing these use cases.

Why?