Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

391–392 of 392 posts

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

#391
post #42

Earlier quoted context omitted.

nmtui

Thanks for the recommendation, but "nmtui" is also the most Linux answer you could have given me :) And it completely misses the point. Yes, there’s a lightweight tool for everything, but the appeal of KDE is that I don’t need to know. It mostly just works, is extendable and configurable. But i also understand the appeal of staying minimal. The thing is, i want some kind of middleground: I want a simple tiling window…

> Maybe it's also brain damage of using too much Windows (with wsl). But there I have a different problem: It's easy to install and configure stuff, but it's everything else than minimal.

You could make your own tiny Windows 'distro' building on Tiny 11.

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

#392
post #347

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.

When switching to Wayland I lost a lot of custom interactions. I’ve learned to live without them but I still miss them. For example I was a big user of devilspie for placing windows in certain locations, on certain desktops, marking windows as sticky, or marking them as different types of windows. I am still a heavy user of pidgin (I know I know but I’ve even written my own protocols for it). I really liked being abl…

What's wrong with Pidgin? Also what protocols have you written?
Post reply on HN