For many years now KDE has focused on polish, bug fixing and "nice-to-have" improvements rather than major redesigns, and it paid off.
VDG tackled (and tackles) not only design for the desktop itself, but also for KDE applications that had never seen a designer's touch before.
I've been long a KDE user, even through the 4.0 troubles, but also the first to admit that it used to look clunky. Looking at old screenshots is a quick reminder of how far this initiative has taken it.
I love open source and have been running Linux since 1999, but my experience of contributing to both KDE and GNOME is your PRs never go anywhere unless you're part of the inner cabal of maintainers, otherwise any small bugfix or feature goes into bikeshedding mode, and it's the reason I don't contribute any more.
That said, I run KDE now after two decades of GNOME. It's pretty good and has been looking good for a while now.
What's up with the massive amount of chrome used for nothing except new tab/copy/paste buttons? Is it really necessary to take up what could be used for 2+ extra lines of terminal output for a labeled Copy button? Compare it to gnome console, or any other terminal really, and you will get far more terminal output for the size of the window, as it should be.
And it's not just Konsole. So many KDE apps have this same problem. Giant labeled buttons taking up space from the actual content, for things you will never use or have well established keyboard shortcuts already.
https://mero.ng/i/lWMWazUP.png
The screenshot on the website has all sorts of optional bits enabled, and I would readily agree is not a good showcase.
The reason all those optional bits exist is because you'd be surprised who ends up using a terminal emulator in a general purpose desktop GUI used in many large IT deployments. E.g. a lot of folks who are used to PuTTy on Windows and want a little GUI for SSH connections, and for them this is the game changer.
The "try to show all the goods in your screenshot" mindset is really not a good one though, agree :)
This is what I've done since SGI 4DWM Terminal (and ancient NT Command Prompt), and almost all other terminal emulators can be configured to do so. Konsole stands alone (to my knowledge) in its insistence on cruft all over the interface. The terminal widget itself seems fine.
To be clear, I don't mind obscure options, but they should live in the control panel. See my cousin comment for more details.
I don't find that context menu so bad to be honest. If you use it often you should know where things are anyway.
Overall I'm quite surprised at the hate Konsole receives in this HN thread. Removing the toolbars is two clicks away and only needs to be done once. Even the menu bar can be hidden. Such a konsole window would be just the terminal, no cruft, no UI elements. To me we are in the "some people will never be happy for no clear reasons" territory.
I've been using it for years I'm very happy with it. Its search feature is awesome, and its ability to have infinite scroll history is very nice too, it has decent performance.
The one terrible thing I have seen about konsole is that the toolbar buttons were highjacking the keyboard bindings in the terminal, but it was a bug, I think this is now fixed and a workaround was to remove the toolbar.
No other mainstream GUI term has these clutter issues. They are small issues to be sure, but unnecessary.
Folks trying to talk me into a new workflow can’t succeed because I’m multiplatform. Gnome terminal, iTerm2, Win Terminal, etc. konsole is the oddball and least used of the group. Partly because the context menu is a mess.
Bottom line, it doesn’t prevent my workflow.
