Language Selection

English French German Italian Portuguese Spanish

Basic Overview of Differences Between Gnome and KDE

Filed under
Software

In one my previous posts, I went over some of the basics of Linux. One of the major aspects I discussed was the difficulty in choosing which desktop environment you would like to use. The two most popular choices are Gnome and KDE. Both desktop environments offer great functionality and by most accounts they are very similar. For anyone new to Linux, the subtle differences are not clear. I thought it would be good to list three of the primary along with the perceived differences of Gnome and KDE for new Linux users.

The first and most obvious differences fall in the aesthetic area. The differences in aesthetics can easily (and most often) be changed by any user. The easiest way to overview these is by using each desktop environment's default settings. All of the comparisons below are using the default settings after installation. For this and all of the comparisons, I have used the Ubuntu and Kubuntu Linux distributions.

Aesthetics in desktop environments most commonly start with color schemes.

More Here




More in Tux Machines

OSS Leftovers

  • Comment: Many happy returns to open source
    Twenty years ago the phrase “open source” was first used and the development of software – and hardware – was changed forever. Very few designers today will not use some element of open source software in their development projects.
  • Percona Unveils Full Conference Session Schedule for the Annual Percona Live Open Source Database Conference 2018
  • Worth seeing in Barcelona: Open source for white box vRAN solutions
    News this week from cloud and carrier infrastructure platform company Kontron builds on our earlier coverage of the emerging virtual radio access network (vRAN); a promising technology that could help the evolution to 5G by maximising available bandwidth while lowering costs. The market for open vRAN solutions is gaining wider acceptance as operators seek more cost-effective approaches to network architectures and deployment. According to analyst firm Research and Markets, the growth of the vRAN market is expected to grow at a CAGR of approximately 125 per cent during the next three years.
  • Barcelona is the first city council to join the FSFE's "Public Money? Public Code!" campaign
  • Earlham Institute releases open source software to help identify gene families
    Researchers at Earlham Institute (EI) have released ‘GeneSeqToFamily’, an open-source Galaxy workflow that helps scientists to find gene families based on the ‘EnsemblCompara GeneTrees’ pipeline. Published in Gigascience, the open source Galaxy workflow aims to make researchers job of finding find gene families much easier.
  • 3 reasons to say 'no' in DevOps
    DevOps, it has often been pointed out, is a culture that emphasizes mutual respect, cooperation, continual improvement, and aligning responsibility with authority. Instead of saying no, it may be helpful to take a hint from improv comedy and say, "Yes, and..." or "Yes, but...". This opens the request from the binary nature of "yes" and "no" toward having a nuanced discussion around priority, capacity, and responsibility.
  • 5 rules for having genuine community relationships
    As I wrote in the first article of this three-part series on the power and importance of communities, building a community of passionate and committed members is difficult. When we launched the NethServer community, we realized early that to play the open source game, we needed to follow the open source rules. No shortcuts. We realized we had to convert the company in an open organization and start to work out in the open.
  •  
  • Rust Typestates
    A long time ago, the Rust language was a language with typestate. Officially, typestates were dropped long before Rust 1.0. In this entry, I’ll get you in on the worst kept secret of the Rust community: Rust still has typestates.
  • It's Time To Do CMake Right
    Not so long ago I got the task of rethinking our build system. The idea was to evaluate existing components, dependencies, but most importantly, to establish a superior design by making use of modern CMake features and paradigms. Most people I know would have avoided such enterprise at all costs, but there is something about writing find modules that makes my brain release endorphins. I thought I was up for an amusing ride. Boy was I wrong.

OpenBSD Gets Mitigated For Meltdown CPU Vulnerability

  • OpenBSD Gets Mitigated For Meltdown CPU Vulnerability
    A few days back FreeBSD 11 stable was mitigated for Meltdown (and Spectre vulnerabilities), which came more than one month after these nasty CPU vulnerabilities were disclosed while DragonFlyBSD was quickly mitigated and the first of the BSDs to do so. While OpenBSD is known for its security features and focus, only today did it land its initial Meltdown mitigation.
  • Meltdown fix committed by guenther@

    Meltdown mitigation is coming to OpenBSD. Philip Guenther (guenther@) has just committed a diff that implements a new mitigation technique to OpenBSD: Separation of page tables for kernel and userland. This fixes the Meltdown problems that affect most CPUs from Intel. Both Philip and Mike Larkin (mlarkin@) spent a lot of time implementing this solution, talking to various people from other projects on best approaches.

    In the commit message, Philip briefly describes the implementation [...]

France Proposes Software Security Liability For Manufacturers, Open Source As Support Ends

It sometimes seems as though barely a week can go by without yet another major software-related hardware vulnerability story. As manufacturers grapple with the demands of no longer building simple appliances but instead supplying them containing software that may expose itself to the world over the Internet, we see devices shipped with insecure firmware and little care for its support or updating after the sale. The French government have a proposal to address this problem that may be of interest to our community, to make manufacturers liable for the security of a product while it is on the market, and with the possibility of requiring its software to be made open-source at end-of-life. In the first instance it can only be a good thing for device security to be put at the top of a manufacturer’s agenda, and in the second the ready availability of source code would present reverse engineers with a bonanza. Read more

today's howtos