I do like how the wayland usage statistic are based on wayland apps crashing more than x11 apps
How do you get that?
They showed the statistics based on their telemetry tools and said they match crash data.
Not that it was 100% from crashes.
Also the fact they can tell which one is in use does not mean that’s the reason it crashed. It could be crashes due to bad network handling or file corruption or something that has nothing to do with the GUI.
Good old David - he loves systemd. No wonder he does not like X11. Oldschool KDE devs were better. Today's generation of David or Nate, are just killing KDE off. But no worries, on their blog they'll continue how everything is great. It is so great that they need a donation-widget to keep on pestering people to donate. So now you can pay for them ruining the legacy here.
I don't really like Systemd neither - but Wayland and Systemd are pretty much opposites of each other. Systemd does (too) many things, many of them badly. Wayland does well what it does, but it (still!) does too little. Wayland is adding features and is pretty close to doing "everything necessary". Systemd keeps accreting worse replacements for existing services.
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
I know nothing about the detailed technical differences between X11 and Wayland but with Hyprland for me the PIP is working as expected so I assume its not just a Wayland issue but specific to the window manager you are using? Maybe somebody else can explain?
Gnome has a "Always on Top" toggle for each window. I imagine there's a protocol for an application to set it by default but the OP's window manager might not implement it or there might be an incompatibility.
I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11. I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.
When was the last time you tried? What compositor?
> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations [sic], and brand new exciting features throughout Plasma. I wish they would have listed what some of those features might be.
Did you really just [sic] a British guy using British spelling?
I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11. I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.
Well, there's SonicDE, but like many such projects it's probably maintained by reactionaries which introduces its own suite of issues around security, code quality, and "will this be maintained in a year, 5 years?"
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
I know nothing about the detailed technical differences between X11 and Wayland but with Hyprland for me the PIP is working as expected so I assume its not just a Wayland issue but specific to the window manager you are using? Maybe somebody else can explain?
Isn't that usually how it goes? Wayland is a million little optional protocols, which in the abstract is a lovely idea but in practice means which things work depends on which grab-bag of features your compositor supports.
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
I know nothing about the detailed technical differences between X11 and Wayland but with Hyprland for me the PIP is working as expected so I assume its not just a Wayland issue but specific to the window manager you are using? Maybe somebody else can explain?
As far as I know, there are multiple Wayland implementations. Which is also not good because it creates fragmentation and potential inconsistencies (some subtle differences in behavior, differences in bugs, etc). Maybe Hyprland solves the issue, but I don't want to use this DE just because it solves this particular issue. I have tons of other needs and preferences.
> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations [sic], and brand new exciting features throughout Plasma. I wish they would have listed what some of those features might be.
They're still trying to figure that one out themselves.
I’m not surprised they’re not nailed down. But I’d appreciate seeing a “we’re looking at X or Y or if Z is now possible” kind of thing.
The maintenance and performance stuff is good, but it’s not exactly end user stuff. Yeah you benefit but it’s less obvious.
I don’t follow this stuff closely so personally I have no idea what kind of Wayland only features could exist that couldn’t before.
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
I can't speak for Chrome, but I can right click a Firefox picture-in-picture window, tell it to remain on top, and it does, no problem. I've been using Plasma Wayland for years now and this has worked for ages