After reading about Wayland for 10 (?) years and thinking it was some huge deal, I finally took the leap as I was redoing my window manager anyway and it was quite easy (at least on NixOS). Heck virt-viewer (one of my main apps) is still running under Xwayland because the performance seems better.
Oh for sure. The point is the way I hear it talked about even today is as if it's going to be really great at some point in the future, but involves a lot of off-the-beaten-path tinkering if you want to use it right now. But there really wasn't much tinkering!
Honestly with "AI" helping a lot of the boring configuration tedium, I feel like I might finally reach the stage where I like my desktop environment config.
The only reason why I'm not running Wayland on my Framework laptop is that there's some really weird bug where it hardlocks the system, and after I force-reboot it, the audio chip doesn't come back up unless I drain or unplug the battery. X11 doesn't have this issue.
Of course, this was also several years ago, and it's possible the bug has been fixed. Maybe I should try Wayland again.
After reading about Wayland for 10 (?) years and thinking it was some huge deal, I finally took the leap as I was redoing my window manager anyway and it was quite easy (at least on NixOS). Heck virt-viewer (one of my main apps) is still running under Xwayland because the performance seems better.
10 years ago Wayland was in much worse state. It started being good in the last few years, though some features are still lacking.
Oh for sure. The point is the way I hear it talked about even today is as if it's going to be really great at some point in the future, but involves a lot of off-the-beaten-path tinkering if you want to use it right now. But there really wasn't much tinkering!
Honestly with "AI" helping a lot of the boring configuration tedium, I feel like I might finally reach the stage where I like my desktop environment config.
The only reason why I'm not running Wayland on my Framework laptop is that there's some really weird bug where it hardlocks the system, and after I force-reboot it, the audio chip doesn't come back up unless I drain or unplug the battery. X11 doesn't have this issue.
Of course, this was also several years ago, and it's possible the bug has been fixed. Maybe I should try Wayland again.