this post was submitted on 09 Oct 2023
337 points (98.6% liked)
Linux
48417 readers
1050 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I play Heroes of the Storm through Lutris.
I have a superultrawide 32:9 monitor.
In X11, I can get HotS to scale past its normal limits just like I could in windows and take up a full 5120x1440 resolution.
In Wayland, I can't.
I will die on this hill.
thy gamescope(that run on steam deck) i think it can scale, if yes, so it's an implementation issue, that need to be fixed by the compositor
It is a Wayland issue that things like this need to be fixed per compositor. Honestly, what were the designers thinking?
the compositor need to implement the option to change resolution, how could wayland(the protocol) dictate it?, it don't have a feasible way to do it, what could help is less fragmentation, like using wlroot, but again wayland(protocol) don't habe a way to dictate it
If they had kept the window manager concept, separating mechanism and policy they would have only needed one implementation for all the mechanisms.
yes, they could have made the implementation from the start, and that is a valid criticism to wayland(i also agree), but we have wlroots now, and they are working very close with KDE(in one of the devs blog they even said about KDE being ported to wlroots in the future), except for gnome, every DE are working together
Why should it not be fixed by the compositor, exactly?
As far as I see it, that's a smart design choice, the issue is just that we needed a universal implementation, an x.org equivalent, and we now have that with wlroots, now that that exists, there's no downsides to that approach, as far as i'm aware.
In what way exactly does that make it a smart design choice. It sounds like compositor implementers essentially have to work around the bad design choice by including a library and even then each compositor will have to update the dependency version for wlroots each time something needs to be fixed that breaks the wlroots ABI (or for containers, static linking,... just each time).
No, it sounds like compositors will use a library so that they don't have to do a shitload of work that they'd have to do otherwise.
...this is already how x.org works. You have to implement the x.org server, or create your own implementation of X11.
The only reason you think your criticism doesn't apply to X.org is because nobody updates X.org anymore... There's no more breaking changes to be made because it's a fundamentally broken, shitty protocol.
there is a base implementation basically all compositors are based on