Given the choice between GNOME Shell and KDE Plasma Desktop, I would have traditionally chosen GNOME Shell.
However, these days the only place I rely on GNOME Shell is on my HTPC because the big interface elements lend themselves well to couch-surfing, the GNOME applications are so pared down and simple and because the virtual desktop animation is nice (I've set my system up to autologin to a GNOME Shell session in which Kodi is started in full screen automatically).
My proper Linux desktop PCs are Plasma now and I really like ngraham 's push to get all the papercuts in KDE fixed. The work on achieving gvfs feature parity via kio-fuse in the upcoming Plasma Desktop 5.18 was the clincher for me.
My old must-work-no-matter-what-as-a-backup laptop is MATE with Brisk Menu, which is basically a lightly refreshed GNOME 2 experience. This is a compromise because I need to be able to test the functionally of certain software on all major DEs as part of my maintainer duties.
However, these days the only place I rely on GNOME Shell is on my HTPC because the big interface elements lend themselves well to couch-surfing, the GNOME applications are so pared down and simple and because the virtual desktop animation is nice (I've set my system up to autologin to a GNOME Shell session in which Kodi is started in full screen automatically).
My proper Linux desktop PCs are Plasma now and I really like ngraham 's push to get all the papercuts in KDE fixed. The work on achieving gvfs feature parity via kio-fuse in the upcoming Plasma Desktop 5.18 was the clincher for me.
My old must-work-no-matter-what-as-a-backup laptop is MATE with Brisk Menu, which is basically a lightly refreshed GNOME 2 experience. This is a compromise because I need to be able to test the functionally of certain software on all major DEs as part of my maintainer duties.
Comment