5 ms·

Wayland is actually pretty stable. Nvidia has problem with OpenGL in Xwayland (i.e. 3d accel for x11 apps), otherwise, it should work. There are warts though,

Wayland is actually pretty stable. Nvidia has problem with OpenGL in Xwayland (i.e. 3d accel for x11 apps), otherwise, it should work. There are warts though, when using Wayland. When using scaling (doesn't have to be fractional, either), X11 apps are being upscaled, not downscaled, resulting in blurriness. Unfortunately, neither Firefox nor Chrome does support Wayland natively, and who wants to use their most used app on their computer in blurry mode?

nanna 8y ago
Must admit I don't understand what Wayland is, or X server for that matter. Would someone mind explaining it, for someone a bit dull of mind as myself?
- Shywim 8y ago
  In short: X.org is a decade old display server that became the standard to display graphical window on the majority of Linux distribution. GNOME, KDE, XFCE and others are/were client to this display server. Wayland is a new protocol where the window manager (ie GNOME, KDE,...) is responsible of directly managing the display. Each window manager must reimplement this protocol (or use a library already doing this work) which enable them to have more control over the windows. Applications must also directly support Wayland like they did for X.org before (which was the default commonly used, so no problem) or the user just have XWayland installed on their computer to show X.org windows inside a Wayland WM but then the application may not display correctly (blur, artifcats,...)
  - ch_123 8y ago
    It is perhaps worth noting that while X.org is about a decade old, it is an implementation of the X Window System protocol which dates back to the mid 80s. Suffice to say, quite a lot has changed in computer graphics/interfaces since that time, and most modern *nix operating systems end up circumventing quite a lot of X to offer modern features. Thus X brings quite a lot of legacy debt to the table which can't be easily removed.
    - oblio 8y ago
      Also, even back in the day, X wasn't considered the best tech around, at least by some. For example: https://en.wikipedia.org/wiki/NeWS https://en.wikipedia.org/wiki/NeWS was around. However NeWS' licensing was proprietary and X won out.
      - unstuckdev 8y ago
        Gopher and HTTP had a similar situation. Gopher had a lot going for it, but the future licensing situation was unclear. HTTP was free, clear, and widespread by the time Gopher became GPL.
lllr_finger 8y ago
After 10 years of work you still can't do much useful unless you run X and shim it with XWayland. "Stable" is a strange descriptor given this context.
- vetinari 8y ago
  "Stable" and "popular" are two different concepts. Yes, some apps and frameworks didn't bother yet with the switch. Some did, Qt5 or Gtk3 are fine.
jdofaz 8y ago
Firefox has recently added wayland support, it isn’t enabled by default.
- vetinari 8y ago
  It doesn't play nice with OMTC, or 3d accel in general (see EGL bugs in bugzilla), and has problems with scaling and input. It is a work in progress, that's why it is disabled.

nanna 8y ago

Must admit I don't understand what Wayland is, or X server for that matter. Would someone mind explaining it, for someone a bit dull of mind as myself?

Shywim 8y ago
In short: X.org is a decade old display server that became the standard to display graphical window on the majority of Linux distribution. GNOME, KDE, XFCE and others are/were client to this display server. Wayland is a new protocol where the window manager (ie GNOME, KDE,...) is responsible of directly managing the display. Each window manager must reimplement this protocol (or use a library already doing this work) which enable them to have more control over the windows. Applications must also directly support Wayland like they did for X.org before (which was the default commonly used, so no problem) or the user just have XWayland installed on their computer to show X.org windows inside a Wayland WM but then the application may not display correctly (blur, artifcats,...)
- ch_123 8y ago
  It is perhaps worth noting that while X.org is about a decade old, it is an implementation of the X Window System protocol which dates back to the mid 80s. Suffice to say, quite a lot has changed in computer graphics/interfaces since that time, and most modern *nix operating systems end up circumventing quite a lot of X to offer modern features. Thus X brings quite a lot of legacy debt to the table which can't be easily removed.
  - oblio 8y ago
    Also, even back in the day, X wasn't considered the best tech around, at least by some. For example: https://en.wikipedia.org/wiki/NeWS https://en.wikipedia.org/wiki/NeWS was around. However NeWS' licensing was proprietary and X won out.
    - unstuckdev 8y ago
      Gopher and HTTP had a similar situation. Gopher had a lot going for it, but the future licensing situation was unclear. HTTP was free, clear, and widespread by the time Gopher became GPL.

lllr_finger 8y ago

After 10 years of work you still can't do much useful unless you run X and shim it with XWayland. "Stable" is a strange descriptor given this context.

vetinari 8y ago
"Stable" and "popular" are two different concepts. Yes, some apps and frameworks didn't bother yet with the switch. Some did, Qt5 or Gtk3 are fine.

jdofaz 8y ago

Firefox has recently added wayland support, it isn’t enabled by default.

vetinari 8y ago
It doesn't play nice with OMTC, or 3d accel in general (see EGL bugs in bugzilla), and has problems with scaling and input. It is a work in progress, that's why it is disabled.