[cosmic_cheese]

YMMV and all, but my experience is that Wayland smoothness varies considerably depending on hardware. On modernish Intel and AMD iGPUs for example I’ve not had much trouble with Wayland whereas my tower with an Nvidia 3000 series card was considerably more troublesome with it.

[samiv]

As a user...why would I care?

If my Ferrari has an issue with the brakes and I go to my dealer I don't care if the brakes were by Brembo.

Blaming the vendor and their drivers is just trying to shift the blame.

[cosmic_cheese]

Generally true, though this particular case is due to a single company deciding to not play ball and generally act in a manner that's hostile to the FOSS world for self-serving reasons (Nvidia).

[samiv]

I don't even think it's even that. These bugs seem like bog standard bugs related to correct sharing of graphics resources between processes and accessing with correct mutual exclusion.Blaming NV is likely just a convenient excuse.

[bigyabai]

> my tower with an Nvidia 3000 series card was considerably more troublesome with it.

I think you're describing a driver error from before Nvidia really supported Wayland. My 3070 exhibited similar behavior but was fixed with the 555-series drivers.

The Vulkan drivers are still so/so in terms of performance, but the smoothness is now on-par with my Macbook and Intel GNOME machine.

[gf000]

My 3080 still has the occasional hiccup, but from what I've read it's from vsync colliding with Nvidia's gsync?