I appeared as a software developer in my own world, dominated by large corporations with closed source software - he was not questioned. As my career grew, the Internet became more and more present, and I was exposed to more and more open source software.
Looking back at most libraries, I'm not talking about the application level code and the scraps we wrote for my employers, not only was it a direct competitive advantage, and even less intrinsically represented what you consider intellectual property. More libraries, frameworks, and utilities have open source equivalents. Now, for me and the developers, I'm used to looking for existing libraries first, before embarking on such code.
That has already changed a lot. Many of these libraries could dry up as an open source due to lack of maintenance, and my employers would not suffer if they did. If they prospered or, at least, attracted materials, then these employers would win - what happens to my current employer.
Now, looking at what lies ahead, I am beginning to think that for most of the libraries and frameworks we will be writing, we must create them based on the assumption that they will be made with open source code. For libraries, utilities, and frameworks, this should be a basic case, not an assumption that they will be closed and that you will need to work to open them - which, as it turned out, often works a lot more after (getting approval, performance of reviews and cleaning).
If the base register is open source, I think there will be benefits:
- , , , , , , . , , , , . , .
- , , .
- , , , , .
- .
- , , , .
, , , - , . , ?