17 ms·
Fractional scaling is kind of the most visible thing today. But to be clear, there’s a lot of benefits to wayland. Mostly the issues could be hacked around. Bu
by dijit 6y ago
Fractional scaling is kind of the most visible thing today. But to be clear, there’s a lot of benefits to wayland.
Mostly the issues could be hacked around. But let’s be absolutely clear with this: it is hacking around the issue.
Problem: tearing, solvable with double buffering, maybe.
Problem: Xorg runs as root, solvable, there’s ways of making your user have direct control of the frame buffer device.
Problem: Xorg is a network system, and a porous one, meaning it’s possible to intercept keystrokes from any running program. Solvable by running a mini X11 instance for each program.
Problem: Xorg is a network system, meaning it is very inefficient. (Imagine using TCP to talk to your SSD)
Problem: Xorg needs to be backwards compatible, so it can’t dig much into hardware features. Especially as the client may not be on the same machine as the server.
Overall, wayland is a good clean slate, it’s been in development a long time. X11 has major warts and they are hard to clear out.
- _jal 6y agoI find it personally a bit hilarious - Wayland has been Going To Be Great Soon for over a decade. I've never even had a reason to want to run it. But I'm sure it'll be great, any day now.
- toun 6y agoI find Wayland is great already for my usage, and has been for the last two years. If Xorg works for you and Wayland doesn't, that's perfectly fine too.
- _jal 6y agoDon't get me wrong - I would love to not deal with certain X warts. (I see substantially fewer warts than other people do, but that's just me.) It just seems Wayland's combination of technical requirements and political entanglements make it a sort of Zeno's Project, doomed to asymptotically approach peoples' expectations and desires, but never reach them.
- coldtea 6y ago>I find it personally a bit hilarious - Wayland has been Going To Be Great Soon for over a decade. So? The same has been the case for desktop Linux in general, for 2 decades.
- throw0101a 6y ago> So? The same has been the case for desktop Linux in general, for 2 decades. Some of us have been running Linux desktops for over two decades. Nothing more fun than setting Modelines manually for your VESA card: * https://en.wikipedia.org/wiki/XFree86_Modeline https://en.wikipedia.org/wiki/XFree86_Modeline
- edoceo 6y agoMy Gentoo/Xfce multiple monitors with Nvidia has been great for at least 10 years. Linux Desktop is Great. Wayland is still in the process of becoming great (I think it's making good progress too)
- de_Selby 6y agoLinux desktop has been perfectly fine for at least 1.5 of those decades.
- michaelmrose 6y agoDesktop linux actually worked pretty well in 2003 for my purposes. I started on Fedora Core 1. I burned a dvd hit the magic key to select a boot target booted it up told the installer what time zone I was in and what disks it could use and such details and rebooted after a while. Wine sucked and there was less software existed but it was perfectly possible to do the normal tasks one did with a computer.
- hedora 6y agoBack on my IBM 386/75MHz (yes, really), linux could only boot at 25MHz, yet its desktop environment was faster, prettier and more featureful than Windows @75MHz Edit: I guess it was a 486 in a 386 motherboard. Windows was definitely slower at 75MHz than Linux at 25MHz though: http://ps-2.kev009.com/sandy55/Interposer/386_upgrade.html#REV%20to%20486%20%20(%20for%20386%20SX http://ps-2.kev009.com/sandy55/Interposer/386_upgrade.html#R...
- KeyBoardG 6y agoFrom what I gather its a chicken and egg issue. Wayland would get more attention and development if it had more users. It would have more users if it had more feature development. Although a lot of the bigger gaps are closed or closing now. OBS now works on Wayland as of 03/30/2021 and Fedora plans to ship Wayland as the default.
- Conan_Kudo 6y agoFedora Workstation (i.e. GNOME) has already been shipping with Wayland by default. What's new is that Fedora KDE is also going to ship with Wayland by default. Reference: https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPlasma https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPl...
- kaba0 6y agoMaybe actually trying it and adding something to the discussion would be better?
- gspr 6y agoI very much agree with what you wrote. I'll just add a comment: > Overall, wayland is a good clean slate, it’s been in development a long time. X11 has major warts and they are hard to clear out. This may seem like it's irrelevant for the user. It isn't. Lots of things us users want are much easier and more attractive for developers to add to the clean slate design that is Wayland. For example: When I switched, an unexpected bonus I experienced was that my touchpad's behavior got orders of magnitude better. So I googled around a bit, and it turns out that almost all touchpad improvements just happen to occur on Wayland because the people who are interested in that aren't interested in wading through the X swamp in order to implement their stuff. (I mean, have you looked at the X code? Oh dear, oh dear, it's a daunting thing!)
- mrighele 6y ago> This may seem like it's irrelevant for the user. It isn't. Lots of things us users want are much easier and more attractive for developers to add to the clean slate design that is Wayland. This is something I don't understand about Wayland. How is it possible that something that is supposed to be much easier and more attractive for developers after TEN+ years of development still has so many issues ?
- stinkytaco 6y agoOn the other hand, a bunch of X11 issues were just listed, and X has existed three times as long. Some issues are architectural and thus probably not solvable, some are just persistent annoyances that must be difficult to fix and likely will not get fixed because X11 has so little active development anymore. X has enough issues that a good portion of the community said, "we've got to fix this". And frankly, I've used software from multi-billion dollar corporations that gives me more trouble in a day than Wayland does in a month.
- kaba0 6y agoThe protocol had been in development for that long, most compositors for a few years, and clients change their implementation up to their own schedule. I see it as a “failing” of the bazaar way of development, linux can’t just say we now use this API. So there is an inherent not enough user on the new API to bother porting, and due to not enough user it is not as streamlined/stable, and you have a vicious circle. But I have to say the issues with wayland are heavily overstated, and I think it is out of this cycle, and is getting quite a bit of steam.
- josefx 6y ago> Xorg is a network system, meaning it is very inefficient. (Imagine using TCP to talk to your SSD) I am quite sure that there is something wrong with your system if your X clients run through the IP stack by default.
- jrm4 6y agoSo, I see and understand these arguments in theory -- but, and I don't think I'm alone, none of them are actually pressing? I'm running Openbox/Xubuntu on a 4K monitor, doing some awesome equivalent-of-4-monitors work, then playing all the steam games I want with the Proton and the decent AMD GPU, all under X. "Font size is a little weird sometimes" is my only gripe? Put differently, I understand "hacking around the issue" criticism in theory -- but if you applied that sort of purity to, say, web programming -- step one would be, okay, first get rid of Javascript, an idea that I really do like in theory, but I know it's not happening.
- michaelmrose 6y agoYou said Xorg is a network system twice and I don't think you did enough research once. Wherein client and server are local it doesn't doesn't communicate via the network stack. The problem you imagine exists only in your imagination not reality. I don't care if xorg runs as root and I don't need to run an instance of xorg per application I simply install software from trusted sources and haven't managed to get malware between 2003 and now. I also didn't have issues with tearing in 2003 and I don't now. Generally speaking QT and GTK and other toolkits must concern themselves with the details of X others concern themselves with QT or GTK as they would under wayland. It is extremely likely that all players in the overall ecosystem who never had to specifically worry about X in many years have had more issues, work, and tears from wayland development than they would have had for the remainder of the next century with X. This is nearly entirely about presenting a saner stable base to improve the work for a tiny number of people actually developing the graphics stack in Linux to build upon and unfortunately they made poor design decisions at the start that have led to it taking 12 years and still not being ready for prime time in some ways. After doing the necessary research to understand the topic you could construct another post about the shortcomings of X that is actually factually correct but it would still be beside the point. Wayland would still be a poor work that squandered a lot of the opportunity of a clean slate despite its authors being in perhaps the best position possible to do so. In 20 years Linux if it exists on the desktop will be a weird opaque overengineered system that works when it works and is impossible for an end user to understand why it is misbehaving when it doesn't. On the bright side due to package management the windows solution of pave over the install and start over could probably be configured to automatically reinstall all your software for you!
- jrm4 6y agoAfter a few years of wondering about the "why," I find this comment very illustrating; it feels like Wayland is one of many Linux related efforts (like Gnome and KDE) that are not particularly interested in a high level of interoperability and/or long term durability. Instead, the goal is more in the direction of trying to make their preferred way of things more dominant in the ecosystem. Now, if those efforts are actually good at it then more power to them. But most of the time, that doesn't happen, and I think it harms the Linux ecosystem, one that I am a fan of, overall.
- sprash 6y ago> Fractional scaling is kind of the most visible thing today. And also perfectly possible with X11 because the pitch information is exposed via the Xrandr extention > Problem: tearing, solvable with double buffering, maybe. Solved since ages. Just enable Tearfree in your Xorg.conf. That also shows how great X11 really is. It allows you the choice to turn it on or off. Because Tearfree comes at a cost of latency. > Problem: Xorg runs as root, solvable, there’s ways of making your user have direct control of the frame buffer device. OpneBSD solved that two decades ago. Also it perfectly possible on Linux to run X11 as non-Root. > Problem: Xorg is a network system, and a porous one, meaning it’s possible to intercept keystrokes from any running program. This is a feature not a bug. The security paradigm is blacklisting (which means sandboxing untrusted apps) instead of whitelising (which means locking everything up and only allow the compositor to do stuff). Since the vast majority of Software on FOSS system is trusted X11 is the far superior solution here. > Problem: Xorg is a network system, meaning it is very inefficient. X11 runs even on 386's and beats Wayland in every performance metric, especially latency. After 13 years of development only some compositors come close to X11's performance. > Problem: Xorg needs to be backwards compatible, so it can’t dig much into hardware features. Backwards compatibility is a major feature even 40 year old Software runs on current Xorg which is an impressive feat. As for the "hardware features": DRI3 uses the exact same buffer sharing mechanism as the major Wayland compositors do. Wayland offers zero advantage in exploited Hardware features. On the contrary X11 is capable of using hardware layers that has the effect that you can smoothly move your mouse even on heavy load and OOM events. Wayland still completely craps out in that regard. > Overall, wayland is a good clean slate, it’s been in development a long time. It is a clean slate, but a very bad one. The wrong philosophy ("every frame is perfect") and the wrong abstractions ("everything in the universe is a buffer made of RGB values") make it a major step backwards in computer graphics on Unix/Linux.
- Sebb767 6y ago> The security paradigm is blacklisting [...]. Since the vast majority of Software on FOSS system is trusted X11 is the far superior solution here. This is absolutely not a good solution. Even if you audited all your software enough to consider it trusted (which is unlikely if you're not a purist - see IDEs, browsers, widevine, Docker ...), it does not guarantee anything is secure. Anything that receives input from the outside might be vulnerable to an RCE. If you're running it under a different user or in a jail, the impact is limited - unless it can access your X server, in which case it can simply log everything you type and escalate. Jailing an app is basically impossible under X. Yes, you can use Zephyr, but you're not going to be able to watch a video there and you're WM integration is going to be miserable as well. And realistically you'd really need to jail most apps. X11 might work for a lot of things, but blacklisting is absolutely not a superior approach.
- espadrine 6y agoI’d like to emphasize a major aspect that makes the switch a non-brainer: SECURITY. The “good old days” of unencrypted Internet, where everyone could see your cookies, are no longer acceptable; the same is true of X11. With X11, if you copy a password from your manager, you must assume all running apps now know it and transmitted it to a malicious server. There’s no way to tell. With Wayland, it is only transmitted upon pasting, and only done directly from the copier app to the paster app. With X11, everything displayed on the screen is compromised. Also, all inputs, keyboard and otherwise. With Wayland, each app only sees their own pixels. With X11, screen locking is pure hackery that doesn’t always protect the locked pixels and… login password. Traditionally, you are meant to trust that process boundaries on Linux are sacredly secure, which is why Spectre was a big deal. But in practice, that is only true under Wayland.
- marwis 6y agoX11 is also just a protocol and you can implement it securely and expose access control through extensions. In fact it already exists (XACE) just nobody is using it.
- jude- 6y agoExactly! It astonishes me that Wayland folks think that replacing the whole graphics stack is somehow easier than using an X extension that already exists. Really speaks to the profound immaturity of the project.
- cycomanic 6y agoMy god, those "wayland folks" were the same people developing X. They were not some unrelated people pushing an agenda. It's always fascinating to see all the arm chair experts saying things how things ought to be done without ever having written a X extension or anything of that sort.
- wander_homer 6y agoSo the fact that someone was a developer of X, means their resilient to following some agenda or non objective opinion? There's a really famous and often quoted talk about X vs Wayland from one of those developers and it was clearly made in a way to present Wayland in a better light by purposely portraying X11 in a bad way, for example by leaving out crucial details. Like in one example they picked on the slow startup time of applications and attributed it to the blocking calls made to X.org, without even mentioning that asynchronous alternatives are not only available, but toolkits like Qt were already using them exclusively at that time. The verdict of course was that X11 is broken and fixing that is almost impossible.
- marwis 6y agoIf you have enough permissions to intercept keystrokes in X via network monitoring then most likely you have enough permissions to intercept keystrokes in wayland e.g. by ptrace. You're not using TCP for local X, it's all Unix domain sockets and SHM. Hard to get any faster on Linux. One could certainly implement feature emulation to preserve backward compatibility with evolving hardware. Or just deprecate feature, X over network was pretty much broken for a long time. Not saying Wayland isn't an improvement over X but a lot of supposed limitations of X are often misrepresented and exaggerated.
- hedora 6y agoAlso, all the other “problems” with X have been solved for years. (No tearing, no root X1q on my box, in particular)