Back to article

Mixing Proprietary Software and Linux

Proprietary code on an open platform

June 30, 2009

For most people, computing comes down accomplishing their daily tasks with as much time saved and cost efficiency as possible.

There are also users (such as myself) who want to know that the applications we use are running code that is not locked in by any one company. This gives us freedom of choice.

Where things tend to go wrong, however, is that we do not live in a world where Open Source software and mainstream needs are always on the same page. No matter how much I might wish that everything could just be Open Source, sometimes the issue is a bit more complicated than it seems on the surface.

Proprietary code on an open platform.

Open Source software enthusiasts will tell you that if you open up the proprietary Pandora's box onto an Open Source platform such as desktop Linux, you're playing with fire.

For instance, listening to music. The end user could choose to convert their CD collection to Ogg Vorbis if they want a music jukebox experience on their desktop. And on the video driver front, just how important is that 3D desktop really?

All a person needs to do is use the default video drivers instead of "infecting" their system with problematic proprietary video drivers. Clearly, this is the smoothest approach to a stable desktop Linux experience.

But is this also providing a practical experience as well?

Exploring this further: Let's say you own CDs, have a full understanding of how to rip music from the CDs to Ogg Vorbis or FLAC and have something portable to play your music on that works with Ogg Vorbis. Then you're in good shape.

If, however, you're someone using a Linux distro, own an iPod and have all of your music in iTunes, then going with open formats might not be practical.

While this might sound incredibly trivial to you, realize that for someone who has spent tremendous amounts of money on music locked up in a DRM prison, this really puts a damper on being able to enjoy their media on a Linux desktop.

Then there is also the issue of ease of use. Clearly not being locked into a proprietary application sounds attractive, but is it really easier to convert other people to using the same software you are in order to select Open Source software over that of a proprietary nature?

Is easier truly better?

Skype vs Ekiga - which is actually easier to use?

This is one of my favorite examples of using open vs. closed source software as it hits close to home for me personally. I have been using Ekiga since the days it was known as Gnomemeeting. Ekiga has always served me well as my preferred VoIP client for quite some time now.

However, once Skype came to Linux I found that I was suddenly not using Ekiga as often anymore.

The problem was that Skype has a massive adoption rate among all three major platforms, whereas Ekiga does not. And despite Skype having some issues early on with video, PulseAudio, etc, it's what most people are using for VoIP communications on the other two major platforms these days.

Unfortunately, I found that it takes a bit of research to understand how PulseAudio best works with Skype. Ekiga on the other hand, does a much better job working with PulseAudio out of the box. Yet back on the flip side of the coin, Ekiga's UI is not as familiar as Skype's.

To make matters worse, voicemail was bit confusing for those few users that I did convince to switch over to Ekiga on other platforms.