this post was submitted on 27 Jun 2023
18 points (100.0% liked)

Free and Open Source Software

17966 readers
15 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

I don't get why big companys are afraid of open source software.

I know that monetizing open source is hard but in exchange they would have 8 billion programmers ready, for free!

Even if they do like redhat , as controversial as it is right now, they would be better off than just closing the source.

I would be willing to pay to have the license to modify my own software even if I couldn't redistribute it afterwards.

you are viewing a single comment's thread
view the rest of the comments
[–] furrowsofar@beehaw.org 6 points 1 year ago (1 children)

Businesses have a core mission. If you open a piece of software then you would need to have someone to support it internal to the company, it increases company liability, it increases distraction, and to justify all of those downsides it would have to have a clear upside.

The other problem is that companies are short term. Even if you could demonstrate all of the above, this could not be sustained for very long. Priorities would change and personnel would be reassigned or move on. Keep in mind head count costs are very high for companies. Moreover often head count is harder to get and maintain then the $ it represents to the company. By this I mean you might think head count is just $ on a project, but generally in terms of getting resources head count and $ are totally separate things.

[–] AnalogyAddict@beehaw.org 3 points 1 year ago (1 children)

I was going to respond, but you said it so much better than I could have.

The tension between liability and control is real.

[–] furrowsofar@beehaw.org 2 points 1 year ago

Yes there is the control end too. To develop software internally in a company you have to show there it gives you a proprietary advantage that other companies do not have and cannot buy. So that leads one down the confidentiality path. Every stupid thing then gets justified based on confidential and proprietary even if it is a stupid argument (not saying it is always a stupid argument). Imagine then saying let's open the software. Might even be the correct thing to do but then you'd have to admit your proprietary arguments were BS.

Then even if you did that, you would have to do a deep code audit to remove anything that could potentially be an issue. Then you'd have to run that all through legal and up the flag pole to executive level. Then they would ask, why are we doing this. You had better have a good answer.