

The very first attempts at organizing something for Wayland development were much later in 2008, also by that exact same group of devs that had worked on X.Org and XFree86 <4.3 (it's not like there were any other devs around familiar with the intimate workings of display servers to compete with them). and founded an organization to develop a GPL-compliant fork based on the previous version, XFree86 4.3. X.Org was founded and forked XFree86 in 2004, not to "fix bugs", but because the company developing XFree86 decided to release the next version, XFree86 4.4 with a non-GPL license. Your timeline and explanation is way off. Wayland may seem new to you but if your are a Fedora Gnome user, you've been using it since 2016, if you are a long-time Ubuntu user, you may remember a Mark Shuttleworth blog post glowingly and excitedly talking about Wayland way back in 2012. So yes, in a way you could say they are 'jumping the gun' but you should understand that the are aware of this, and it wasn't the first choice, but after a decade of feet-dragging in the linux community, somethings gotta accelerate things.

Fedora, Gnome, RHEL, and probably others are dropping Wayland in part to try to accelerate the pace of development and improvement. Support for Wayland is not nearly 100% there yet, but it won't ever be if projects are allowed to continue to put it off indefinitely because its easier for them to just stick with X11. The thing it is replacing X11 is no longer even being actively developed.

Wayland is the default in most major distros (Fedora, RHEL, SUSE, Debian, Ubuntu), even conservative distros like Debian default to Wayland now (with Gnome/KDE). Only in the world of Unix/Linux can a decade old project be considered the distant future. We know spam when we see it and will delete it. This means things like repetitious posting of similar content, low-effort posts/memes and misleading/exaggerated titles on link posts. We all need to support each other to help GNU/Linux gaming grow. If it's a link post, think about writing a comment to tell us more - the more you engage with us, the more we like it. Remember you are talking to another human being.ĭevs and content producers: If you've ported your game to Linux or created some GNU/Linux-gaming-related content (reviews, videos, articles) then, so long as you're willing to engage with the community, please post it here. Heated discussions are fine, unwarranted insults are not. What exactly did you do, and how, and with what version of what? How have you tried to troubleshoot the problem? Vague, low-effort tech-support requests may get removed. Include relevant details like logs, terminal output, system information. Tech-support requests should be readable by and useful to others. It is not (primarily) a tech-support forum. /r/Linux_Gaming is for informative and interesting gaming content, news and discussions.
