Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

111–120 of 392 posts

Re: Preparing for KDE Plasma's Last X11-Supported Release

#111
post #45

Earlier quoted context omitted.

When I upgraded from Debian 12 to 13 on my personal laptop running KDE, I knew that the switch from X11 to Wayland would happen and was braced for all kinds of issues, like every other time I tried to switch to Wayland in previous years. Instead, I could tell literally no difference. Multiple desktops works fine, scaling works fine, screen capture works fine, old apps work fine, literally everything works just fine.…

I think I noticed lower latency, more consistent frame pacing (recent-ish improvement in KWin) and a more "solid" feel because everything in a frame is synchronized. On X11, you can have things like border and contents of a window not matching exactly while resizing. An early principle of Wayland was "Every frame is perfect", which is clearly reflected in how e.g. window resizing works.

my experience us sadly the opposite. when I'm recording gameplay with OBS with x11 and xfce I have roughly a 7-9ms frame render time and with Wayland and any desktop env it creeps up above 16ms, which means I can't get a solid 60fps.

in all other cases other than gaming and recording, Wayland has been a delight.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#112
post #82

I can't be the only long time Linux use who still has no real idea what X11 or Wayland are. Except that sometimes software won't work properly with one or the other and I need to paste some arcane command to fix it.

It's what puts graphics on the screen. If you are not interested in hacking or developing it, there's not much else to know except X11 is deprecated and Wayland is not finished, leading to this suboptimal situation.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#113
post #26

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?"

Is that "reactionaries" in the "we object to certain technology decisions" sense, like the anti-systemd crowd, or in the "software compatible with our political views" like the xlibre project?

A quick search (in which I found no evidence of heated controversy) suggests to me that it's the first one.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#114

Earlier quoted context omitted.

Right right, and I'm not saying users shouldn't be able to have a floating window with video (or whatever) in it. I'm saying it shouldn't be Chrome making that window floating and always visible.

I don't get it, if you're on google meet, and you want to make one of many videos PiP. How can you ever do that in the window manager? It has to be done in the application! You right click or click on the menu on that particular video, and click Picture in picture. How the heck can the window manager do it?

The application could tell the window manager it wanted an always on top window. The window manager could ask the user if it should allow or reject and remember for this application or not.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#115

Earlier quoted context omitted.

I think I noticed lower latency, more consistent frame pacing (recent-ish improvement in KWin) and a more "solid" feel because everything in a frame is synchronized. On X11, you can have things like border and contents of a window not matching exactly while resizing. An early principle of Wayland was "Every frame is perfect", which is clearly reflected in how e.g. window resizing works.

my experience us sadly the opposite. when I'm recording gameplay with OBS with x11 and xfce I have roughly a 7-9ms frame render time and with Wayland and any desktop env it creeps up above 16ms, which means I can't get a solid 60fps. in all other cases other than gaming and recording, Wayland has been a delight.

Do you have "allow tearing" enabled?

Re: Preparing for KDE Plasma's Last X11-Supported Release

#116

Plasma/Wayland Known Significant Issues[1] No ability to save and restore positions of native Wayland windows Real-fake-session-restored apps don't remember which virtual desktop their windows were on No full-screen aspect ratio correction "Spare Layouts" feature not implemented "Per-application Keyboard Layout" does not work No way to change the gamma or manually adjust the colors without generating or finding an ap…

The Bluetooth integration needs work - missing features such as "never connect automatically."

Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt.

+1 on the gamma controls

Re: Preparing for KDE Plasma's Last X11-Supported Release

#117
post #85

Earlier quoted context omitted.

>> Chrome's PIP is a stupid workaround for Windows and Mac because they do not have robust window management. What are you talking about? It's very convenient when I watch video while I do some work or entertaining thing on other web page or app. It's fine if you don't want to use it but many people do.

Yes, it's fine, but it shouldn't be necessary. If Windows and Mac OS just had native support for always-on-top windows, you wouldn't need it.

I actually prefer macOS's PiP handling compared to other operating systems. In that it's a blessed concept that only goes to one corner of the screen and can be shunted out of the way easily.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#118

As someone who shipped my fair share of critical production features, I find this plan raising my eyebrows somewhat. Disabling a feature AND simultaneously removing the codebase for that feature almost never ends well. There will always be some use cases that people haven't thought of. In serious projects (read, your career is at stake) a much better strategy is to first make the feature unavailable by normal means w…

> a much better strategy is to first make the feature unavailable by normal means

They started doing that in early 2024 with the release of KDE 6.0 by enabling KDE Wayland by default. The Wayland-only change won't happen til 6.8 which will be an early 2027 release.

https://pointieststick.com/2023/11/10/this-week-in-kde-wayla...

> And only then, once we are confident that no massive unforeseen issue has surfaced, can the codebase be removed.

Yes, that's the current step they'll be at with 6.8.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#119
post #40

I've been using Kubuntu for the past 12 years without any X-related issue, and have and am actively working on stuff that requires it. I guess it's time to switch to another DE.

Most people are not you. A small minority do things that really need X. However there is good reason to say that the things that really need X are things you shouldn't do anyway. Meanwhile there is a slightly larger minority that need things that cannot be done in X. For the vast majority of people they cannot tell the difference, either works just fine. If there are issues they are tiny things they don't notice unti…

(?) they didn't say otherwise

Re: Preparing for KDE Plasma's Last X11-Supported Release

#120

in my mind unfortunately this basically destroys KDE's viability as a gaming platform. SO many older games just do not work properly unless run under X11 (hell, some newer ones too). XWayland is good for everyday applications but for games in my experience it too often falls flat.

I was under the impression that the Steam Deck runs under KDE Wayland? I wasn't aware of it having video game support challenges due to Wayland.
Post reply on HN