Installed apps and running instances of installed apps are different concepts, damnit, and I don't need a phone-like interface that fakes the idea that all apps are "always running" when they are not.
KDE user here. What you say is false. Xfce is quite primitive in comparison, it has a miniscule amount of features and hence gets away with using less memory. Observational data:
3570M kwin_x11 (window manager)
2512M plasmashell (task panel)
1411M krunner (application launcher)
895M kded5 (?)
532M kactivitymanagerd (multiple desktops)
422M polkit-kde-authentication-agent-1 (?)
389M org_kde_powerdevil (energy settings)
352M kdeconnectd (use mobile phone as remote control)
220M xembedsniproxy (make tray icons work)
277M kaccess (accessibility keys?)
277M ksmserver (?)
276M plasma-browser-integration-host (Firefox can show desktop notifications)
276M kwalletd (password manager)
265M klauncher (?)
265M kglobalaccel5 (global keyboard combos)
213M kscreen_backend_launcher (changing screen orientation and resolution?)
153M kio_http_cache_cleaner (?)
101M kdeinit5 (?)
101M file.so [kdeinit5] file local:/run/user/1000/klauncherXHvFxc.1.slave-socket (?)
69M kdesud (caches sudo password)
7M xsettingsd (apply colour scheme to Gnome applications)
2M start_kdeinit (?)
On top of that, some applications for comparison: 2805M ktorrent (file sharing)
694M konsole (terminal)
402M kate (text editor)
---- 570M xfce4-appfinder
332M tumblerd (makes thumbnail images)
331M Thunar (file manager)
283M xfdesktop
266M xfce4-panel
260M xfce4-session
251M xfce4-notifyd
223M xfconfd
220M xfwm4
205M xfce4-screensaver
190M xfsettingsd
188M wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libactions.so
186M wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libsystray.so
179M xfce4-power-manager
On top of that, some applications for comparison: 411M mousepad (text editor)
363M xfce4-terminal (terminal)
----KDE really has become very bloated. First of all, I cannot uninstall any part of that huge list with the exception of kdeconnectd (don't want/need) or plasma-browser-integration-host (maybe want/need); AFAICT this problem is existing, but not at all pronounced in Xfce.
Due to lazy design choices by the responsible programmers, KDE fails to scale properly down to the user's circumstances or preferences.
• I do not have multiple desktops configured, yet I must spend 532M
• My computer chassis only has a power button that does something in the desktop environment when triggered, and any power saving settings are off, yet I must spend 389M for that
• I do not have any of the five accessibility features enabled, yet I must spend 277M
• I have only one monitor attached, yet I must spend 213M listening for an additional
Then there are many initialisation processes hanging around after the desktop environment has already started. Xfce does not have this problem.
A lot of the processes I cannot even identify in the sense of telling what use they are to me.
Some processes exist only due to their own doing where the responsible programmers painted themselves into a corner (like with the tray icons fiasco), or no one competent stepped in and stopped the submission of a solution that has a simple and superior equivalent.
• Why is there a 153M cache cleaner hanging around resident in memory? This is a job for periodic timer (cron/systemd). Even if real-time cleaning is needed for some bizarre reason, then one would attach an inotify listener to the cache directory, and every time a file is added or changed, a small <1M process executes that calculates the diskspace in use, and only when we are over the threshold, then execute the big cleaning process. Exit the process when done.
• Why is there a daemon for applying the colour scheme? I mean, it's only 7M, but this used to be a checkbox in the settings dialogue.
Virtual memory[1] is not at all the same thing as resident memory[2].
I've experienced similar amounts of memory usage to the stats in this article when it comes to KDE vs Xfce memory usage[3].
[1] https://linuxconfig.org/ps-output-difference-between-vsz-vs-...
[2] https://en.wikipedia.org/wiki/Resident_set_size
[3] https://www.forbes.com/sites/jasonevangelho/2019/10/23/bold-...
That does not change anything in the conclusion.
685M kwin_x11
417M plasmashell
161M krunner
74820k kded5
58612k kdeconnectd
53368k polkit-kde-authentication-agent-1
52460k ksmserver
50364k kaccess
49488k plasma-browser-integration-host
48568k kwalletd
44268k kglobalaccel5
44044k org_kde_powerdevil
44020k klauncher
40384k kactivitymanagerd
26068k kdeinit5
24432k xembedsniproxy
21508k kscreen_backend_launcher
18964k file.so [kdeinit5] file local:/run/user/1000/klauncherwpWDlK.1.slave-socket
11672k kio_http_cache_cleaner
3984k kdesud
3652k xsettingsd
96k start_kdeinit
144M kate
96464k konsole
---- 73828k xfdesktop
59788k xfwm4
44508k xfce4-screensaver
38552k xfce4-appfinder
36260k xfce4-panel
29392k xfce4-session
29216k wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libactions.so
27156k wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libsystray.so
27064k Thunar
25284k xfsettingsd
25284k xfsettingsd
25140k tumblerd
17656k xfce4-notifyd
15248k xfce4-power-manager
5880k xfconfd
54492k mousepad
51244k xfce4-terminal
The findings from the article are non-reproducible, too. When I run the desktop environments with a text editor and terminal each, `free -h` reports a clear difference in the "used" column: KDE 5.19.4: 1.2Gi
Xfce 4.14.5: 521Mi2. You can disable that feature and use old-style taskbar. In fact it's a prominent toggle in the first-run config window.
Gnome is so smooth on Nvidia in comparison but in every other way I prefer and still use cinnamon
Unfortunately not. Muffin, the compositor is based on a really old version of Mutter, and it’s missing a lot of performance work and fixes that make latency lower and output less likely to hitch, hidpi works better, etc. They need to just drop their fork and use the upstream version. They haven’t added anything significant to Muffin to justify keeping it—-the differences to gnome are done with other packages.
I user Gnome on Nvidia, but use the open drivers since Nvidia was difficult to get to a stable state.
Did you just install the nvidia drivers from your OS's repo or get them directly from Nvidia?
NB: The free drivers are working splendidly by the way
After going back to mac (for work reasons), It's been a painful experience adjusting to the lack of tiling.
Same situation, I use ‘yabai’ on macos, which is similar enough to i3 for me.
Yabai is actually the second iteration of tiling windows that koekeishiya has made and it's super well developed.
https://github.com/kasper/phoenix/
I hacked something together several+ years ago (see below) based on someone else's config, and I've maybe edited it twice since then, so it likely can be substantially improved. Also, I'm sure it's not as slick as a true tiling manager, but I've certainly gotten a lot of mileage out of it:
https://gist.github.com/michaelsbradleyjr/a8ef81982420d06118...
You’ll probably use 100% scaling?
My approach is to use the window manager best suited for the task, but all at the same time.
That means for my highly structured multi-desktop, multi-git-workspace programming tasks I use i3, which is ideal for those.
However for my less structured tasks like writing or consuming documentation, email, and personal web browsing, I use a more conventional, less constrained desktop environment (i.e gnome), which is more ideally suited for those tasks.
If I'm willing to abuse the term window manager a little further, Vim running inside i3 serves as a third window management environment I run in parallel, optimized specifically for code editing.
The trick is that I use i3 in its own separate Linux desktop window (In my case running on a remote machine, but you could just as well do this running in a local VM). this allows me to have both environment successful on the same screen at the same time.
This also has the added benefit of making it very easy to find my code editing window among the tons of other windows I have open.
So: just like the site says. Top is the taskbar, which also has a left icon for the current tiling pattern (fullscreen, tiled vertically, etc). The left side panel starts at the top-left with the search button that does the Gnome activities overlay, then a globe icon for each workspace, and a button to create a new workspace. At the bottom of the left panel are the system icons (normally in the upper right in Gnome) and then the clock, crammed into bottom-left.
So I don't hate the tiling, and one of the layout options is "floating" so you can have a workspace full of floating windows. Cool.
My first thought was that the panels are too big -- 48px, which seemed overly large. Luckily this is easily configurable in the extension settings, and updates as you change it so there's no guesswork.
If I switch to floating, or a new workspace, I appear to have no wallpaper behind the windows or the "new workspace" launcher. I liked my wallpaper, and I miss it.
I was going to complain about the globe icons for the workspaces, but it turns out it only preselected those icons because I have browsers primarily in each workspace. It'll pick based on the first open app (I think?) or you can override the icon by right-clicking, or have it display a group of app icons for the open apps in that workspace. This is cool! It's not quite the thumbnail previews of virtual desktops I had in 2004 with Openbox, but It works well.
I'll keep on this for a little while -- I really like that I can turn the whole shebang on and off with a single extension toggle.