[v3ss0n]

Wayland is no way ready

  - O proper screen recording support
  - broken screen sharing 
  - No proper global keyboard shortcut
  - No push to talk support
  - Their developers are seriously crazy on their design decisions.
  - Several problems with multiple screens

A proper refactor of X11 should have been the way to go and there should had been X12 with modern technologies

[JoshTriplett]

> proper screen recording support

> broken screen sharing

Both work perfectly here with pipewire installed. I can do screen recording, and share my screen in video meetings in Firefox.

> No proper global keyboard shortcut

System-wide keyboard shortcuts already work, through the desktop. The ability for an arbitrary application to request a global keybinding is in progress and expected to become available soon.

> No push to talk support

Completely valid; that's the near-future global keybinding support mentioned in the previous point.

> Several problems with multiple screens

Such as? Reported bug URLs?

For the record, there are other known issues with Wayland, and they're being worked on; nobody's claiming Wayland is perfect at this point, just that the solution is to fix it rather than assuming it's doomed because it doesn't do some specific thing.

> A proper refactor of X11 should have been the way to go and there should had been X12 with modern technologies

Wayland is X12; it's designed and endorsed by the folks who worked on X11.

[redox99]

So, basic functionality is still not there 15 years after release.

And I believe gnome still has that thing where if the UI lags, the cursor lags.

Windows DWM, WDDM architecture, and anything graphics related on Windows is superior in so many ways. They should have copied that instead of the mess that Wayland is, which was developed in a manner that is typical for so many free software: the developers think they know better than the users about what features they need or don't need

[JoshTriplett]

> So, basic functionality is still not there 15 years after release.

X11 didn't have what we currently consider "basic functionality" for decades after its release.

The design of X11 says that every application connected to your display is completely trusted, hence why it can grab any key (and thus be a keylogger if it wants to be). The design of Wayland starts with the premise that every application connecting to your display might not be completely trusted, and thus has to ask for a global key shortcut. That makes some things harder, requiring the design of a protocol for such requests. It also makes it possible to have sandboxed applications. That seems like a tradeoff worth making.

[enriquto]

> The design of Wayland starts with the premise that every application connecting to your display might not be completely trusted,

What a strange premise... Do the wayland people have keylocks on all the rooms, drawers and cupboards on their houses?

Unix programs by default have access to all files in the user home. That's the main point of running programs after all: to edit your files. Letting these programs see all pixels in you screen does not seem that bad, does it?

If for some reason you want to run an untrusted application, use a container. But building your whole house around the "untrusted" premise sounds ridiculous.

[linuxandrew]

> If for some reason you want to run an untrusted application, use a container. But building your whole house around the "untrusted" premise sounds ridiculous.

I guess we should do away with memory protection as well. Filesystem permissions? Bah, they can go too, after all, a computer is generally used by a single person right?

The reality is that many users use untrusted applications that don't have access to home, ergo Flatpak. There are plenty of reasons why the free for all security model for X11 isn't suitable. Besides, that ship has well and truly sailed - most of the X11 devs have been working on Wayland for the better part of a decade now.

[mcpackieh]

> The reality is that many users use untrusted applications that don't have access to home, ergo Flatpak.

I'd like to see this quantified. How many people using flatpack are afraid of their application reading their files, vs using flatpack simply because it's a convenient way to install programs? I don't mean "oh me me!" responses, are there any user surveys to support the premise that average users are afraid of their applications?

Quite frankly I don't believe this level of paranoia is the norm. On Windows and MacOS, applications installed in the normal way can read the files on your desktop. This is the way it as always been on Linux too, with few exceptions. Letting the most paranoid users set the norms is a recipe for irrelevance. How popular is Qubes? It's a pain in the ass.

[mongol]

It is not a strange premise. It is the security model that for example Android uses. Unix security model is dated, and it is good that steps are taken in this direction.

[sam_lowry_]

Android is different, it is built to run untrusted apps.

My Linux Desktop runs Chromium, xterm, IntelliJ and occasionally Gimp.

