The openness in software is known as an open source, and generally, is interpreted as releasing your source code to the public community. Some other groups view openness as freeware software and consider anything commercial as closed (as opposed to open).But, openness has a deeper meaning in the software world, and open source is just the face of an extreme of openness (Turkle, 2005, pp 45). Openness in software is nothing but the level of flexibility you provide for people to build on top of your software. Openness in this matter is the opposite of control not closeness because the latter doesn't make sense in the context of software. Openness in software is all about allowing others to use, modify, and extend your software in different forms, and here open source and different types of licensing are only an aspect of this.
Openness: A Catalyst for Innovation
Over the last two decades, globalization has dramatically transformed the world and the way people interact with each other. It has ushered in an era of unprecedented collaboration, transparency, and Openness. These global trends have had a direct bearing on the ICT industry, which has also moved towards new levels of collaboration, transparency, and Openness. The rapid growth of ICT products and services on offer however, has created complex challenges in areas such as security, privacy, reliability, data management, and Openness (Rainie, 2010, pp 10). As with other global challenges, there is no one single solution for the very diverse issues companies face, and no organization can solve these problems on its own. Because of that, ICT companies, as well as companies in other sectors, are now collaborating, as well as sharing information and ideas at higher levels than ever before. All this had a tremendous impact on how innovation happens, with Openness becoming a catalyst for creativity. Openness is generally considered desirable and a good thing and one of the reasons why is because, besides promoting heterogeneity and choice, it has an impact on innovation (Lundberg, 2009, pp 59).
Technical Roots of Openness and Control
The main source of this whole openness and control is in the hand of computer architects, compiler designers, and programming language developers and is all about two key decisions in software: how to manage the integration of software and hardware, and how to allow programming language and compiler users to use what we have provided. As of the integration between software and hardware, in the simplest form, we know that each hardware has its own instruction set and specifications, and it is the job of the compiler to generate instructions compatible with hardware (Lenhart, 2007, pp 74). The more hardware compiler designers decide to support, the more hardware you as a programmer can run your programs on. Here some people may think that it's ...