Originally posted by treba
View Post
Announcement
Collapse
No announcement yet.
SDL3 Will Keep Wayland Default At Least For The Time Being
Collapse
X
-
- Likes 6
-
Originally posted by dekernel View Post
Really, that seems odd since I have been using multiple monitors for quite some time with no issues. Now what I can tell you that doesn't work on my system is performing simple copy/paste sequences with Wayland.
- Likes 9
Comment
-
Originally posted by treba View Post
Hm, don't recall having had copy/paste issues in a long while - please report! Regarding multiple monitors: X11 compositors can only sync against one of them. So you have to choose - and *might* be lucky if all of them run at the close enough refresh rate to not see tearing and/or things run slower than necessary. Running a 144Hz and 60Hz monitor in parallel won't work well though and adding e.g. rotation etc. makes things even worse. The only option I'm aware of that helps around this is to not use a compositor - which, well, IMO does not count as functional post-2010. So IMO it's fair to say that X11 multi-monitor is simply broken by modern standards.
- Likes 2
Comment
-
Originally posted by ReaperX7 View PostThe main reason why many people are saying Wayland is a joke is the fact that XFree86 4.x took only five years to fully mature before Xorg took back control with X11R6 after the licensing issues.
Wayland has been out for over a decade and still has failed to deliver on its promises. It's still mostly broken.
Some of you say its "dead" and "old" really have no clue about how software works and what package stability means. Just because something isn't actively developed doesn't mean it's dead or abandoned. X still gets distribution level patches.
All Wayland did really was divide resources, development teams, and interest. It's droned on long enough to show it's pointless to continue when protocols can't be merged in a timely fashion. All of this could have been used to redevelop X11 to improve designs, security, driver handling, etc.
And yes, people's gripe with Red Hat is what it is, because they're literally the Microsoft of Linux wanting their Windows clone. That's been known for over 20 years.
- X11 is not gone and it is not going anywhere. If you like it, use it, take the source develop it, but just shut up!
- RedHat cannot dominate open source. Because it is open source, it is free software, nobody can be forced to follow them.
- Resources are not divided. People smarter than you are developing anything they want. They do not need your permission nor you can tell them what they should work on. Your opinion matters as much as your code.
- Likes 5
Comment
-
Originally posted by treba View PostHm, don't recall having had copy/paste issues in a long while - please report!
Since Fedora 31, Qt Wayland is on by default, meaning that Qt apps on Fedora 31+ don't use xcb anymore by default. Alas open-vm-tools seems to only work on xcb clients when it come to copying text ...
Still not resolved...
To me and my customers Linux in vmWare without functioning cut&paste is borderline useless. So nobody is using Wayland on vmWare, because cut and paste works properly in X11.
- Likes 3
Comment
-
Originally posted by kokoko3k View PostCan someone explain me what changes for end user?
If one is using an X11 environment, will SDL3 use X11?
Maybe the change impacts Wayland environments only and will skip XWayland?
Also, does Steam use SDL? Because otherwise, why is Valve so involved?
Comment
-
Originally posted by dlq84 View PostIf don't think you understand open source if you think they somehow hold Wayland hostage... If the community didn't like the way it's handled it would have been forked ages ago.
That's as naive as saying if the Windows API sucks in some way every dev will instantly switch to something better.
Except that doesn't fucking happen in reality.
Comment
Comment