Businesses don’t care about ideologies in general. They care about money.
They will use and contribute to FOSS whenever it fits their cost-benefit analysis.
That means, they usually don’t mind FOSS for stuff that they don’t sell, but that is used as infrastructure for their products.
For example, nobody makes money selling a kernel, but a kernel is a necessary base for many different products. If, for example, I build a car entertainment system, people buy a car entertainment system. Being able to use Linux as a base saves a huge amount of development cost. So a company might use Linux here and maybe even contribute some code. Because they benefit from cooperation on infrastructure that they don’t directly make money off.
But of course they aren’t in it for the ideology, so once using/contributing to FOSS would hurt their earnings, they will stop doing that.
Depending on the industry (thinking engineering and safety in particular) FOSS may actually cost more to implement and certify so that also has a bearing. But yeah, ultimately all about cost + revenue.
It feels like we’re saying the same thing at different levels of skepticism. Their primary motivation is going to be money as they’re private companies. Most people will stop contributing to an open source project when it stops being important to them. Either its not profitable for them, or its no longer cutting edge, or they just don’t like the direction of the project.
My main point is that private companies can and do contribute to the FOSS ecosystem and can do so in helpful, non-nefarious ways. Most aren’t google, most just want a useful and reliable message queue or database or kernel without trying to profit directly from the component itself and instead just using the component to do the thing that actually makes them profitable.
In my company, for example, we are encouraged to contribute bugfixes/features that we need to FOSS projects that we use. E.g. we find a bug in Angular, we are encouraged to fix it and send it upstream.
But we are forbidden from making anything open source that we’d want to sell.
But you are also right that also private people have their limits when they contribute to a FOSS project, as evidenced by the many, many forks of FOSS software when the original project changes in a way the contributors didn’t like (looking at you, OpenOffice. Or at any Debian-like OS)
Businesses don’t care about ideologies in general. They care about money.
They will use and contribute to FOSS whenever it fits their cost-benefit analysis.
That means, they usually don’t mind FOSS for stuff that they don’t sell, but that is used as infrastructure for their products.
For example, nobody makes money selling a kernel, but a kernel is a necessary base for many different products. If, for example, I build a car entertainment system, people buy a car entertainment system. Being able to use Linux as a base saves a huge amount of development cost. So a company might use Linux here and maybe even contribute some code. Because they benefit from cooperation on infrastructure that they don’t directly make money off.
But of course they aren’t in it for the ideology, so once using/contributing to FOSS would hurt their earnings, they will stop doing that.
Depending on the industry (thinking engineering and safety in particular) FOSS may actually cost more to implement and certify so that also has a bearing. But yeah, ultimately all about cost + revenue.
That is true, but on the other hand, industries like that usually don’t use FOSS.
It feels like we’re saying the same thing at different levels of skepticism. Their primary motivation is going to be money as they’re private companies. Most people will stop contributing to an open source project when it stops being important to them. Either its not profitable for them, or its no longer cutting edge, or they just don’t like the direction of the project.
My main point is that private companies can and do contribute to the FOSS ecosystem and can do so in helpful, non-nefarious ways. Most aren’t google, most just want a useful and reliable message queue or database or kernel without trying to profit directly from the component itself and instead just using the component to do the thing that actually makes them profitable.
Yeah, that’s exactly what I meant.
In my company, for example, we are encouraged to contribute bugfixes/features that we need to FOSS projects that we use. E.g. we find a bug in Angular, we are encouraged to fix it and send it upstream.
But we are forbidden from making anything open source that we’d want to sell.
But you are also right that also private people have their limits when they contribute to a FOSS project, as evidenced by the many, many forks of FOSS software when the original project changes in a way the contributors didn’t like (looking at you, OpenOffice. Or at any Debian-like OS)