4 ms·

>Next you're gonna tell me that Wayland will be usable in the next decade. It's already usable today, so I don't see why you'd need to wait for a decade.

ChuckNorris89 4y ago
>It's already usable today, so I don't see why you'd need to wait for a decade. No, it's not usable for me. I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) No scroll acceleration settings. Currently, Wayland is one step forward, one step back. Especially that many highly used apps still haven't made the switch and that Wayland has not yet feature parity to what X11 offered.
- Arnavion 4y ago
  >I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. Works fine in at least all wlroots compositors (via xdpw) and in GNOME (via xdpgtk). The Electron versions presumably don't use PW so they'll only share Xwayland windows. The browser versions will be able to share everything through xdp since all major browsers support PW. >Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) Dunno, works for me. Firefox isn't exactly the poster-child of intelligent decisions. >No scroll acceleration settings. Depends on the compositor. sway supports them. Not a Wayland problem. >Currently, Wayland is one step forward, one step back. Nope. >Especially that many highly used apps still haven't made the switch Yes they have. For starters, every GTK3+ and Qt 5+ program will already use Wayland if it exists. >Wayland has not yet feature parity to what X11 offered. Yes it has.
  - ChuckNorris89 4y ago
    Thank you for proving my point. If you need to tinker with all that in an OS just to get a usable system, then, repeat after me, it's not ready.
    - Arnavion 4y ago
      Good thing there's no tinkering mentioned in my comment, then.
      - ChuckNorris89 4y ago
        Oh sorry, you're right, your comment was basically "it works on my computer therefore Wayland is usable, period"
        Arnavion 4y ago
        "HTML isn't usable because elinks doesn't show inline images." - ChuckNorris89
  - greyw 4y ago
    > >I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. > Works fine in at least all wlroots compositors (via xdpw) and in GNOME (via xdpgtk). The Electron versions presumably don't use PW so they'll only share Xwayland windows. The browser versions will be able to share everything through xdp since all major browsers support PW. > >Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) > Dunno, works for me. Firefox isn't exactly the poster-child of intelligent decisions. > >No scroll acceleration settings. > Depends on the compositor. sway supports them. Not a Wayland problem. > >Currently, Wayland is one step forward, one step back. > Nope. > >Especially that many highly used apps still haven't made the switch > Yes they have. For starters, every GTK3+ and Qt 5+ program will already use Wayland if it exists. > >Wayland has not yet feature parity to what X11 offered. > Yes it has. Wayland still doesnt support color managment and tearing updates (the latter might not happen because wayland people dont understand the usecase)

ChuckNorris89 4y ago

>It's already usable today, so I don't see why you'd need to wait for a decade. No, it's not usable for me. I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) No scroll acceleration settings. Currently, Wayland is one step forward, one step back. Especially that many highly used apps still haven't made the switch and that Wayland has not yet feature parity to what X11 offered.

Arnavion 4y ago
>I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. Works fine in at least all wlroots compositors (via xdpw) and in GNOME (via xdpgtk). The Electron versions presumably don't use PW so they'll only share Xwayland windows. The browser versions will be able to share everything through xdp since all major browsers support PW. >Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) Dunno, works for me. Firefox isn't exactly the poster-child of intelligent decisions. >No scroll acceleration settings. Depends on the compositor. sway supports them. Not a Wayland problem. >Currently, Wayland is one step forward, one step back. Nope. >Especially that many highly used apps still haven't made the switch Yes they have. For starters, every GTK3+ and Qt 5+ program will already use Wayland if it exists. >Wayland has not yet feature parity to what X11 offered. Yes it has.
- ChuckNorris89 4y ago
  Thank you for proving my point. If you need to tinker with all that in an OS just to get a usable system, then, repeat after me, it's not ready.
  - Arnavion 4y ago
    Good thing there's no tinkering mentioned in my comment, then.
    - ChuckNorris89 4y ago
      Oh sorry, you're right, your comment was basically "it works on my computer therefore Wayland is usable, period"
      - Arnavion 4y ago
        "HTML isn't usable because elinks doesn't show inline images." - ChuckNorris89
- greyw 4y ago
  > >I still can't share my screen in Slack or Teams making calls with Windows and Mac colleagues an embarrassing mess. > Works fine in at least all wlroots compositors (via xdpw) and in GNOME (via xdpgtk). The Electron versions presumably don't use PW so they'll only share Xwayland windows. The browser versions will be able to share everything through xdp since all major browsers support PW. > >Firefox in Ubuntu 22.04 has Wayland disabled by default (why though, if Wayland is so usable?) > Dunno, works for me. Firefox isn't exactly the poster-child of intelligent decisions. > >No scroll acceleration settings. > Depends on the compositor. sway supports them. Not a Wayland problem. > >Currently, Wayland is one step forward, one step back. > Nope. > >Especially that many highly used apps still haven't made the switch > Yes they have. For starters, every GTK3+ and Qt 5+ program will already use Wayland if it exists. > >Wayland has not yet feature parity to what X11 offered. > Yes it has. Wayland still doesnt support color managment and tearing updates (the latter might not happen because wayland people dont understand the usecase)