When I tried installing Linux on there, I had a ton of trouble getting Wayland to work in any capacity (it was very glitchy when I tried), and I had to go back to X, before nuking the Linux install and going back to macOS.
Every recent time I would daily drive Linux (Ubuntu and Antix) I had screen tearing out of the box. Not really an acceptable feature.
3 year old Lenovo laptop with Intel Integrated plus Nvidia dedicated on Ubuntu connected to external HDMI and Displayport standard 1080p monitors and built in laptop monitor, and an old PC with old dedicated Nvidia on AntiX(Debian) connected to old 17" VGA LCD monitor. Nothing fancy. Screen tearing on all of them.
Anyway, the out of the box experience is shit on this front. Screen tearing shouldn't be a thing anymore. It's not like those GPUs were some exotic prototype HW nobody else has to need hours of reding forums and tinkering with .conf files to get rid fo screen tearing.
2) If I were using a batteries-included distro,
Section "Device"
Identifier "AMD"
Driver "amdgpu"
Option "TearFree" "on"
Option "VariableRefresh" "on"
EndSection
> Option "TearFree" "on"
reminds me of a pdf viewer at some point had an option to "respect permission" or something, you could turn it off and ignore the limits on the pdf that the author set.
Oh yeah, I always say "Don't respect" on PDF readers that have that setting. It's a very nice setting.
In regards to "TearFree" not being on by default, I expect that there's a good reason for it... maybe it adds some amount of latency (whether on hardware I don't have, or so little latency that I don't notice it), or maybe it just flat-out doesn't work right on some hardware that I happen to not have.
Regardless, deciding whether or not to set those settings is the job of one's distro.
I think is more probable that anyone will have a problem in Wayland than X
Ready means if everything is flawless to MacOS/Windows levels, where you never have to think about display server compatibility, and that's where X11 is still king despite the performance shortcomings. At least it always just works™ and compatibility beats performance most of the days.
I could excuse it if it had been 4 years old or so, but it's old enough already it can drink and smoke in Europe.
If that game were to be launched today and feature a setting in the same time delta, it would be set in 2008 when movies like The Dark Knight or the first Iron Man launched.
How time flies.
Xorg was a fork of XFree86, which was released in 1991. So that codebase was 17 years old when Wayland was first released. I don't think the date of the fork is what's relevant here.
I could also argue that you should be comparing the Wayland protocol (2008) vs the X11 protocol (1987), or even older versions of X (1984).
On https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/ it even says:
> Wayland
> Works just the same :D
Apart from that while it's true that the compositor has to do everything, some of the interfaces seem to be shared (standardized? I don't know enough about Wayland development tbh) across different compositors: https://wayland.app/protocols/
> It's now up to each desktop environment project (e.g. GNOME or KDE Plasma) to develop their own full featured GUI for tablet configuration.
That doesn't sound ideal.