My experience has been less that stellar, but it’s always improving.
I’ve accepted it’s inevitable, but at the moment nobody’s forcing me to switch and I have zero motivation to. I haven’t had any issues with X in years.
Thankfully, I’m not in Ubuntu, so I don’t have anyone shoving their decisions down my throat (software-wise).
Oh, about 4 or 6 months ago? I had problems with font scaling and multiple monitors with different resolutions, and correct DPI handling. I hear that’s all been fixed, but I haven’t tried it yet.
I have no reason to try it. X works just fine for me. I have herbstluftwm set up the way I like it, and there’s only one Wayland window manager that looks at all similar in functionality to herbstluftwm (niri?). picom gives me all of the functionlity I find useful or attractive: dimming non-focused windows and light tranparency on terminals. Switching would be a lot of work, finding a bar to work like polybar, getting the WM set up, finding a good terminal to replace rio. And why? For what? X works well and reliably, and I don’t have any edge cases like I did in Wayland, so should I make the time and effort to switch? There’s no compelling reason, at the moment. There’s nothing I want, or need, from Wayland.
I’ll probably log in to Niri to play with it one of these days when I have nothing better to do. I’m curious if it does anything herbstluftwm doesn’t.
Eventually, I may be forced to switch, but at the moment I just see a bunch of unnecessary effort on my part to just get back to what I have under X now. Seriously, what’s the compelling reason for me to use Wayland?
Niri is interesting. It has a configuration file, and the config file is in yet another fairly complex config language: not toml, not yaml, not ini, not json. That’s something I’m avoiding.
It’s funny people’s X and Wayland experiences are so varied. I could never stop screen tearing with X, on multiple machines, with Wayland I never had any tearing. It brought along different small issues, but never had tearing, which in my opinion was a better option than no issues and tearing. These issues got fixed with time, and now I’d hate to go back to X.
It doesn’t?
I can’t log in or shutdown on Wayland. Switch to X and it works fine.
I’m sure it’s fixable, but why should I have to?
This is a wild question to ask about Linux lol
My experience has been less that stellar, but it’s always improving.
I’ve accepted it’s inevitable, but at the moment nobody’s forcing me to switch and I have zero motivation to. I haven’t had any issues with X in years.
Thankfully, I’m not in Ubuntu, so I don’t have anyone shoving their decisions down my throat (software-wise).
When’s the last time you used Wayland? I tried a few years back and there were quite a few paper cuts.
I’ve been using sway for about six months and there is one obnoxious paper cut, and one thing that just doesn’t work.
The paper cut for me is a java app that won’t render menus correctly. Most menus work, but there are a few that don’t draw properly.
The one thing that still doesn’t work is deskflow.
Screen sharing with zoom and Google meet and jitsi work fine. Keyboard input changes work fine, and most things are just hunky dory.
Oh, about 4 or 6 months ago? I had problems with font scaling and multiple monitors with different resolutions, and correct DPI handling. I hear that’s all been fixed, but I haven’t tried it yet.
I have no reason to try it. X works just fine for me. I have herbstluftwm set up the way I like it, and there’s only one Wayland window manager that looks at all similar in functionality to herbstluftwm (niri?). picom gives me all of the functionlity I find useful or attractive: dimming non-focused windows and light tranparency on terminals. Switching would be a lot of work, finding a bar to work like polybar, getting the WM set up, finding a good terminal to replace rio. And why? For what? X works well and reliably, and I don’t have any edge cases like I did in Wayland, so should I make the time and effort to switch? There’s no compelling reason, at the moment. There’s nothing I want, or need, from Wayland.
I’ll probably log in to Niri to play with it one of these days when I have nothing better to do. I’m curious if it does anything herbstluftwm doesn’t.
Eventually, I may be forced to switch, but at the moment I just see a bunch of unnecessary effort on my part to just get back to what I have under X now. Seriously, what’s the compelling reason for me to use Wayland?
Well, Niri is a dynamic and scrolling tiling compositor. So it offers that.
Well, and Niri supports Wayland.
Niri is interesting. It has a configuration file, and the config file is in yet another fairly complex config language: not toml, not yaml, not ini, not json. That’s something I’m avoiding.
It’s a novel and interesting approach.
It’s funny people’s X and Wayland experiences are so varied. I could never stop screen tearing with X, on multiple machines, with Wayland I never had any tearing. It brought along different small issues, but never had tearing, which in my opinion was a better option than no issues and tearing. These issues got fixed with time, and now I’d hate to go back to X.