Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

1–10 of 392 posts

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

#2
I think the KDE developers in particular have done a great job of pushing Wayland forward and getting features that people want and need added as new protocols. KDE feels a lot smoother and more responsive when using Wayland than when using X11, and by this point most stuff has been updated to work properly on Wayland so I don't notice any breakage or missing features in day-to-day usage.

> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations, and brand new exciting features throughout Plasma.

I think the blog post would have been better if he had some specific examples in mind that he could have shared here.

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

#7
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.

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

#8
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 is not broken and should not be replaced, but many Wayland's decisions harm user experience more than X11.

Post reply on HN