3 ms·

Wayland is already done and ready. It has been the default in fedora for years and works perfectly fine. The slow rollout is because nvidia won't support it so

Wayland is already done and ready. It has been the default in fedora for years and works perfectly fine. The slow rollout is because nvidia won't support it so only distros that reject nvidia like Fedora will ship it. Fedora is probably the only distro actually pushing things forward without being tied down to vendors. When CgroupsV2 came out it was disabled for many years because docker didn't support it. Until fedora decided to turn it on and suggest users use podman instead which got docker to update to v2.

shmerl 6y ago
It's very far from done and ready. Where is adaptive sync in KWin on Wayland? That's a major feature for gaming. Subsurfaces clipping is a huge mess and so on. Because of all that I'm still using X11 session.
Blikkentrekker 6y ago
It's default on Fedora because Fedora assumes it's users to have a use case no more advanced than browsing the internet and editing some text documents, and perhaps running a compiler. A very simple reason that I can't use Wayland is that I have a piece of software I sometimes use that is bugged and doesn't properly exist when it's window closes at times, so I actually run a very simple daemon that checks whether the window is gone, and if that be so, sends a signal to close it that way so I don't have to do it manually every time — I can't do such simple things on Wayland because asking for a list of all open windows is “insecure”.
- cycloptic 6y ago
  If you are on GNOME Wayland, try using this shell snippet to close a window with a specified app id. (I used firefox as an example but you can change it) busctl call --user org.gnome.Shell /org/gnome/Shell \ org.gnome.Shell Eval s \ 'global.get_window_actors().forEach(w => w.meta_window.wm_class == "firefox" && w.meta_window.delete(global.get_current_time()))'
- dylan-m 6y ago
  > It's default on Fedora because Fedora assumes it's users to have a use case no more advanced than browsing the internet and editing some text documents, and perhaps running a compiler. And, you know, developing a complete desktop operating system. (Fedora's developers are its users, almost universally).
  - Blikkentrekker 6y ago
    That would be something that is done by browsing the internet, editing text documents, and running a compiler. Writing software is really not something that is demanding of the features of a display protocol — and that Wayland is developed by those that write software without consulting users that say, play videogames is why it's so lacking. At the end of the day, playing even the simplest video games tends to be more of test for the merits of a display protocol than writing said video game from scratch, without playing it.
    - kaba0 6y ago
      Wayland is developed by those who... wrote Xorg?
still_grokking 6y ago
Wayland is done and ready when Debian Stable finally switches the default display server - not Fedora.
- the_why_of_y 6y ago
  GNOME in buster defaults to using the Wayland display server instead of Xorg. https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.en.html#wayland-by-default-on-gnome https://www.debian.org/releases/buster/amd64/release-notes/c... Debian 10 "buster" released July 6th, 2019

shmerl 6y ago

It's very far from done and ready. Where is adaptive sync in KWin on Wayland? That's a major feature for gaming. Subsurfaces clipping is a huge mess and so on. Because of all that I'm still using X11 session.

Blikkentrekker 6y ago

It's default on Fedora because Fedora assumes it's users to have a use case no more advanced than browsing the internet and editing some text documents, and perhaps running a compiler. A very simple reason that I can't use Wayland is that I have a piece of software I sometimes use that is bugged and doesn't properly exist when it's window closes at times, so I actually run a very simple daemon that checks whether the window is gone, and if that be so, sends a signal to close it that way so I don't have to do it manually every time — I can't do such simple things on Wayland because asking for a list of all open windows is “insecure”.

cycloptic 6y ago
If you are on GNOME Wayland, try using this shell snippet to close a window with a specified app id. (I used firefox as an example but you can change it) busctl call --user org.gnome.Shell /org/gnome/Shell \ org.gnome.Shell Eval s \ 'global.get_window_actors().forEach(w => w.meta_window.wm_class == "firefox" && w.meta_window.delete(global.get_current_time()))'
dylan-m 6y ago
> It's default on Fedora because Fedora assumes it's users to have a use case no more advanced than browsing the internet and editing some text documents, and perhaps running a compiler. And, you know, developing a complete desktop operating system. (Fedora's developers are its users, almost universally).
- Blikkentrekker 6y ago
  That would be something that is done by browsing the internet, editing text documents, and running a compiler. Writing software is really not something that is demanding of the features of a display protocol — and that Wayland is developed by those that write software without consulting users that say, play videogames is why it's so lacking. At the end of the day, playing even the simplest video games tends to be more of test for the merits of a display protocol than writing said video game from scratch, without playing it.
  - kaba0 6y ago
    Wayland is developed by those who... wrote Xorg?

still_grokking 6y ago

Wayland is done and ready when Debian Stable finally switches the default display server - not Fedora.

the_why_of_y 6y ago
GNOME in buster defaults to using the Wayland display server instead of Xorg. https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.en.html#wayland-by-default-on-gnome https://www.debian.org/releases/buster/amd64/release-notes/c... Debian 10 "buster" released July 6th, 2019