I’m talking about FOSS software incompatibilities, I don’t have any expectation for mega corporate apps like Discord and Teams to adopt it. Those are a lost cause, I just use the browser versions and pray.
I truly do think this is a cool feature, but after seeing all the comments saying stuff like “now there’s ZERO excuse not to use Wayland!”, I felt like it was appropriate to share my perspective as a professional user who uses their computer a little differently than a FOSS enthusiast or hobbyist/casual user. I’m not getting paid to go around submitting bug reports and making PRs, so when things don’t “just work” it can be a big issue.
“Zero excuse” is a bit of a stretch, I aggree, but most things work really well now in my, and a lot others experience, at least recently. I also do my work full time on Linux, it’s mostly devops/sysadm work so a lot of what I use is terminal, web browser and well… Teams and Slack (the first one work well with an unofficial client, the latter got fixed recently), so it’s really not that hard to switch to Wayland. On my private machine I do mostly gaming, consuming content, some basic audio production and editing and there I rely a lot on X11 programs some running through Wine. They all work fine on Xwayland, recently even including HiDPI support (at least with simple one screen scenario). It’s really hard to find completely broken use case unless it’s something like automation scripts that move windows around, emit click or capture keyboard input globally and were designed strictly for X11. Oh, and apps that have multiple windows and request certain positioning - that is currently still missing and WIP.
On the other hand, the topic was originally about VR. While still kinda early, gimmicky and niche, it’s pretty cool modern tech. Good luck with that on X.
Even more common cases like high refresh rates with multi screen setups, VRR, all suck on X11 while working nicely on Wayland for some time now, at least with good drivers.
I’m talking about FOSS software incompatibilities, I don’t have any expectation for mega corporate apps like Discord and Teams to adopt it. Those are a lost cause, I just use the browser versions and pray.
I truly do think this is a cool feature, but after seeing all the comments saying stuff like “now there’s ZERO excuse not to use Wayland!”, I felt like it was appropriate to share my perspective as a professional user who uses their computer a little differently than a FOSS enthusiast or hobbyist/casual user. I’m not getting paid to go around submitting bug reports and making PRs, so when things don’t “just work” it can be a big issue.
“Zero excuse” is a bit of a stretch, I aggree, but most things work really well now in my, and a lot others experience, at least recently. I also do my work full time on Linux, it’s mostly devops/sysadm work so a lot of what I use is terminal, web browser and well… Teams and Slack (the first one work well with an unofficial client, the latter got fixed recently), so it’s really not that hard to switch to Wayland. On my private machine I do mostly gaming, consuming content, some basic audio production and editing and there I rely a lot on X11 programs some running through Wine. They all work fine on Xwayland, recently even including HiDPI support (at least with simple one screen scenario). It’s really hard to find completely broken use case unless it’s something like automation scripts that move windows around, emit click or capture keyboard input globally and were designed strictly for X11. Oh, and apps that have multiple windows and request certain positioning - that is currently still missing and WIP.
On the other hand, the topic was originally about VR. While still kinda early, gimmicky and niche, it’s pretty cool modern tech. Good luck with that on X. Even more common cases like high refresh rates with multi screen setups, VRR, all suck on X11 while working nicely on Wayland for some time now, at least with good drivers.