Kde Is Now My Favorite Desktop
Posted4 months agoActive3 months ago
kokada.devTechstoryHigh profile
supportivepositive
Debate
60/100
KdeLinux Desktop EnvironmentsUser Experience
Key topics
Kde
Linux Desktop Environments
User Experience
The author shares their positive experience with KDE as their favorite desktop environment, sparking a discussion about its strengths, weaknesses, and comparisons with other desktop environments.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
40m
Peak period
138
0-6h
Avg / period
20
Comment distribution160 data points
Loading chart...
Based on 160 loaded comments
Key moments
- 01Story posted
Sep 18, 2025 at 8:17 AM EDT
4 months ago
Step 01 - 02First comment
Sep 18, 2025 at 8:57 AM EDT
40m after posting
Step 02 - 03Peak activity
138 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 22, 2025 at 11:40 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45288690Type: storyLast synced: 11/23/2025, 1:00:33 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I currently use niri but Plasma has always been my go-to/backup DE. I always have it installed in case someone else has to use my PC.
[1]: https://bugs.kde.org/show_bug.cgi?id=433569
Don’t get me wrong, KDE is a nice desktop in many ways, but it would benefit considerably from attention of a professional UI designer.
I know, of course, that it's an extremely minor thing, but it felt quite representative. It also reminded me that Linux is stuck in this bygone age where it's expected for a computer to be a multi-user system, so of course they can't have a "privileged" user account other than root (and god forbid you'd think of using root as your normal every day user).
One of the tricks Debian team does is they first compile the old KDE with newer libraries, then migrate KDE itself, like Intel's Tick Tock. This gives both a performant and issue-free experience as far as I can tell.
Note: I run Debian Testing on my Desktop systems. Servers always run stable.
True, but frankly, KDE team repeatedly said that 4.0 to 4.2 is considered beta, and not production ready. I'm also coming from 3.5.x days, and just waited for KDE to mature a little before jumping 4.x bandwagon, and I'm still on KDE.
Maybe, we, the users shall read the announcements with a keener eye.
It states the following:
Also, IIRC, KDE developers were openly saying that releases from 4.0 to 4.2 will be buggy, and things will stabilize in 4.2 and beyond.[0]: https://community.kde.org/Schedules/Is_KDE_4.1_for_you%3F
That being said: I've been using KDE since the 1.x days, with only a short Ubuntu Unity-intermezzo around the 4.0 release. Most of that time, it's been great!
However I neither have the time, nor the desire to dig these places, yet alone logon to them.
Of course my mind may be lying to me, as well.
Anyway, these days are over and KDE is better than ever, so it’s only nitpicking over some trivia.
It is safe to say that many other projects have not done beta .0 releases like that because they don't want the same to happen to them - even though they really need beta testers. Of course few projects will admit that they learned the lesson from KDE.
Yeah, I remember that turmoil, and was really sad for all KDE devs.
> It is safe to say that many other projects have not done beta .0 releases...
This was a brave move by KDE back then, and still a brave move, but with proper communication, it can be done, I guess...
KDE developers and volunteers embody a great trove of wisdom about software development. I learnt how to make proper bug reporting from AmaroK project, and still use the same methodology, even with projects which do not enforce any style. It makes things much easier. ...and everyone needs beta testers. That's true.
Oh, this is so true. Ubuntu adopted Pulse Audio long before anyone (including Poettering) considered it stable. IIRC the readme even said something like "The sound system that breaks your audio"
I probably shouldn't complain though, since as a non-Ubuntu user, I get the benefits of all the Ubuntu users beta testing software for me.
So I'm not sure whether it's try that that caused a bad reputation that sticks around to this day. (I have other reasons for not preferring it.)
I remember the one that finally made me stop using KDE altogether and migrate to Gnome 3 at the time was one crash that I would get frequently with Dolphin while randomly browsing fils (that would stop once I removed all Dolphin configuration files but go back after a few weeks).
I'm sure if you're missing anything useful diagnostics-wise it's worth a FREQ though. A lot of us also do travel with our laptop to numerous FOSS events all over the place and encounter sub-par networks left and right, after all.
Somehow or another, if you open a file in Dolphin on one of these network addresses in a non-KDE application, it seems to pass it through using a FUSE filesystem, which does work somewhat but not 100% in my experience (I don't really know how this works or remember when it falls down). The terminal view in Dolphin also `cd`s to this virtual directory.
Of course, if you really really wanted the sshfs mount for some reason, then this workaround doesn't help you.
Myself and my family are running Fedora's KDE edition. The Fedora team has a long history of working very closely with the Plasma dev team, quite actively contributes upstream, and I haven't been disappointed. I'd vouch for this one from first-hand experience!
We also have a new project to produce a distro of our own in the works, called KDE Linux. That has recently had its first alpha release. It still has some real feature gaps and may not serve you well if one of the missing bits is something you require, but it's definitely worth looking into. It has a lot of next-gen ideas baked and some things we got to learn during the SteamOS effort, and think it has a place in the ecosystem.
In the dev community I generally see a lot of people running KDE on Arch, Debian and openSUSE as well.
The company stuff in the background doesn't really matter.
The team working on KDE Linux are motivated by addressing some structural challenges that always plagued KDE Neon from the concept of trying to graft more recent SW on top of the Ubuntu LTS base, plus some lessons learned from the SteamOS project's way of handling updates, and fully utilizing more recent Linux/systemd features.
It's sufficiently different that sticking with the Neon brand and swapping it out for that userbase would have been pretty disruptive, so they felt it was better to go with a distinct identity.
I have three observations to make.
1) There is a pain point in KDE involving windows on top of another fullscreen window. Specifically, the Live Captions app. This is a design problem that other OSes like Microsoft Windows doesn't suffer from. What happens is, if you leave the taskbar in place and want to have the captioner running over video and make the video fullscreen, you can't with KDE. I eventually figured out a hacky workaround in that if I turn auto-hide on for the taskbar, I can then alt-tab the Window and it'll stay on top. I did see some talk about this window behaviour. It's nuts that an accessibility feature needs the user to make the taskbar auto-hide first before it works. It would be nice if there could be a setting where it is "this window is on top of everything".
2) SteamOS as having a large device-specific installed base, I think there is value in the KDE team encouraging Valve to turn KDE from a snapshot to a rolling release as Fedora has done where KDE is rolling but the rest of the distro is a snapshot. Why this matters, is because when it comes to bug reports and the like, the KDE bot basically closes them because Valve's KDE is "unsupported" because they only seem to rebase once a year or two. I know they did move to 6.2 with 3.7, but I found 3.7 buggy and thought KDE looked worse and had worse scrolling performance (maybe setting conflicts from the 5.27 version?) so I just switched back to the 3.6 version with 5.27 where everything looks right and scrolling moved smoothly. I know they changed the kwin compositor a lot in the 6.x series, and I suspect there are regressions in it, so if it isn't rolling, people are stuck with a buggy compositor? That sucks.
3) Setting upgrades.. so with SteamOS, Valve was shipping the 5.2x series of KDE. Now 6.2, and the next rebase is probably going to be 6.x on Wayland instead of X11. So there's a lot of legacy cruft settings that carry on and I think they cause glitches. I always used to do clean install of Windows versions, and think it would be nice to be able to do that in KDE, but there's a lot of legacy cruft with various settings and conf files scattered in various random folders. At some point it really should be cleaned up.. one central folder for all settings.. no some settings are stored in a KDE4 folder, and others are stored in this other one KDE5 introduced, etc.
Personally I've had an issue with KDE on Fedora several years ago, possibly due unstable Wayland, but I don't know real reason. Something in the graphic stack failed. So that was a reason for me asking about it.
Something I use a lot on xfce4 is the Alt-F11 shortcut (it toggles) that maximises a window over the bottom bar and removes the title bar.
In this way, with LibreOffice or say Inkscape I get the application menus at the top and the applications controls at the bottom of the screen. No hotspots - nothing pops up.
On Fedora's live KDE iso I can use the window control menu to supress the title bar on a maximised window and I can hide the bottom bar but its a faff requiring multiple steps.
edit: According to AI, LTS is not provided. Was my AI answer accurate, and if so is there consideration of an initiative to implement an LTS channel?
We did in fact have versions marked as LTS in the Plasma 5.x generation, but the concept never quite worked that well practice (e.g. because distros generally shipped newer versions based on user demand and didn't really adopt the LTS releases, even for their own LTS distro releases, so the benefit calculation for them was different from your expectation) and we haven't kept them for the Plasma 6.x series. You can read some background here:
https://pointieststick.com/2025/05/01/notes-from-the-graz-pl...
It might come back some day in some form, but the discussion is ongoing.
How can we make this happen? I am a programmer but I am not in a good position to do this specific kind of programming myself. This seems tightly integrated to a lot of stuff I don't have a good understanding of. Is there a way to donate to specific features, could I do some crowdfunding to hire a dev to do this feature and if so who? Is there any way at all you can think of that I could effect this feature landing other than spending a few years learning this kind of development?
- X11 is nearing EOL, and once we drop support for it this will get a lot less painful to do.
- If we want to switch to a virtual desktop / paging protocol that supports this we need to switch away from the current one, and it just so happens that in late 2024 a new protocol called ext-workspace made it into Wayland that is flexible enough to work for this purpose.
I'd say at this point the biggest problem is designing a UX for it that makes sense and doesn't confuse the hell out of people. If you want to contribute to e.g. that design discussion in our VDG working group that could be a good place to start.
> could I do some crowdfunding to hire a dev to do this feature and if so who?
Someone else has pledged a bounty:
https://discuss.kde.org/t/bug-fix-per-screen-virtual-desktop...
Right now I have the TV disabled, but if I go to the Display settings and enable it, the TV and monitor have a huge gap for some reason and KDE can't apply the configuration since it says that there should be no gap between the displays. I can of course fix this manually and apply, but if I disable and enable the TV again it seems that it forgots my layout and I need to setup everything from scratch again.
But anyway, thanks for the fantastic work!
> However, KDE considered my TV the primary desktop and put the task bar only in that monitor, and even disabling the TV didn't add the task bar to my monitor.
You can order the screens however you want; the first one will be considered primary.
I have a LG TV C1 that behaves like that. While my computer monitors do not have this issue.
The TV even has a dual personality. It doesn't appear to report the same informations via EBID when powered off vs powered on.
I also have a MS Windows 10 connected to this same TV, and if I make the mistake of powering up or wake from sleep Windows before turning on the TV, then the NVIDIA GPU setup some broken resolution. And only a reboot fixes it.
So my guess is it's the TV presenting itself with different EBID when off vs powered on. And also somehow presenting itself as active on the HDMI line no matter if off or on. Changing the TV inputs also doesn't tell KDE that the display was turned off.
I haven't debugged any of it. These are just my observations.
I always want the taskbar on every screen personally. I think that'd be a friendlier default, but since it's KDE it's at least not too hard to change, and everything is configurable down to fine details
It selects the first screen just as a default.
E.g. the machine we optimized for during at least one or two Plasma dev meetings I remember was the original Pine64 Pinebook, which was a very under-powered device. We had a stack of them to hand to devs. Intentionally as a "if we can get it to fly there, it'll fly anywhere".
So it's not just that we haven't gotten worse, we also did get legitimately better in later releases compared to some of our porkier ones (which also did exist).
Everything is sooo small on my 16" notebook and when I zoom it gets blurry.
My goal was to have my own setup without "bloat" I never used. So my own task manager of choice, my search bar of choice, etc.
My initial impression of xfce was that it was much snappier than kde. My main gripe with xfce was the lack of wayland support.
A big personal issue; while my own custom setup was ok, I still had to maintain it, and I found myself trying to make xfce like kde. So might as well use kde I guess.
Another super specifc thing I missed was that its window manager didn't support defining horizontal gradients in the titlebar, so I couldn't rock a true windows classic theme. It could do vertical gradients, but that's not the same.
Now I'm back to using KDE.
I switched from X11 and LXDE to Sway and had a good experience. But Sway was my slippery slope to labwc.
https://github.com/labwc/labwc
I actualy liked Ubuntu's Unity, and the move to GNOME did not made me an happy user.
As someone that used Gtkmm during the GNOME 1.0 days, the way current GNOME works and the overuse of JavaScript made me look elsewhere.
XFCE was good enough for me (I am old enough to have used twm), and looks rather nice.
Seriously though, the fact that macOS still doesn't have an option to fully extend the dock horizontally or vertically drives me nuts. If you auto hide the dock it loses half of its value, and if you don't hide the dock then you have dead gaps in the corners that serve no purpose.
But I'm worried we're being left behind with the shift to Wayland.
Maybe that is unfounded.
It has become more memory-hungry since then, losing some of its early advantage. And with the move to Gtk 3, it has adopted UI patterns that constantly get in my way. (Client-side window decorations, for example.) I worked around those changes as best I could for several minor versions, but eventually gave up the fight and switched to KDE. Turns out Plasma slimmed down a bit while Xfce was gaining weight, and it lets me turn off the bells and whistles that I don't want.
I'm happy to once again have a desktop that I enjoy using. I do miss Xfce's Thunar, but KDE's Dolphin is mostly not bad.
https://github.com/labwc/labwc
I'm concerned about the XFCE team's approach to Wayland, which is to say they are not making any commitments to make a stable release for it. I've already had to take my new Debian install back to X11 to get XFCE working. I know that Wayland is contentious and not developed with clear communication with many DE teams, but the drift here is concerning, and I am considering trying to find something XFCE-like with full Wayland support.
XFCE isn’t as polished as KDE, and I do miss some features, like KDE’s excellent network applet that shows detailed statistics. But overall, the experience has been good, and I really appreciate how quickly I can unlock the screen after a pause.
I also enjoy the wide variety of themes. KDE has plenty of impressive dark themes, but very few light ones, and most of those fail to clearly differentiate the active window’s title bar from inactive ones. XFCE does much better here.
(Some people point out that XFCE doesn’t work with Wayland. That’s not an issue for me. My time with Wayland was highly frustrating, primarily due to the unreliability of keyboard layout customization. After months of struggling, I went back to Xorg and good old xmodmap.)
Though, my monitors are also from 2010, so a lot of the visual problems people have with XFCE, I don't.
I'm keeping an eye on XFCE and they plan to release Wayland support some time this autumn. Once this is somewhere near stable, I thin I will switch back again to XFCE.
For a daily drive DE though, it may be too minimal?
The only desktops I've used since 2007 are XFCE and macOS, so I guess I don't know what I might be missing from KDE or MATE. But XFCE absolutely blows macOS out of the water, so at least I'm not missing anything from that alternative.
I get the idea of a desktop environment offering more consistency. But, my system feels very consistent. It is really easy, because there are only ~4 types of windows: Firefox, Evince, a terminal, or some ephemeral matplotlib graph.
I wouldn’t think of it as missing out on anything. You just become familiar with the ecosystem of mostly terminal utilities.
I run KDE Plasma on my laptop. KDE animations are too bloated and heavy for the Rock64, and there's way too many preferences to fiddle with to disable them all. If there was some kind of global "lightweight mode" checkbox in the plasma prefs, I might give it another try.
LxQT is fine. The main gripe I have with it is there's no sort of LxQT-meta package on ArchLinux which installs everything I actually need without a lot of fiddling. I spent a couple weeks just gradually figuring out things were missing that would make the environment a lot better. It would be nice if it just included things like oxygen icons and whatever. I understand lightweight, but they should have an "opinionated" lightweight option since I just want something that runs well on a SBC.
I used to run XFCE on an arm chromebook for a few years as my daily driver. Between the two, XFCE seemed much easier to install/customize. IDK about now, since that was before the latest release which uses latest GTK. I assume it is less lightweight now as a result of that change.
It lacks tiling, and I use some KDE apps very heavily (Kate, Dolphin) so KDE integrates a bit better.
I have thought of giving XFCE another go and I do not think there is anything critical I would miss if I had a tiling window manager (which would have some advantages over KDE's tiling, I think), but I have KDE configured in a way that works for me so not very motivated to do it.
What kinds of things are you talking about?
These days I feel like all of the major desktop environments are good enough. 95% of what I do with them is launch applications and move or resize windows and that’s easy enough on all of them.
On windows you have to click the icon before you can interact with it. IIRC on Mac too.
Not anymore! This changed in some win11 update I can't remember, but I recall celebrating this improvement.
However, this being windows, of course it's half-assed. This works with the mouse wheel but not by scrolling the touchpad (as of up-to-date 24h2).
I've used a variety of environments extensively (Windows, macOS, KDE, GNOME, Xfce, i3, dwm, you name it) and this is basically the one feature I find myself regularly missing from another environment.
Can you explain more about this?
You can also use links between most apps, documented here: https://github.com/bhagyas/app-urls
And drag and drop files and stuff onto and between apps, etc.
Give example.
> Another is things in OS X, such as deep Spotlight integration with apps, and a unified scripting and automation language between apps.
I am sure KDE has it too.
One time I needed a shortcut for concat-ing 2 images, and I was able to get the son-of-a-bot Gemini to script me a .Desktop file + .sh script which added it as a context menu option to Dolphin. I didn't even know it was possible. I am sure even more automation should be possible with D-bus.
> You can also use links between most apps
Android has this, and I think it can cause borderline security risks. Anyway its' not as important these days when everything that could use a deep link from another app is a react app in browser anyway.
> And drag and drop files and stuff onto and between apps, etc.
I need it maybe 2 - 3 times a day. I can always use Paths and paste them in the file picker. Its never a deal breaker.
On my work macbook - I can't install third-party software and the default window management is just not there. It has problems restoring windows to correct size when i switch external monitors... The experience just isn't as nice as KDE on my home laptop.
I had to install inputactions to get mac like touchpad gestures on my home kde set up but after that it just feels nicer and smoother than my office mac
But that doesn't work anymore since a while (I guess due to SIP).
I reciprocate their comment; 5-10 years ago the cross-OS experience was pretty samey. Now I just feel deeply upset when a relative brings me their Mac/Windows machine asking to make the popups go away.
Wow! (about) A whole week!
I am using it in my main machine now for almost 2 weeks, and this is the period of time that this blog post refers too.
So, I gave up and just use Windows for gaming. Sigh.
I'm not going to change the type of gamer I am just for an OS.
Could easily make the argument you are doing that for windows currently
Edit: Why someone downvotes the most innovative CD ripping solution on the planet is beyond me. =)
Encoding and tagging can be configured in System Settings directly.
In short, it's neat.
https://arcan-fe.com/2017/12/24/crash-resilient-wayland-comp...
These days, I daily drive Niri and love it. I love the workflow of a scrolling WM. I love that I can configure it via a single text file in the standard configuration directory, I love how lightweight it is. It’s just about perfect for me.
But enough about Mac OS Tahoe!
Apple should at once hire the people who are responsible for Gnome's UI, because they've got it figured out. Even better, put back together the Nokia N9 GUI team.
There's many things to not like with Gnome, but they've got the user interface figured out. Contrast is correct both in light mode and dark mode. Readability is excellent. Margins and paddings are consistent across the board. Buttons, checkboxes and other gizmos look exactly as they should, with subtle shadows and 3D effects. Border radiuses are consistent and not to large.
Icons are not great, but that's the same on all desktop environments now. OS X had great icons, but that age is over.
And since they have all the important basics correct, it is trivial to fix any short comings in the UI. The team deserves praise for what they've achieved.
You're sabotaging hard your own messaging with comments like this.
There are many cruel and pugnacious creatures here.
Indeed, it's best to remain indifferent, lest... behavioral modification ensue, and one become strange.
macOS is nearly the opposite in this regard. I wouldn’t mind giving it a facelift but doing it GNOME style would mean it losing much of what has kept many users on it.
Often it functions as a “do this for everything” modifier. So for example, option-clicking the minimize traffic light minimizes all windows from the application the window belongs to, and option-clicking a disclosure triangle in a nested list expands or contracts all child nodes.
There’s tons of little things like that which might sound silly but become significant time and sanity savers after making a habit of using them.
Missed opportunity for "comparing apples and penguins!"
582 more comments available on Hacker News