Download the authoritative guide: Cloud Computing 2018: Using the Cloud to Transform Your Business
By now, you'd think that anyone who owns a computer knows about free and open source software (FOSS). However, once you move beyond techie circles, you'll find that, for many people, the concept is unknown. Even worse, when people have heard of it, they have alarming -- and rather discouraging -- misconceptions of what it involves.
Here are the twelve most common misconceptions of FOSS, and why they're distorted, exaggerated, outdated, or just plain wrong:
1) If software costs nothing, it's no good
Technological culture is so influenced by business logic that most of us believe that "you get what you pay for" is common sense. However, when you only look at proprietary software, that adage isn't true. If price really reflects quality, then Adobe Creative Suite would be six times better than Xara Xtreme.
2) FOSS is inferior to proprietary software
This idea may have had some truth twenty years ago, when FOSS was just getting started, and needed a lot of development to catch up with existing proprietary programs. And you can still find areas today, like OCR scanning, where FOSS is inferior in functionality or usability to its proprietary equivalents.
However, if you compare the most common programs -- for instance, Firefox to Internet Explorer, or OpenOffice.org to MS Office -- the idea quickly becomes indefensible. While you can quibble over a feature here or there, in general, the leading FOSS programs are a close match for their proprietary equivalents.
3) FOSS is piracy (or at least encourages it)
Actually, since FOSS licenses permit copying and redistribution, the concept of piracy is irrelevant to it. You can't pirate what the copyright holder encourages you to give away. Moreover, when the few restrictions to copying in FOSS licensing are violated, such as the preservation of the original creator's credit, many holders of FOSS copyright are prosecuting the violators as fiercely as proprietary software vendors do pirates. For instances, the Busybox project has brought legal action against several violators of its license in the last year.
True, many FOSS supporters would like to see a world where proprietary software doesn't exist, so you can easily imagine that some might use that ideal as an excuse to ignore proprietary licenses. But since most FOSS supporters either use proprietary software reluctantly or refuse to use it all, such cases are hardly the norm.
4) FOSS has no support
Selling support and related services is how many FOSS-based companies like Red Hat make a profit. But, even if you don't want to pay for support, most FOSS has mail forums in which you can receive free help -- often as quickly as you can from a commercial company. If anything, the problem is not getting help so much as being deluged by suggestions from helpful volunteers.
5) FOSS is only for developers
FOSS has always been centered on developers, who invented it and continue to sustain it. Especially in the early history of FOSS, this orientation meant that little attention was paid to usability. But, as the popularity of FOSS has spread, artists, technical writers, and usability experts have also been attracted to the community. For the last decade now, usability has been an important aspect of FOSS development, and now the leading programs are as easy to use as the leading proprietary ones.
As FOSS continues to spread, the attention to usability can only increase. Recently, for example, Mark Shuttleworth, the leader of the Ubuntu distribution of GNU/Linux, has challenged project members to exceed OS X in usability in the coming years.
6) Using FOSS means working from the command line
This idea is one of the most persistent about FOSS. It only shows the power of rumor, because FOSS operating systems have had usable graphical desktops for well over a decade. Until the last few years, they weren't as advanced as Windows or OS X desktops, but they were adequate. Now, FOSS operating systems give you the choice of working with the command line, several types of lightweight graphical interfaces, or full-featured desktops.
Admittedly, for some advanced administration work, the command line still has the most advanced tools. But that is also true in Windows, as anyone who has used ipconfig to trouble-shoot an Internet connection can testify.
7) FOSS is only good for small projects
FOSS developers have inherited the Unix preference for small programs of limited functionality. And it is true that several large FOSS projects, such as OpenOffice.org and Java, were developed privately and later had the code released.
All the same, FOSS has no shortage of large-scale projects, ranging from the GIMP, a PhotoShop equivalent to Scribus, a desktop publishing program, and Inkscape, a vector graphics program. Desktops like Xfce are even larger projects, while GNU/Linux distributions like Ubuntu are larger yet, involving thousands of applications. Such examples make clear that FOSS is perfectly capable of scaling as necessary.
8) FOSS is unable to develop games
This misconception is perhaps a sub-set of the idea that FOSS can't develop large pieces of software. It gains added credibility because, for a long time, games were a low priority; FOSS developers were too busy with basic functionality and productivity to pay much attention to large-scale games. For a long time, FOSS games were confined to card games and simple strategy games, many of them based on arcade games.
Now, FOSS continues to be weak in 3-D games, partly, no doubt, because of its lack of free 3-D video drivers. However, a few large games like Battle of Wesnoth are now available, and most online games have GNU/Linux clients as a matter of course.
9) Having the code freely available makes it less secure than proprietary code
For those new to security, the idea that the best way to keep something safe is to hide it. This idea is known by experts as security through obscurity, and is generally discredited.
Probably the greatest reason that security through obscurity doesn't work when it comes to code is that, if security is breached, you have no way of knowing what has happened. By contrast, if the code is open to anyone to read, then the odds are that the insecure elements will be detected and corrected. Since what you want to protect is the information, not the technique used to protect it, according to most security experts, FOSS tends to be more secure than proprietary software.
Of course, because bug detection is public, detractors can say that FOSS is buggier than proprietary software. However, because we have no way of knowing how many bugs in proprietary software go unfixed or unnoticed, the number of reported bugs is not a reliable measure of security.
10) FOSS is unable to innovate
When FOSS got strongly under way in the 1990s, proprietary software had almost two decades' head start. Under these conditions, for a long time, FOSS development focused on catching up with proprietary software. Also, the standards for usability were developed for proprietary software, so FOSS often seemed to be imitating its rivals, especially since one school of thought held that, to attract users, FOSS needed to resemble as closely as possible what users were familiar with.
Yet, even while the goal was equivalent functionality, FOSS never lacked for innovation. Both the GNOME and KDE desktops, for example, allow a degree of customization unheard of on the Windows desktop, to say nothing of standard features such as virtual desktops. And now, with the release of KDE 4.1, some developers maintain that the FOSS desktop has surpassed proprietary ones, and is now setting the pace for innovation.
Similarly, FOSS has caused a revolution in business, showing that companies can be successful by selling services rather the software itself. You might say that the very idea of FOSS is a major innovation -- to say nothing of the communal organization in which FOSS development takes place.
11) Since the license places restrictions on the users, FOSS isn't really free
The truth is, proprietary licenses restrict users far more than any FOSS license. If you read the typical end-user license agreement closely, you find that you don't even own the software that you buy. What you have purchased is a license to use, and that license severely limits the number of computers you can install it on and your ability to work with the code.
By contrast, FOSS licenses give you a right to the source code and to use it more or less how you want. Such restrictions as they include, such as preserving copyright notices, fall upon distributors more than users. BSD-style licenses are so permissive that you can even incorporate the code into proprietary code.
Copyleft licenses are more restrictive, in that they insist that, if you distribute the software, you do so without changing the license. However, that restriction simply means that you pass along the same rights that you have in the software to anyone who receives a copy from you. Compared to proprietary licenses' terms, this is a minor restriction, and justified by the theory that the only way to ensure your own freedom is to ensure everybody's freedom.
12) FOSS is all about price
The fact that FOSS is often free for the downloading is often what attracts people to it. However, if the lack of cost was a primary motivation for using FOSS, then it would probably be no more popular than shareware.
Those who stay with FOSS usually do so for one of two reasons. For free software supporters, the reason is that they wish to control their computers and what they do with them, rather than allowing a company to exercise that control. For open source supporters, the reason is that freely available source code is an extension of the academic free exchange of ideas, which they believe results in better quality software. In both these cases, it is idealism, not price, that makes FOSS attractive.
Anything said often enough takes on a life of its own. And, because FOSS is relatively unknown and is different from the proprietary norm, it is likely to continue to attract rumors and half-truths. For these reasons, while the myths above are easy to debunk, I don't imagine that doing so will greatly slow their circulation -- nor stop other misconceptions in the future.
Perhaps, though, by answering these myths when you encounter them, you can clear the way for the greatest argument of all -- sitting the users of proprietary software down with FOSS to try it for themselves.