| ▲ | ccakes 9 hours ago |
| This is a great project! I like and use Wayland but the portal protocols and extension mechanism does leave a lot to be desired. Wayland is still quite a way behind Windows and macOS in terms of what productivity users need An X11 rewrite with some security baked in is an awesome approach. Will be watching! |
|
| ▲ | drpixie 9 hours ago | parent | next [-] |
| I thought for a long time that rather than move to Wayland, we could come up with a tidied-up version of X. Sounds like a good and useful project, I hope it progresses. |
| |
| ▲ | reactordev 8 hours ago | parent | next [-] | | I thought this too and originally thought that’s what Wayland was going to do but it went off and did its own thing. I’m all for an X12. | | |
| ▲ | sho_hn 8 hours ago | parent | next [-] | | An X12 was briefly considered by the community before adopting Wayland: https://www.x.org/wiki/Development/X12/ If you take the time to read through that (very partial) list of cruft and footguns in X11 it probably makes it a little easier to understand why a clean-slate approach was able to attract momentum and why many hands-on involved developers were relatively tired of X11. Critics would of course respond that backwards compatibility is worth the effort and rewrites are often the wrong call, etc. It's the Python 2/3 debate and many others. | | |
| ▲ | PunchyHamster an hour ago | parent | next [-] | | Realistically rewrite would keep X11 compatibility layer and just do same wayland did, make new protocol. Just... without all that mess that turned out to be at best +/-, at worst outright negative causing problems for everyone involved.
And near all of the "advantages" are "the server is built from scratch" not "the protocol was the limitation" | |
| ▲ | reactordev 6 hours ago | parent | prev | next [-] | | I’ve been here since the beginning. I remember Usenet. X11 was built for multi-user terminals a kin to today’s Microsoft VDI garbage. There’s some good. A lot of bad. And some WTF in there. | |
| ▲ | glzone1 8 hours ago | parent | prev [-] | | Python 3 was actively antagonistic to Python 2 code for no reason other than to lecture us about how we were doing things wrong, writing code to support 2 and 3 to help transition was dumb etc etc. For example, in python 2 you could explicitly mark unicode text with u"...". That was actively BLOCKED with python 3.0 which supposedly was about unicode support! The irony was insane, they could of just no-oped the u"". I got totally sick of the "expert" language designers with no real world code shipping responsibilities lecturing me. Every post about this stuff was met by comments from pedantic idiots. So every string had to have a helper function around it. Total and absolute garbage. They still haven't explained to my satisifaction why not support u"..." to allow a transition more easily to 3. Luckily sanity started prevailing around 3.5 and we started to see a progression - whoever was behind this should be thanked. The clueless unicode everything was walked back and we got % for bytes so you could work with network protocols again (where unicode would be STUPID to force given the installed base). We got u"" back. By 3.6 we got back to reasonable path handling on windows and the 3 benefits started to come without antagonistic approaches / regressions from 2. But that was about 8 years? So that burnt a lot of the initial excitement. | | |
| ▲ | yjftsjthsd-h 4 hours ago | parent | next [-] | | > Python 3 was actively antagonistic to Python 2 code for no reason other than to lecture us about how we were doing things wrong, writing code to support 2 and 3 to help transition was dumb etc etc. > [...] > By 3.6 we got back to reasonable path handling on windows and the 3 benefits started to come without antagonistic approaches / regressions from 2. But that was about 8 years? So that burnt a lot of the initial excitement. So it's a great analogy. Wayland started out proudly proclaiming that it intentionally didn't support features in the name of "security" but everyone should "upgrade" because this was totally better, and has been very slowly discovering that actually all the stuff it willfully dropped was useful and has mostly evolved back to near feature parity with Xorg. | |
| ▲ | someguyiguess 5 hours ago | parent | prev | next [-] | | Python is really one of the worst designed languages. It always baffles me that people recommend it to beginners. | | | |
| ▲ | reactordev 6 hours ago | parent | prev [-] | | There’s a reason they’re called Pythonistas It’s always drama and they’re the center of it. (I’m joking of course, Merry Christmas) |
|
| |
| ▲ | bdhcuidbebe 8 hours ago | parent | prev [-] | | Be the change you want to see. Also happy winter solstice. |
| |
| ▲ | viraptor 5 hours ago | parent | prev [-] | | It was always an option, but "just" needed someone to dedicate all their time to it and pull in a group of long term maintainers. The real question is what will happen with the project in 2 years and will it be stable for day to day use. | | |
| ▲ | bsder 3 hours ago | parent [-] | | The fact that you can "assume Vulkan exists" helps a lot (both hardware and software renderers exist). Do remember--Wayland predates Vulkan by almost a full decade. In addition, you can offload OpenGL compatibility to Zink (again leaning into Vulkan). > pull in a group of long term maintainers. "Use new cool language" seems to be a prerequisite for this nowadays ... At least Zig is very compatible with C. | | |
|
|
|
| ▲ | reppap 6 hours ago | parent | prev | next [-] |
| I don't really understand what is supposedly missing in Wayland for productivity users? At work I have been using gnome with the wayland backend for years at this point and I can't really figure out anything that's missing. |
| |
| ▲ | sillystuff 5 hours ago | parent | next [-] | | Accessibility is apparently a big problem with wayland. E.g., the most popular / ?only? app that supports hardware eye trackers on Linux does not work with wayland, and states that it likely never will as wayland does not provide what it needs to add support (it is also the most popular app for voice/noise control). Even basic things like screen readers are apparently still an issue with wayland. Without a strong accessibility story, systems running wayland would have been banned at my last employer (a college). Personally, I have a 3200x2400 e-ink monitor that has a bezel that covers the outer few columns of pixels. I use a custom modeline to exclude those columns from use. And, a fractional scaling of .603x.5 on this now 3184x2400 monitor to get 1920x1200 effective resolution. Zero idea how to accomplish this with wayland-- I do not think it is possible, but if anyone knows a way, I am all ears. I ran into, at least, ten issues without solutions/work-arounds (like the issue with my monitor) when I tried to switch this year, after getting a new laptop. Reverted to a functional, and productively familiar, setup with X. | | |
| ▲ | pezezin 3 hours ago | parent [-] | | I don't know about other DE, but at least with Plasma there is a "overscan" option to compensate for hidden borders. |
| |
| ▲ | MrDrMcCoy 2 hours ago | parent | prev | next [-] | | Headless remote desktop, at least for KDE, is very much not possible today as far as I can tell. It's the last thing I miss from Xorg. | |
| ▲ | OsrsNeedsf2P 3 hours ago | parent | prev [-] | | Autoclickers and screen macros on Wayland are all janky |
|
|
| ▲ | nish__ 6 hours ago | parent | prev | next [-] |
| > Wayland is still quite a way behind Windows and macOS in terms of what productivity users need What's missing? |
| |
| ▲ | gen2brain 31 minutes ago | parent | next [-] | | Window positioning? You cannot position the window, you cannot send a hint, nothing? So my pop-up with GTK4 will randomly be placed somewhere, anywhere, without any control. OK, GTK4 went further and also removed popups without the parent, so you hack that with an invisible anchor window and then write platform-specific code for sane platforms that CAN, of course, move the window. And let's not talk about window icons that you have to put somewhere on the file system? | | |
| ▲ | bloppe 12 minutes ago | parent [-] | | It's not technically behind on window positioning. Rather, it was a deliberate choice not to support it. You can very reasonably object to that, but it is sorta a necessary measure to prevent clickjacking. | | |
| |
| ▲ | quantummagic 5 hours ago | parent | prev [-] | | Ads in the start menu, forced screenshotting of all your activity, and AI integration in every aspect of the desktop experience. | | |
|
|
| ▲ | redeeman 8 hours ago | parent | prev [-] |
| BS, windows and macos cant even do proper window managing for a start, and then it just goes downwards from there on.. You can perhaps install various weird third party things, but it does not come with it by default. If you took people who absolutely never tried any computing, and gave them macos, windows, and for example Plasma, they would NOT consider windows or macos to be ready for the desktop. If you go 15 years back, even way more so. even in the early 2000s, windows was so hilariously crappy that you had to make floppy disks to even get to install the thing. If PCs didnt come preloaded with windows, regular users would never ever be able to install it, versus the relative ease a typical linux distribution was to install. This is also one of the large reasons that when their windows slowed down due to being a piece of shit with 1000000 toolbars, people threw it out and bought a new, despite the fact that a reinstall would have solved it. |
| |
| ▲ | p_ing 5 hours ago | parent | next [-] | | > You can perhaps install various weird third party things, but it does not come with it by default. A Window Manager and Window Server don't come by default with Linux... It's always an install-time option on the major distros. > even in the early 2000s, windows was so hilariously crappy that you had to make floppy disks to even get to install the thing. Windows in the early 2000s installed just fine without a floppy directly from CD or PXE booting. | | |
| ▲ | PunchyHamster an hour ago | parent | next [-] | | Windows in early 2000s didn't even detect your early 2000s SATA drive Windows in early 2023 didn't even detect the network card it needed to download network card drivers. After changing mobos I needed to boot into linux to download network drivers for windows... Windows in early 2025 still uses SCSI emulation to talk with NVMe and only now the server part got a proper driver Windows in early 2025s still need virtio driver injection to boot properly as a VM without IDE emulation "Drivers working out of the box" were never windows strong part | |
| ▲ | tstenner an hour ago | parent | prev [-] | | Unless you needed a SATA driver not included in the installer because you wanted to avoid a legacy IDE emulation for your disks. |
| |
| ▲ | OsrsNeedsf2P 3 hours ago | parent | prev | next [-] | | > If you took people who absolutely never tried any computing, and gave them macos, windows, and for example Plasma, they would NOT consider windows or macos to be ready for the desktop. There's some truth to this. I've been installing fresh Windows 11s on family computers this holiday season, and good lord is it difficult to use. The number of tweaks I had to configure to prevent actively hostile programs from ravaging disk read/writes (HDD pain), freezing and crashing, or invasive popups was absurd. | |
| ▲ | figmert 4 hours ago | parent | prev | next [-] | | As someone who came from Windows, and has used Linux as my primary OS for 15 years, and MacOS here and there (cos work provided laptop), I can tell you that Linux was not ready for prime time 15 years ago. Today, I feel it is, but definitely not 15 years ago. | | |
| ▲ | akho 2 hours ago | parent [-] | | I use Linux on the desktop since 1997, and there was no point where Windows was even slightly more attractive. I don't know what "prime time" means here. edit: apart from, you know. Applications and drivers for random hardware. |
| |
| ▲ | 7bit 7 hours ago | parent | prev | next [-] | | 15 years back people were given Windows macOS and Linux and people voted which OS were ready for the Desktop and which were not. The only BS is your inflammatory contribution to this topic. | | |
| ▲ | PunchyHamster an hour ago | parent | next [-] | | Nope, Macs were expensive stuff games did not run on, and linux was just not pushed by near anyone. It was not a war "which desktop is easier to use", it was "which system can run stuff I need". And if "the need" was "video games and office stuff", your only choice was windows. | |
| ▲ | grim_io 6 hours ago | parent | prev [-] | | The average user only cares what they can run on the desktop. Linux did not have as much choice back then. |
| |
| ▲ | someguyiguess 5 hours ago | parent | prev | next [-] | | I can’t tell if this is satire. | |
| ▲ | MangoToupe 8 hours ago | parent | prev [-] | | > windows and macos cant even do proper window managing for a start Well they certainly manage them better than x11 and wayland. What a fucking nuts thing to say. Are you rms? | | |
| ▲ | sho_hn 4 hours ago | parent | next [-] | | Windows is reasonably OK, but MacOS' window management has always been really terrible. Just think through the many different iterations over the years of what the green button on the deco does, which still isn't working consistently, same as double-clicking the title bar. Not to mention that whatever the Maximize-alike is that you can set title bar double click too (the options being Zoom and Fill, buried in settings somewhere) is different from dragging the title bar against the top of the screen and chosing single tile. Which is different from Control-Clicking the green button. Maybe. It depends on the app. What a mess. Both of them miss (without add-ons) convenience niche features I cherish, such as the ability to pin arbitrary windows on-top, but at least the basics in Windows work alright and moreover predictably and reliabily. Window management in MacOS just feels neglected and broken. There may be many other ways in which MacOS shines as a desktop OS, and certainly in terms of display server tech it has innovated by going compositing first, but the window manager is bizarrely bad. | | |
| ▲ | MangoToupe 3 hours ago | parent [-] | | > Windows is reasonably OK, Doesn't windows conflate window and process? That should kick it to the bottom of the bin by default. > There may be many other ways in which MacOS shines as a desktop OS May I suggest examining why your keyboard has a "home" key |
| |
| ▲ | Arch-TK 7 hours ago | parent | prev [-] | | I don't use a Mac, but have you ever used Windows? I mean, maybe you have, but if you are not fussy then at worst MacOS is quirky and Windows and Linux are identical and merely have different icons. If you pay a little bit of attention you will notice that on linux things seem more flexible and intuitive. If you are very finnicky, there is nothing that comes close to X11 window managers when it comes to window management flexibility, innovation and power. | | |
| ▲ | II2II 6 hours ago | parent | next [-] | | Windows allows you to launch applications from a menu or via search. You can switch between windows with a mouse or keyboard shortcuts. Windows can either be floating, arranged in pseudo-tiled layers, or full screen. KDE can pretty much do the same under Wayland. Ditto for Gnome under Wayland, albeit to a lesser degree. That covers the bases for most people. X11 window managers were a mixed bag. While there were a few standouts, most of the variation was in the degree to which they could be configured and how they were configured. There may be fewer compositors for Wayland because of the difficulty in developing them, but the ones that do exist do standout. | |
| ▲ | MangoToupe 5 hours ago | parent | prev [-] | | > and Windows and Linux are identical and merely have different icons At least on this we can agree, but windows never had to reboot the window server in my experience |
|
|
|