Open Source Software (OSS) has become a standard item in the lexicon of folks working in IT companies and departments. The charm of getting source code at no cost seems so appealing that everyone is for OSS.
Despite no commercial company pushing, at least willingly, the case for using OSS it seems to grow like wild weed across the business world.
The use of the term "Open" may appear as a deliberate attempt to sell OSS. The term "Open" hints at the following:
For every X which existed an anti-X or X-complement was evolved as a better solution to a known problem. So for Waterfall you have Agile and for Proprietary Software you have Open Source Software.
It is however completely debatable as to the agility of Agile (just think of the SCRUM rituals) and the openness of Open Source Software (just think of GPL terms and conditions).
Of course OSS does offer certain advantages like:
OSS comes with certain limitations, constraints and risks as listed below:
It is always good to remember that there is no free lunch and also every coin has two sides.
Despite no commercial company pushing, at least willingly, the case for using OSS it seems to grow like wild weed across the business world.
The use of the term "Open" may appear as a deliberate attempt to sell OSS. The term "Open" hints at the following:
- transparent
- easy to access, adopt and adapt
- no discrimination among its users
For every X which existed an anti-X or X-complement was evolved as a better solution to a known problem. So for Waterfall you have Agile and for Proprietary Software you have Open Source Software.
It is however completely debatable as to the agility of Agile (just think of the SCRUM rituals) and the openness of Open Source Software (just think of GPL terms and conditions).
Of course OSS does offer certain advantages like:
- increased coding productivity
- assurance from use of proven code
- multiple code options for a functionality
- visibility into code-level implementation allowing complete customization
OSS comes with certain limitations, constraints and risks as listed below:
- higher exposure to legal violations
- easy availability of code may choke creativity and inventiveness of programmers
- lack of timely support or no support available in case of issues with OSS
- programmers may have to spend more time pondering on legalities rather than technicalities (this may conflict with the psychology of a typical developer)
- Some OSS licensing may require "opening" up the code written using the OSS (for business organizations selling software source code is akin to IP, trade secrets and hence using OSS will make no business sense in certain instances)
It is always good to remember that there is no free lunch and also every coin has two sides.
