Maintained by: Nah Soo Hoe

Last updated: 26 April 2003

This FAQ was written as it was felt there was a necessity for a short, simple, yet comprehensive document that we could use to refer non-open source aware people to and also to distribute on the web to help raise the profile locally for open source. This is meant to be a living document and so if you wish to contribute or have some opinion please e-mail the maintainer at webmaster@my-opensource.org.

Comments and contributions: Please forward any to webmaster@my-opensource.org

The latest version of this FAQ can be found at http://www.my-opensource.org/oss-faq.html

For information on the duplication and distribution of this FAQ please see Question 99.

(Note: This is an extensively revised version of the original FAQ which appeared on the www.my-opensource.org website from 1999-2002. The contributors to the original FAQ include: Beh Hong Leong, Loke Kar Seng, Fan Li Tai, Dinesh Nair, Nah Soo Hoe)

Contents

1. What is open-source software?

2. Is open-source software a new thing?

3. What is the difference between Open Source and Free Software?

4. Why is open-source software important?

5. Why is open-source software important to Malaysia?

6. Why is the open-source process/model important to eductional institutions in Malaysia?

7. What open-source software is available?

8. Open Source software licensing and copyright(/left)

9. What about accountability and support for open-source software?

10.Is open-source software secure?

11.What business models are available for open-source software?

99. Can I reproduce this FAQ and distribute it?

100. A little open-source software culture

101. Hackers are not crackers

1. What is open-source software (OSS)?

Software comes in the form of compiled code (binaries), and the human-readable source code from which these binaries are compiled. Open-source software is software whereby the software is distributed in the form of binaries as well as source code. But, more than that, to qualify as open source, the distributor cannot restrict any party from redistributing the software, nor can any party be restricted from making modifications or making derivative works based on the source code.

Open source has its roots in “Free Software”, a term coined by Richard Stallman of the GNU Project and the Free Software Foundation (FSF). The word “Free” is to be read in the context of “Freedom” and liberty not “free” as in price. The GNU Project set out to write a Unix-compatible software system, and was led by Richard Stallman after he resigned from the MIT AI Labs in the mid-1980s.

Note: Open source is different from shareware and freeware which normally do not fulfill the definitions of open source and as a norm do not make the source code available.

The definition of ‘Open Source’ is amplified further at the Open Source page http://www.opensource.org/docs/definition.php. The FSF’s ‘What is Free Software’ at http://www.fsf.org/philosophy/free-sw.html should also be read.

Back to contents

2. Is open-source software a new thing?

No. open-source software has been around since the days of the early mainframe computers.
In those days, software was freely exchanged with source code by researchers and academics. It used to be commonly called free software, and was typified by The Free Software Foundation and the GNU Project. The Internet was built using free software and to this day it still depends a lot on it for its functioning. The term “open source” itself came about when, with the success of the Internet, the technical people tried to introduce good quality free software into their organisations and were met with disbelief by the management that anything which has no price-tag to it can be good and reliable. To try and overcome the negative sentiments about using non-commerical free software the term “open-source software” was coined.

Back to contents

3. What is the difference between Open Source and Free Software?

OSS has its roots in Free Software. The Free Software Foundation has defined what constitutes Free Software and it shares the same basic philosophy and outlook as OSS. However, the FSF favours the retained usage of the term “Free Software” to reflect the “freedom” aspect of the philosophy behind it. It argued that by changing the name to Open Source Software, the ideals expounded by Free Software will not be emphasised and subsequently may even be lost. This may result in a tendency for people to compromise and switch back to software which does not fulfill the Free Software definition. Many of the Open Source Licenses are recognised by the FSF as Free Software.

In everyday usage to all intents and purposes we can treat OSS and Free Software to be the same. In fact some people are now using term Free and Open Source Software (FOSS) to refer to open source and free software in general.

Back to contents

4. Why Is open-source software important?

Participation and Evolution

Open-source software provides an alternative software development model in which the development need not be made by a closed monolithic group of exclusive software engineers and programmers. In some projects anyone interested can participate in the development, and because the source code is readily available, everyone can scrutinise it, learn from it, and contribute to it. It should also be viewed as important in the context of the evolutionary process of software, whereby the wheel need not be reinvented continuously. This is one of the hallmarks of most scientific discovery whereby present day researchers build upon the free body of knowledge already available.

No Technology or Vendor Lock-in

