Wine 10.0 Released With Native Wayland Support, Better HiDPI

It'll be more performant, lower latency, have proper HDR support (current method is a hack), scale properly based on your displays, and probably be generally less buggy long-term (probably more buggy when it first gets added since it's a pretty fundamental change).

You're currently using a compatibility layer called xwayland to run it, which adds a ton of cruft.

HDR support

Fractional scaling

No way. Containers are absolutely necessary to provide reliability across a wide range of distros and to keep games working in the future.

It makes running additional programs harder (opentrack for example)

Then we need better tooling and documentation to interact with the container, not to get rid of them. I don't see any technical limitation that would prevent your use case. It's just not implemented or maybe simply undocumented.

our computers less ours

How so? The end result is probably the opposite. Without the containers Steam would be less reliable on unsupported distros, which might mean your only choice would be to use Ubuntu LTS. That would be a much bigger loss of control.

Containers are good for a number of reasons, and definitely will not and should not be going away, instead use one of these tools to bypass it:

https://github.com/jcnils/protonhax

Does it? What containerization does it use? I thought it was similar to wine, just a process pointed at a windows exe, and an environment to make the app think it's running in a windows filesystem.

Maybe it is just too much time since I last played or with proton on wayland, it just takes that bit more power, so that my good ol 980 isn’t handeling it well 🤔

It's a translator. Takes commands that are meant for windows to understand, and translates them into something Linux can work with. If the program requires the services of the kernel, for instance, it makes its system call as usual but the call gets converted to a command for the Linux kernel. At the end of the day it's the Linux kernel doing the work that was aimed at the windows kernel, and there is no windows kernel anywhere at all. That's unlike an emulator where you'd be running the windows kernel inside your Linux environment.

Wine also creates a windows-looking file structure so that programs can find the stuff they're looking for where they expect them to be. Like, it creates a "program files" directory somewhere in your filesystem and tells the windows applications to look there if they need to. There's more to it, but you get the gist I hope.

In a way, wine extends your Linux environment to support windows stuff. Whereas an emulator would create a new windows environment entirely. The goal is not to trick software into thinking it's on a windows machine, it's to make it work on Linux. The difference there is that by making it work on Linux you can make it work together and share resources with the rest of the system instead of remaining isolated in its own emulated environment.

I can't fathom the use of Wine on Linux, clearly Tux has always had a Beer belly