[diggan]

> My # 1 issue with wayland is it is Linux Specific, not protable.

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.

[akimbostrawman]

I know this doesn't help but those seem like GNOME issues not Wayland protocol issues. Using Nvidia also probably doesn't improve the odds.

[diggan]

Yeah, you're probably right. I guess as I'm just an end-user who don't mind the internals that much, I'm just seeing how Xorg/Wayland work in the context of Gnome, so when I use Gnome+Xorg, everything works while using Gnome+Wayland leads to lots of stuff broken, so I associate the broken stuff with Wayland, although it could very well be the problem of how Gnome uses Wayland.

Although I'm not sure how Gnome affects how Firefox Extensions work, or how Electron applications render, I also don't know enough about the internals to say that's because of Gnome or Wayland.

[palata]

Agreed. I am using Sway; it just works (tm).

[Wheaties466]

its not even just arch linux. you can literally buy a PC from anyone who sells ubuntu 24.04 and you still cant properly install (and have them work out of the box) snap store items like shutter.