Under open source, everyone has access to the source code and the freedom to modify, use and re-distribute the un-modified or modified code. This means that now anyone has the freedom to learn, redistribute and enhance the software. It prevents single vendor and technology lock-in since the code is there for all to see and so no one or vendor can implement some secret or proprietary technology. Instead it ensures that open standards are promoted and preserved. The compliance to open standards helps to bring about fairer competition based on technical merit and everyone or organisation, big or small, can participate.

Reliability

Free distribution of the source code also offers the avenue for open-source software to be more reliable. Many eyeballs will have scrutinised the source code and people will have been banging on it to see what breaks and fixing it in a kind of darwinian mutation by peer review that has produced some very reliable software. This peer review and feedback mechanism contributes to the transparency in the reliability and security aspects of software (i.e. you don’t just have to take the vendor’s word for it).

Alternatives

Open source provides the world an alternative model for the creation and dessemination of software. It offers a model that avoids the pitfalls of concentrating monopolistic power in the hands of a select few. It is a model which assures a free flow of ideas, technical competence, information and encourages intellectual cross-pollination. One can think of it as a transfer of technology in a natural manner.

Software Freely Available

While many of the Open Source or Free Software Licenses do not prohibit charging for the software, most of the major OSS is freely available for downloading over the Internet or for distribution on CD-ROMs with no licensing fees. This will benefit poorer societies such as those in the Third World in providing useful, good and affordable software running on affordable computers and networks.

Back to contents

5. Why is open-source software important to Malaysia?

OSS is especially important to a developing country like Malaysia which is striving to transform its economy into a technologu-driven and knowledge-based one.

The availability of source code is very important. It allows the local software people the oppportunity to “look under the hood” and learn. Typically in a less-developed country, what is lacking are people with skills in developing system software and these are crucial to implement any technology. It is no accident that many of the open source projects are of this nature since these are more challenging and interesting and tend to attract the interest of the software hacker. Open source promotes an environment conducive for technical and system development.

Most of the proprietary off-the-shelf software that the country use are from foreign vendors and it is totally dependent on these companies for its ICT implementations and projects. This dependence on software and technologies where we have little control or say can be overcomed to a large extent if OSS is used more, especially by the Government. In addition to savings on foreign exchnage and import expenses the ability to build and leverage on open source technologies will result in a critical mass of good local coders and this will help to build up the local software industry. Localised versions of software can be produced more easily too.

With the availability of source code and the freedom to change it and redistribute it, a country can make use of open source to Learn, Innovate and inVEnt (LIVE) ICT technologies. This is one of the most compelling reasons for a country to embrace the open source model.

Back to contents

6. Why is the open-source process/model important to the eductional institutions of Malaysia?

Open source is particularly important in the context of Malaysia’s education system. All schools are now encouraged to have computer and IT courses where students are supposed to learn
about computer technology and the Internet. However, given the current commercial PC operating environment, most of the students will only end up learning how to use the Windows Manager and some specific applications. To promote the hacker culture and mindset, we have to encourage our young to question, probe, experiment and innovate. The current Windows-based PC environment is a close source system and provides an inflexible environment for experimentation and probing under the hood. However if an open-source system like Linux
is used for the PCs in the schools, the operating environment and source code availability provides vast opportunities for teaching, learning and experimentation.

Furthermore it makes huge economical sense operating open-source environments in education institutions as many of these run on relatively inexpensive older Pentium PCs , are very powerful and of high quality. They are compatible with the Microsoft Windows systems widely used in schools to-day, and can co-exist on the same hard drive. There is also a wealth of documentation and support available.

What else can you ask for? Did we say it is almost free? We should be teaching/learning real computing and information technology basics (which is a science) and not just one commercial vendor’s products (which is a product).

Back to contents

7. What open-source software is available?

The list given below is only the tip of the iceberg. For a first hand look at the vast array of open-source software under development visit:

Freshmeat - http://freshmeat.net

Sourceforge - http://www.sourceforge.net

Open Source Directory - http://osdir.com

Multiuser Networked Operating Systems/Platforms

Linux - The most popular OSS operating system on the planet!

http://www.linux.org

http://www.linux.com

http://www.distrowatch.com

FreeBSD - Second only to Linux in terms of Open Source operating system usage

http://www.freebsd.org

OpenBSD - Famous for its security settings and features

http://www.openbsd.org

Internet/intranet Services and Applications

Apache web server - Accounts for over 60% of the web servers on the Internet

