Wayland has at least one deal breaker for me. It doesn’t remember where my windows were at logout when saving the session. I have six virtual desktops and have specific windows in certain desktops. Putting everything back where they belong after each login, no thank you. Until they add that I’ll stick to X11.
You actually think the X11 protocol remembers any window positions?
Neither Wayland nor X11 do. It has always been the window manager that does it and whether or not some specific window manager does this using either protocol is an implementation detail of the WM.
I ended up switching to Wayland 3 or 4 years ago precisely because X11 was so shit about remembering my monitor positions. I had to run an xrandr script every time it booted or otherwise decided to shit itself. Using 2 GPUs didn’t seem like it was thought about in the X11 design.
Dual GPUs are no issue for x.org it’s just that automatic configuration assumes a somewhat standard machine or it gets confused. Should I tell you about the days before automatic configuration, of hand-editing XF86Config to tell the X server that no, I didn’t have a serial or ps/2 mouse but an USB one, and it had three buttons and a mouse wheel? Of seeing a list of monitor timings with the comment “CHOOSING THE WRONG THING MIGHT DESTROY YOUR HARDWARE”?
xrandr is actually quite recent (or I may be ancient), being able to do all that stuff at runtime was a godsend.
Oh, I fought with X11 many times over the past three decades (almost) that I’ve used Linux. But as soon as I could push that mess behind me because Wayland did as good or better, I jumped on that horse, let me tell you.
You can configure this with window rules and autostart apps when Hyprland starts. That’s not remembering what you had open the last time, but it will probably give you the experience you’re looking for.
It’s incredible that wayland is so incapable that it can’t even keep this kind of state, and we’re back to having to basically having to write .xinit scripts. Because that’s what little so far wayland offers: less than xinit.
That’s a really weird and dishonest take. If a compositor wants to implement that feature it absolutely can, Wayland or not has nothing to do with it. I’m just saying it isn’t implemented the way you want in the compositors I know of. Seems like all it needs is compositor developers who want what you want.
Wayland has at least one deal breaker for me. It doesn’t remember where my windows were at logout when saving the session. I have six virtual desktops and have specific windows in certain desktops. Putting everything back where they belong after each login, no thank you. Until they add that I’ll stick to X11.
You actually think the X11 protocol remembers any window positions?
Neither Wayland nor X11 do. It has always been the window manager that does it and whether or not some specific window manager does this using either protocol is an implementation detail of the WM.
That’s not a Wayland issue, that’s a compositor issue. Sway for example allows mapping apps to workspaces.
For that matter, Xorg didn’t handle this either, DEs or WMs did.
KDE + wayland on Tumbleweed gave me this experience.
Thts also what i do on hyprland too
I ended up switching to Wayland 3 or 4 years ago precisely because X11 was so shit about remembering my monitor positions. I had to run an xrandr script every time it booted or otherwise decided to shit itself. Using 2 GPUs didn’t seem like it was thought about in the X11 design.
Dual GPUs are no issue for x.org it’s just that automatic configuration assumes a somewhat standard machine or it gets confused. Should I tell you about the days before automatic configuration, of hand-editing XF86Config to tell the X server that no, I didn’t have a serial or ps/2 mouse but an USB one, and it had three buttons and a mouse wheel? Of seeing a list of monitor timings with the comment “CHOOSING THE WRONG THING MIGHT DESTROY YOUR HARDWARE”?
xrandr is actually quite recent (or I may be ancient), being able to do all that stuff at runtime was a godsend.
Oh, I fought with X11 many times over the past three decades (almost) that I’ve used Linux. But as soon as I could push that mess behind me because Wayland did as good or better, I jumped on that horse, let me tell you.
You can configure this with window rules and autostart apps when Hyprland starts. That’s not remembering what you had open the last time, but it will probably give you the experience you’re looking for.
Not the same thing. With session saving I don’t have configure anything.
It’s incredible that wayland is so incapable that it can’t even keep this kind of state, and we’re back to having to basically having to write .xinit scripts. Because that’s what little so far wayland offers: less than xinit.
That’s a really weird and dishonest take. If a compositor wants to implement that feature it absolutely can, Wayland or not has nothing to do with it. I’m just saying it isn’t implemented the way you want in the compositors I know of. Seems like all it needs is compositor developers who want what you want.
Not a deal breaker for me, but I’d love this feature.