Do I need the Wayland security model? Hardly so.

Am I an outlier among Linux Desktop users? Hardly so.

[Shekelphile]

It has nothing to do with security and everything to do with hollowing out all generic functionality and passing it on to the compositor. In other words, the devs are lazy and went for a minimalist approach and now we all get to suffer.

[kingofpandora]

Wow calling FOSS developers lazy is pretty low.

[hifycycyv]

> X11 didn't have what we currently consider "basic functionality" for decades after its release.

What's the relevance of this? You're position is that we should give up features we have for software that doesn't have them after 15 years of knowing they needed them.

[JoshTriplett]

No, my premise is that it takes time to develop features, and what's considered "basic" both changes over time and varies by person.

For instance, I would argue that "basic functionality" today, established by browsers and phones more than 15 years ago, is the ability to sandbox applications and not treat them as all-powerful. X still doesn't have that today. Wayland had that as a basic design premise from the beginning.

[musicale]

> Wayland is X12; it's designed and endorsed by the folks who worked on X11

That would make it a spiritual successor, but not X12.

Considering several comments - and PP's original issues - it also sounds like it isn't ready to become a candidate for X12 at this time.

[FloatArtifact]

What about accessibility that needs to emulate mouse and keyboard based on window titles/executable?

[grandinj]

> share my screen in video meetings in Firefox.

Yeah, in limited ways, the wayland functionality is there. But as soon as you step off the most-popular-path even a teensy bit, it breaks.

I am relying on Teamviewer for remote desktop access because the official RDP support breaks in a different way with every minor release.

[jeroenhd]

> - O proper screen recording support

Works just fine. I use OBS.

> - broken screen sharing

Never had any trouble with it.

> - No proper global keyboard shortcut

> - No push to talk support

On its way: https://github.com/flatpak/xdg-desktop-portal/pull/711 / https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.free...

> - Several problems with multiple screens

Haven't had any more than on X11, but then again I do use Nvidia hardware on Linux.

[mcpackieh]

OBS is absurd bloat. What's the wayland equivalent of `ffmpeg -f x11grab`?

[jeroenhd]

ctrl + alt + shift + R will record the screen on Gnome, it's built into the shell.

wf-recorder will do Wayland screen recording fromtthe she'll. I don't think anyone has bothered to implement Wayland screen recording in ffmpeg yet, maybe ask the ffmpeg mailing list to check if that's on the roadmap yet.

[jraph]

> [N]O proper screen recording support - broken screen sharing - No proper global keyboard shortcut - Several problems with multiple screens

I thing all these things work flawlessly in my KDE Wayland session.

By the way no more blinking and sound cut (my sound goes through HDMI) when rearranging screens.

I've been very late to make the switch (I did a few months ago because I always saw blocker issues with the wayland session), but now it is at a point it works better than on X11. I miss raising apps when they are called from another app (like calling Kate from the terminal) but I know this is coming soon.

[johnny22]

get to work,we're counting on you

[yjftsjthsd-h]

Or, users could stay on the perfectly fine X, and anyone who wants to push for Wayland adoption can put in the effort to make it not a regression.

[hsbauauvhabzb]

Users are at the mercy of developers. If you want to stay and care about maintenance, you’d better hope someone is there maintaining it.

[bandrami]

In that sense they're even more at the mercy of packagers. There's nearly 400 million repositories on Github alone; the pain point is curating those into a coherent system.

[hsbauauvhabzb]

Im not sure how many million of those are required to run gnome on x11 though.

[bandrami]

To run (let's ignore build deps for now) it needs dconf, desktop-file-utils, glib, schemas, python, ibus (you can disable it but it still has to be there, annoyingly), telepathy, a seat manager, pulse, polkit, eds, mutter, gtk4, and whatever fonts you want. If you want it to display on the local machine you'll need an xserver; as of now each of the apps can simply act as a client though (which is the capability they are discussing getting rid of).

I know this because I'm a packager...