fight Big Tearing, stop using X 
fight Big Tearing, stop using X 

@uecker @Vilian @XOrgFoundation anything good has had to break compatibility at one point, the kernel being an exception.
I know Wayland has rough edges, but I also think at the current state of X, developing newer features for Wayland is easier than X.
@uecker @Vilian @XOrgFoundation if X11 was so easy to extend, why didn't it get proper VRR and support for Multi-Monitor setups?
I am not arguing that Wayland is better than X11, I am rather arguing that Wayland is easier to maintain, featureful, extendable than X.
@uecker @Vilian @XOrgFoundation On paper yeah, but I've seen lots of people complain that VRR and multi monitors (especially concerning different refresh rates) don't work for them.
Anyways I think we are not going to get anything good out of this, let's agree to disagree.
@hikari @XOrgFoundation last time I checked Wayland wasn't happy with remote displays, which is a Big Deal if you have graphical utilities that need to be run on remote servers.
But that might have changed since I looked.
@smokku @XOrgFoundation Chrome? try to fiddle with some startup flags... Wayland support w/ GPU acceleration may not be active yet by default...
https://wiki.archlinux.org/title/Chromium#Native_Wayland_support
https://wiki.archlinux.org/title/Chromium#Force_GPU_acceleration
> lspci | grep VGA
09:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1)
Are you sure you are running direct Wayland, not XWayland?
β
β