http://www.apache.org

BIND name server - The software that provides the DNS (domain name service) for host name resolution. Many of the root name servers as well as the Internet backbone network ISPs use BIND.

http://www.isc.org/products/BIND/

Sendmail mail server - The most widely used email transport software on the Internet.

http://www.sendmail.org

Software Development Platforms

GCC - The compiler for C, C++, Objective-C, Fortran, Java, and Ada that comes standard with all the major OSS operating systems

http://gcc.gnu.org/

JBOSS - A popular open-source implementation of J2EE

http://www.jboss.org

Perl - A very popular language widely used in scripts to drive `live content’ on the World Wide Web.

http://www.perl.org

PHP - A very popular scripting language for interactive web development and applications

http://www.php.net

Python - A popular object-oriented scripting language for web and other development

http://www.python.org

Zope - A popular web development platform based on Python

http://www.zope.org

Database Systems

MySQL - A very popular open-source RDBMS

http://www.mysql.com

PostgreSQL - A popular open-source RDBMS with many advanced features

http://www.postgresql.org

The Desktop Environment

GIMP - A powerful graphics image editor and manipulator.

http://www.gimp.org

GNOME - A popular open-source dekstop GUI environment

http://www.gnome.org

KDE - Another popular open-source dekstop GUI environment

http://www.kde.org

Mozilla - The open-source evolution of the popular Netscape web browser, email and news clients

http://www.mozilla.org

OpenOffice.org - An integrated office suite featuring wordprocessing, spreadsheet, drawing and presentation software largely compatible with Microsoft Office

http://www.openoffice.org

SAMBA - An implementation of the Microsoft SMB server and client enabling open-source computers to communicate with Microsoft Windows networks

http://www.samba.org

VNC - A remote control software for controlling GUI-desktops from a remote host

http://www.uk.research.att.com/vnc/

Xfree86 - An implementation of the X-Windows windowing system needed for running GUI applications

http://www.Xfree86.org/

Ximian Evolution - A GUI desktop application for personal email, calender and diary having similar look and feel with Microsoft Outlook

http://www.ximian.org

Back to contents

8. Open Source Software licensing and copyright(/left)

One common misconception among many people is that there is no copyright for open source. All open-source software is copyrighted unless the authors or owners have released them to the public domain. The Open Source Initiative website lists down over 30 recognised Open Source Licenses - http://www.opensource.org/licenses/index.php

Here we list down the two most common types:

BSD-Style Licenses

These are probably the oldest type of Open Source software license. The licensees are given the option of creating derivative closed-source commercial software based on the original open source. In other words this category of license allows one to take an open-source software and redistribute it with or without modifications as proprietary software.

Software under this type of license include Apache, BIND, and FreeBSD.

General Public License (GPL)

This license was devised by the Free Software Foundation. It is a license using the “copyleft” concept. “Copyleft” requires that the product derived from the original open-source software must also be distributed under the same licensing regime as the original. Thus it cannot be turned into a closed-source product, although it can be a commercial product whereby the seller must transfer the full rights of freedom of distribution, modification etc. to the user.

The GPL is an example of a copyleft license. The Linux operating system is the most well known example of GPL licensing.

Back to contents

9. What about accountability and support for open-source software?

These two issues are frequently raised especially for open source adoption and acceptance in businesses and corporations.

Accountability

There is a misconcpetion by many people that OSS is developed and/or maintained by volunteer programmers and hobbyists solely with no single party fully accountable for it. In reality we find that for a mainstream open source project we have legally established non-profit foundations or normal businesses supporting the software. For example, Apache is supported through the Apache Software Foundation and Red Hat Linux is supported and maintained by Red Hat Corporation. The former is a well-established non-profit foundation while the latter is a commercial business entity.

What is true is that initially many open source projects are started off by enthusiasts and volunteers in wanting to solve some problems or implement some new technologies. However once a project becomes popular enough for mainstream usage all over the world, we find that a responsible body will have emerged to take charge of it. So in reality if one sticks to mainstream popular open-source software accountability will not be an issue.

Support

One of the most frequently cited reasons against using open-source software especially in corporations is the alleged lack of support. This is only a perceived problem. In essence there is little difference between open source and proprietary closed source commercial software in that for both we usually rely on our local vendor to support us if we do not want to do it ourselves. There exists professional companies providing service and support for open-source project deployment and implementation. In fact, with the source code made available, many competent vendors and IT personnel find that they manage to resolve deficiences by patching the code themselves. With a proprietary closed source software package they will have to wait for a (possible?) update by the software distributor before they can resolve the problem.

The Internet is another great source of informal support that is surprisingly (for the uninitiated!) efficient. With its myriad of websites, newsgroups, FAQs and HOW-TO documents available online it is an almost unlimited resource for resolving technical and configuration issues.

It should also be noted that many open-source products can be purchased commercially with support comparable with close source software.

Back to contents

10. Is open-source software secure?

A common charge against open source is that it is inherently insecure because as the source code is readily available, anyone can scrutinise it to look for bugs and vulnerabilities in both the design and coding. This is true in that with source code availability one can study the code and try to exploit any weaknesses found. The flip-side to this is that it also enables anyone who wishes, to flush out weaknesses in the design and coding thereby discovering the vulnerabilities before the attackers and making the software more secure. Source code availability also has many other advantages like enabling vulnerability fixes and/or workarounds without waiting for the code authors and independent checks and audits of the software code.

It should also be noted that the inavailability of source code does not prevent the discovery of vulnerabilities. Modern debugging and software development tools can be used to monitor and even disassemble and reverse-engineer the executables to look for bugs and vulnerabilities.

So the answer to the question of whether open source is secure or not depends very much on the software authors, just like close source. It is definitely intrinsically not less secure than close source and in fact as pointed out above there are several distinct advantages in using open source as far as security is concerned.

Back to contents

11. What business models are available for open-source software?

Since OSS usually can be obtained without licensing fees and charges, the traditional software business model of selling software to the mass market cannot be used. Other commercial business models have to be used. They include:

• Charge for services, support, customisation, training, etc. but not the software.
• Develop application using OSS platforms and tools. Product developed is not open source. This is no different from normal software development for close-source platforms.
• Develop tools and/or generic applications and open source them. Charge for the enhanced version(s).
• Dual licensing approach to software developed, one is open source, the other is commercially licensed. The most successful example of this business model is the MySQL database software.

Back to contents

99. Can I reproduce this FAQ and distribute it?

To make the information in this document as widely and freely accessible as possible, you are allowed to copy it and distribute it in whole or in part. It will be nice if you can acknowledge this website as the source of the information but we are not demanding it!

Back to contents

100. A little open-source software culture

First off, it is quite simply stated that the hackerdom culture is essentially a culture of giving and peer recognition. It is a mindset that values above monetary reward the pure satisfaction of solving problems and building things and gaining peer group recognition. It cultivates a gift culture whereby people contribute in a paradigm of voluntary mutual help. It can be a highly competitive paradigm, unforgiving in its vocal criticism of incompetence and pretenders.

The internet provided the medium for such a culture to take hold, and it is no surprise that the present day hacker culture traces it roots back to the earliest days of the internet and network
computing. This is detailed in the essay ‘A Brief History of Hackerdom’ http://catb.org/~esr/writings/hacker-history/hacker-history.html

We dare not hope to even attempt to categorize the open-source/hacker culture here, but can offer the new reader some guidelines and leads to information available. We recommend that you first throw out the misconceptions propagated by the mass media of ‘evil hackers’ wrecking havoc on the Internet.

We can also recommend you read essays by Eric Raymond and Richard Stallman for starters (do keep in mind that hackers can be playful characters so do read with a open mind):-

The GNU Manifesto - http://www.gnu.org/gnu/manifesto.html

What is Free Software - http://www.gnu.org/philosophy/free-sw.html

Categories of Free and Non-Free Software - http://www.gnu.org/philosophy/categories.html

Free Software Licenses - http://www.gnu.org/licenses/license-list.html

The Cathedral and the Bazaar - http://catb.org/~esr/writings/cathedral-bazaar/

How To Be A Hacker - http://www.catb.org/~esr/faqs/hacker-howto.html

The Jargon File - http://catb.org/jargon/

For a tongue-in-cheek essay on the rocky road to hacker-wizardhood check out

‘The Logitanaka’ - http://www.catb.org/~esr/faqs/loginataka.html

Back to contents

101. Hackers are not crackers

The term “hacker” has often been abused in the popular press as meaning a person who breaks into computer systems illegally. This is the furthest thing from the truth. Real hackers are people who share in the culture of expert programmers and networking wizards with a history tracing back to the origins of the internet at ARPAnet. Hackers solve problems and build things, and believe in voluntary mutual help.

The “pseudo-hacker” of notoriety should be properly termed “crackers” and are a destructive breed who break into computer systems for illegal purposes.

Back to contents

Endword: “Binaries May Die But Source Code Lives On”

Last updated: 21 February 2005

This work is licensed under the
Creative
Commons Attribution License. To view a copy of this license, visit
http://creativecommons.org/licenses/by/2.0/ or send a letter to
Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305,
USA

This document was written as it was felt there is a necessity for a
short, simple, yet comprehensive document that one can use to answer
many of the myths and realities surrounding FOSS. Some of these
issues are well-founded but many come about because there have been
many myths circulated about FOSS. This is brought about in part
by people who do not understand FOSS and the way it works and also in
part by the detractors of FOSS to sow the seeds of fears,
uncertainties and doubts (FUDs) into the minds of the users.

There is no accountability and ownership for FOSS

Myth: FOSS is
developed/maintained on a best effort basis by volunteers.
Therefore there is no single party responsible and fully accountable
for the software.

Fact: The mainstream FOSS
projects (software) are all run by a tightly knit developer
community. There are legally established non-profit foundations
or normal businesses supporting the software. For example, Apache
is supported through the Apache Software Foundation and Red Hat Linux
is supported and maintained by Red Hat Corporation. The former is
a well-established non-profit foundation while the latter is a
commercial business entity listed on NASDAQ.

Fact: It is true that a FOSS
project, when it starts off, is sometimes carried out by enthusiasts
and volunteers on a best effort basis only. However once it
becomes popular enough and is considered mainstream software in use all
over the world by many people, a responsible body will step forward (or
be created) to take charge of it.

There is no warranty for FOSS

Myth: FOSS is always licensed
“available as is” and without any warranty.

Fact: While this is usually
true, it does not mean that commercial close source is much
better. Warranty clause in the latter usually offers scant
protection only and often limited to 90 days upon receipt. Most
close-source software licenses come with disclaimers in the end-user
licensing agreement (EULA) to exempt the vendor from any liabilities
arising from the use and misuse of the software.

Fact: There are commercial
vendors which have a separate service offering warranties for the FOSS
software that they support. Examples of vendors which offer this
include Suse Linux ( a subsidiary of Novell Corporation) and IBM.

Fact: Some FOSS have dual
licensing, a FOSS license and a commercial license. The
commercial license offers warranty. A good example of this is the
MySQL database product.

There is no one to turn to for support of FOSS

Myth: Since FOSS software is
not owned by anyone there is no reliable support for it.

Fact: While the original
software author/owner may or may not offer support, many other sources
do. These include the local vendors that the user deals with, the
user communities worldwide and the huge Internet resources available
like mailing lists, forums, websites etc.

Fact: Commercial
proprietary software users still mainly rely on their local vendor for
support. So the key question to ask here if you are the type of
user who relies almost exclusively on your vendor for support is
whether the local vendor that you deal with can support the FOSS
software that you intend to use. In relation to this, the local
vendor will find it easier to resolve some technical problem with FOSS
software as it has, in addition to the software author, the Internet
resources to turn to and very often the problem had been encountered
before by others and a resolution available. The culture of FOSS
development and usage is such that there is a lot of experience and
information being shared by users and developers among the FOSS
communities worldwide over the Internet.

FOSS is not secure

Myth: As source code is
readily available FOSS is inherently not secure since the bad guys can
scrutinise the code and find vulnerabilities more easily

Fact: The availability of
source code has several security advantages. It facilitates the
scrutiny by many people to flush out weaknesses in the design and
code. Also, when a vulnerability is found, fixes and/or
workarounds can be made without waiting for the code authors if the
vulnerability is a critical one. The fixes made also can be
studied and scrutinised to ensure that they are made correctly.

Independent checks and audits can only be made with source code
availability.

Fact: Another advantage
of source code availability is that in the event that the platform on
which one uses the application has been obsoleted by the vendor, it is
still possible to continue using the application safely on the
obsoleted platform even if vulnerabilities have been discovered for the
application in question since one can download the updated source and
re-compile it for the obsoleted platform. For close-source
applications one has no choice but to upgrade to the newer supported
platforms.

Fact: Unavailability of
source code does not mean vulnerabilities cannot be discovered.
Modern debugging and software development tools can be used to examine,
disassemble and reverse-engineer the close-source executables to look
for bugs and vulnerabilities. The most glaring illustration of
this is the never-ending vulnerabilities being discovered for Microsoft
products like IIS, IE and Outlook.

It is easy to hide backdoors in FOSS

Myth: As FOSS software is
usually available from more than one source, it is easy for
someone to offer FOSS software with hidden backdoors for downloading
and distribution.

Fact: This is possible
and so one should not download software from unknown and untrusted
sites. One should also ensure that the software security checksum
corresponds with the published value from a recognised official
downloading site.

Fact: FOSS offers the
ability to examine the source and re-compile to ensure that there
are no backdoors. Also, if it is known that a FOSS
development/distribution site had been compromised, there is no
need to depend on the author/vendor alone to check the software.

Fact: Commercial
proprietary software have been known to ship infected with virus and
backdoors. Backdoors are also possible in close source and
they will be more difficult to detect as the source code is not readily
available. Experience has shown that a backdoor incorporated into
a mainstream FOSS project does not stay undetected for long while there
are examples of proprietary software having a backdoor in it for years
and only upon open-sourcing is the backdoor found. A good example
is the case of the database software Interbase which was found to have
a backdoor within six months of it being released under an
open-source license.

There is no copyright and licensing for
FOSS

Myth: As source code is
available freely, there is no copyright and licensing in FOSS.

Fact: Almost all the
popular and widely used FOSS software are copyrighted. The
ownership stays with the author(s) unless they have relinquished their
claims to it or transfer the copyright to another party.

Fact: There are over 30
Open Source Licenses recognised by the Open Source Initiative
(OSI). The Free Software Foundation (FSF) has successfully
pursued and enforced the General Public License (GPL) on
several commercial violators.

Copies of FOSS cannot be sold for money

Myth: FOSS software
cannot be charged for a profit.

Fact: Whether one is
allowed to charge for a FOSS software will depend on the license under
which it is distributed. The commonly accepted FOSS definition
does not specify that one cannot charge for FOSS. The �free� in
Free Software refers to �freedom� and not �no charge�!

Source code must be given to everyone for FOSS

Myth: If I release my
software under a FOSS license, I must make the source code easily
available to the whole world.

Fact: You are only
obligated to give the source code to the users of your software.
So if you are releasing the software for the general public to use,
then of course you have to make available the source code to
everyone. However, if the software is to be used only by a
private group of users , then you need to provide access to the source
code to these users only. However note that these users are
allowed to distribute your software and source code to others.

Software available on FOSS platforms must be released as FOSS too

Myth: Only FOSS software is
allowed to run on FOSS operating platforms and software developed on a
FOSS platform has to be released as FOSS too.

Fact: The software
available for use on FOSS platforms may or may not be FOSS
themselves. So while the majority of the software running on FOSS
platforms like Linux, FreeBSD etc. are FOSS, there is also available a
substantial number of close-source commercial software e.g DB2, Oracle,
Netware etc.

Fact: If one uses FOSS
software development tools and environment to develop a piece of
original software, one need not release it under a FOSS license if the
software is complete in itself, i.e. it can exist and run on its own
without invoking other parts of the system which are covered by a FOSS
license, e.g. libraries etc. If it does or if portions of the
developed software contain source code from a FOSS software, then the
specific terms of incorporation and usage of the software invoked has
to be looked at to ascertain whether the developed software needs to be
made FOSS too.

FOSS operating platforms are not user-friendly

Myth: FOSS platforms
suffer from their Unix-legacy in that the main user interface is
command-line oriented (CLI); so there is a need to remember archaic
commands.

Fact: This may be
possibly true in the past but all modern FOSS operating
platforms support GUI windowing systems and these are very
much the default interface. The user has a choice of using either
GUI or CLI to run most of the applications where applicable.

There are many versions of the same FOSS software

Myth: The ability to fork off a
FOSS software project will lead to many incompatible different versions
and the open nature of FOSS encourages forking.

Fact: Most FOSS have one
project only and forking happens only as a last resort, after all
attempts at reconciliation fail.

Fact: When forking does
take place, over some time, either the new project becomes dominant and
widely used or it dies off due to lack of support/usage or it
eventually gets folded back into the original project. It is thus
akin to a natural selection process favouring the majority of the
users. The ability to fork off a different project can be viewed
as a good thing as it ensures that ultimately the surviving project
will have the features that the majority of the users want.