Introduction
Open-source software is usually a program in which its’ source code is available to any person or public for their use or modification from its original state free from charge and without any kind of license i.e. open. Open source code is typically created as a collaborative effort in which programmers improve upon the code and share the changes within the community.
A big question is how the open-source model for software development is superior to another kind of development such as the commercial model? Open source development is, effectively, many unrelated or related developers collaborate to produce software for free distribution and for improvement. On the other hand, commercial software is developed by programmers who are employed by a company for the purpose of creating a package that will be sold. The code is protected through various mechanisms, such as a patent and copyright. (Cajori, 2000)
Main body
In many cases, open-source software is also protected by copyright and sometimes by a patent. The main difference is that commercial software doesn’t grant the user any right beyond the application of software package, open-source software licenses usually provide broad rights to change the code and redistribute it either in whole or in part.
There are usually many kinds of encouragement that regard the use of open-source software which is normally viewed as either ethical or philosophical or pure practical issues. The open-source software is usually received at a cheaper cost compared to other software such as commercial source software. (Cajori, 2000)
There are also other features that make Linux open-source software as beneficial as open-source software. The availability of the source code and also the right to change and redevelop it is very useful. This enables free changing and improvement of software to be beneficial to one’s needs. This then makes it possible to use the code in new hardware; adapt it to a different condition, and understanding how the system works. This is why experts have reached a conclusion that open source software has a long time and bugs can be isolated.
There is also the flexibility of the software to an organization. This together with the combination to redistribute the rights increases the population of users which helps to build a market for support and customization of the software. This then improves the quality of the product and its functionality.
There is no one to restrict in a unilateral way the usage of the software. This is due to when a proprietary software vendor decides not to upgrade software for an older platform. This results in organizations sticking to an older version of the software or switching to another product. When open-source software is used the organization can fund the development for desired platform else look for other vendors to provide the upgrades. (McSeveny, 2003)
Open-source software has no end time. This is a very common concern with proprietary software. For example, if an organization uses a software product, and relies on the software manufacturer for upgrades of its continued development and then the software company closes down or merge then the lifetime of the product ends. Open-source software protects against this because if the group or organization that developed the code decides to stop its further development, it is always possible to find another software group to continue the maintenance and its improvement without any obstructions.
There are no black boxes” are possible because open source software is usually dependable. There are many reasons for this. By having the source code, it is possible to check and verify the contents of the algorithm and its implementation scheme. This difference lies in the fact that organizations are allowed to modify what is appropriate. A good example is the Linux kernel and its international patches. The patches are developed by different parties in countries where such a development is acceptable, and users in those countries can use such enhancements. With binary kinds of products, no inspection is possible, with closed source or nearly free licenses inspection is possible, but modifications are unacceptable. (McSeveny, 2003)
There is the possibility of forking: creating an alternative codebase. An example is the Linux kernel, where two distinct code bases are used, one which is perceived as stable and one as experimental. In this way, it’s possible to introduce new and harmful technologies without disrupting the stable ones. So, an organization interested in leading-edge technologies can try them, and people who use the Linux kernel in production areas can count on both stable and tested features.
No extra fees can be asked for modified versions and organizations can use the current code base to start other projects. Knowledge to work on can be gathered at a minimal cost. This is what made Internet software systems such an important factor in the new economy. Also, the right to modify them allows incredible expansion in the number of communication protocols and systems which are tailored for the organization’s needs. This then is a reason for the success of the Linux kernel which is widely used by students because of low cost mostly after college.
There are fewer conflicting priorities due to marketing pressures and expectations. This is so because there is no single commercial pushing for exact time delivery or features that have to be supported. Usually, open-source software is delivered when it is completed, and when the development team feels that the quality of the product is good. This means that software usually does not need many service packs and updates reducing the maintenance cost.
Of course, open-source software leads to the perception of disadvantages. However, some of them are only disadvantages if we are stuck to classical development models, which is of course not the case with open source. Some of them are:
Its’ not guaranteed that the development will succeed. It’s not possible to know the stability of the software and whether the software will be successful or not. This is a problem too with proprietary software, but it is more common in open source. Especially when a project is started with fewer backing companies this is due to immature and the development base still being developed. (Menninger, 1999)
There may be significant problems connected to intellectual software this so because some countries accept software and algorithm patents. This makes it hard to differentiate between piracy and genuine products. Open-source packages are modified with switches or patches that enable or disable patented code fragments according to country. Although the issue of software patents is a problem for the whole software industry, open source is probably one of the more clear cases where it can be shown how they harm the regular process of software development. The specific problems are that the availability of source code simplifies the detection of patent infringements by patent holders and that the absence of a company that holds all the rights on the software also makes it difficult to use the mechanisms in use by companies to defend from patent litigation. (Menninger, 1999)
Conclusion
It is difficult to know the existence of a project and its current status. There is less advertising for open source software and mostly to those that lack support from companies. However, several aggregation points for open-source software exist, although in many cases they are used by experts, and not by the general public or organization. They are also in many cases very specific to some software categories, such as scientific software or database systems.
It is extremely important to see through the various interpretations of the advantages and disadvantages of open source, and if possible try to analyze with quantitative methods if open source can be helpful in a given situation, or for a given user or company. (Menninger, 1999)
References
Cajori, F. (2000). A History of Computer Applications, New York: Dover Publications pp. 17-54.
Hayashi, T. (1995). Theory and Modern Use of Computers, Groningen: Egbert Forsten pp.64-142.
Ifram, G. (2000). The Universal History of Numbers: From Prehistory to the Invention of the Computer, New York: John Wiley & Sons pp. 34-78.
Menninger, K. (1999). Softwares and their Applications, New York: Dover Publications pp. 6-98.
McSeveny, A. (2003). History of Computers, Sydney: Pearson Longman pp. 112- 202.
Victor, J. (2007). The Mathematics and Relation with Computers, NJ: Princeton University Press pp. 47-124.