-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all: use Wayland by default once it is stable/reliable/good enough consistently #1163
Comments
The last two are closed merge-requests, which aren't very helpful to track (as they're closed and unlikely to be reopened)
I'd like to note, however, that none of these look vital (most have workarounds or are only minor inconveniences) and Wayland is already suitable for use in games. |
Oh, also, if Wayland is available, it will almost always provide a better user experience than X11, as X11 clients will be running through XWayland, meaning they're hampered by the cumbersome X11 APIs, while also being subject to the restrictions and issues of Wayland applications. Running under XWayland can't remove any of the restrictions of Wayland, so there's no reason to default to X11 when Wayland is available. |
Copying from discord: Since mach is getting native wayland backend those above issues all can be avoided by being a "good wayland citizen". |
this issue should have been closed by the suspended toplevel state added to xdg-shell. it relies on compositors exposing v6 (mutter, kwin, hyprland), sway has v2, mir has v5, and gamescope has v3. connection buffer size control also got merged just yesterday. this also doesn't automatically fix compositors but allows compositors to fix the instant death condition, depending on what they set max connection buffer size to. |
Seems like the SDL3 PR has accelerated the progress libsdl-org/SDL#9345 |
(Thanks for this helpful list from @Clouddef)
Wayland has some fundamental flaws for games and other apps:
The goal of this issue is to answer this question: When is wayland good enough for us to use by default?
Today, Mach builds both X11 and Wayland support into the same binary and uses X11 by default. If
DISPLAY=
is set, then it uses Wayland.The text was updated successfully, but these errors were encountered: