Why kde over gnome

If we can run some Windows-based apps on a Linux environment, what could be difficult to achieve this same objective when dealing with apps developed for specific Linux distributions or flavors? Your choice or preference between KDE and GNOME desktop environments should not be about app support but about how easy it is for you to adapt and navigate on either of the Linux-based desktop environments. Save my name, email, and website in this browser for the next time I comment.

Sign in. Forgot your password? Get help. Privacy Policy. Password recovery. Home Reviews. KDE vs. GNOME — everything you need to know.

By Brandon Jones. February 24, Updated: February 24, Related Articles. Comment: Please enter your comment! Latest Articles. Top 9 lightweight web browsers for Linux. How to reset MySQL root password. PostgreSQL vs. Top 10 opensource workflow management software. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

Ettrich chose the Qt framework from Trolltech now the Qt Company to build it, later becoming an employee. Click to enlarge. They get something out of it from us testing all of these obscure cases before they get to their clients.

We gain because we have this rich, very powerful toolkit designed for these industrial applications where they have to care about safety-criticalness. We had Xfce and others coming along, wonderful nerdy tools, but if you want a full featured desktop Plasma is the way to go. Qt offloads more onto the graphics card. The Linux display system, X Server, may be all but abandoned , but its replacement, Wayland, may not be quite ready.

What is the status of Plasma with respect to Wayland? The problem is that Wayland is a moving target. Whole new protocols come in all the time. He instanced the clipboard implementation as an area where new protocols have come in to handle things like clipboard history after you close an application. But the danger is that there are hardware types like Nvidia that may not work so well with Wayland because they are not open source friendly.

Org maintainer Adam Jackson right in saying that the community needs to move more wholeheartedly towards Wayland to get it to a mature state? What about Systemd, another hot topic in the community? Nevertheless, he said that it solves a number of problems. Edmundson posted recently about how Systemd enables management of cgroups, which group processes into units that make sense to the user, such as the application or service to which those processes belong.

It is currently opt-in, off by default. I hope to make it the default where available after more testing and feedback. The team is also seeing increased interest from the far east. Money though is not a pressure at the moment, according to Edmundson. The workflow centers around the Activities Overview , a single location where you can search for files or apps, see open windows, and navigate workspaces.

You zoom into a workspace when you're ready to use an open app, and you zoom back out into the Activities Overview to get a good view of all that you're doing and to start doing something else. GNOME applications do not have minimize or maximize buttons. This minimalism extends throughout much of the design language. GNOME developers subscribe to the view that every extra option or button comes with a cost, to both the developer and the user.

KDE Plasma is arguably the most customizable graphical user interface available for any desktop operating system, period. Without having to install any special software or tweak any lines of code, you can adjust almost every aspect of how your desktop looks. Example tweaks include changing the size and position of your panel, the widgets that appear on the panel or on your desktop, the theme, the buttons that appear in application title bars, fonts, app icons, and app names in the app launchers.

Even basic customizations, such as changing system fonts, require installing the GNOME Tweak Tool, rather than looking in system settings. With these extensions, you can fundamentally change how your desktop works.

If you want the dock to be always visible, there's an extension for that. If you really want to keep a Windows-style workflow, there's an extension for that too. In contrast, KDE bakes add-ons directly into the desktop. You can install themes, wallpapers, desktop effects, and more just by hitting the Get New button that appears throughout the system settings. Customization can be a double-edged sword. The GNOME desktop comes with a greater degree of polish, perhaps in part because it can't be so intricately customized.

The little details matter when users are stuck with them. Adwaita is usually plain and minimalistic to me, although it is very functional and legible, with nothing catching your eye specifically, letting you focus on your work. KDE Plasma has very stable applications, but little choice: since most applications do everything and are extremely configurable, there is little incentive to work on a new project instead of contributing to an existing one.

Default applications can sometimes look dated, without place buttons or widgets and convoluted interfaces. They are powerful, though, and do not lack important features. Once you get familiar with a KDE application, you can pretty much do anything you like. GNOME, on the other hand, has a nice choice of different applications, but they have issues.

Photos are too simple, Music crashed a lot, and Contacts didn't support contact groups. One problem is desktop consistency: since GNOME does away with menu bars, once you install something that does not strictly adhere to GNOME guidelines, it quickly looks out of place and behaves differently. Applications open promptly, and stay snappy, even under load.