Language Selection

English French German Italian Portuguese Spanish

Linux for a new user: Gnome or KDE?

Filed under
KDE
Software

So now that I have decided I’ll install Arch on Jen’s laptop, what DE should I install with it? I know I said I wanted to use KDE 4.2.1 (and I still do), but I’ve been thinking. Unfortunately. There’s a lot to be said for both of them.

Why KDE?

One of the main selling points of the KDE4 release is, undoubtedly, looks. Microsoft and Apple are really sexy-fying their OS, and KDE4 now looks just as good. Just look at these screenshots.

This is how the latest build of Windows 7 looks out of the box:

Now, you may argue about the quality of the OS, or non-free software, and I’d agree, but damn if that doesn’t look great.

Let’s have a look at the latest OS X (Leopard):

That’s polished, shiny, and professional. I don’t think Macs offer enough value for money, but Apple knows what’s beautiful and what’s not.

So how does KDE 4.2.1 measure up?




More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.