Sometimes there’s a benefit in getting open source code into proprietary software. Think libraries implementing interoperability APIs, communication protocols, file formats, etc
That’s what permissive licenses are for.
If some company wants to keep their code closed and they have a choice between something interoperable or something proprietary that they will subsequently promote, and the licence is the only thing stopping them from going for the open source approach, that’s worse.
Completely agree that a good breadth of everything else is suited to copyleft licensing though
That’s the whole point, you’re leveraging the use of the commons so that it’s less feasible to keep your code closed. If they want to keep their code closed, they can spend a lot more manhours building everything from scratch.
Our man-hours come from leadership and architects so separated from code they can’t agree on drawings or what constitutes a micro service architecture or… Any real pattern at all.
This is a hypothetical that has no clear bearing connection to common practice.
In other words, I could just reverse this to contradict it and have equal weight to my hypothetical: devs should always use GPL, because if their software gets widely adopted to the point where companies are forced to use it, it’s better that it’s copyleft.
Sometimes there’s a benefit in getting open source code into proprietary software. Think libraries implementing interoperability APIs, communication protocols, file formats, etc
That’s what permissive licenses are for.
If some company wants to keep their code closed and they have a choice between something interoperable or something proprietary that they will subsequently promote, and the licence is the only thing stopping them from going for the open source approach, that’s worse.
Completely agree that a good breadth of everything else is suited to copyleft licensing though
That’s the whole point, you’re leveraging the use of the commons so that it’s less feasible to keep your code closed. If they want to keep their code closed, they can spend a lot more manhours building everything from scratch.
Our man-hours come from leadership and architects so separated from code they can’t agree on drawings or what constitutes a micro service architecture or… Any real pattern at all.
This is a hypothetical that has no clear bearing connection to common practice.
In other words, I could just reverse this to contradict it and have equal weight to my hypothetical: devs should always use GPL, because if their software gets widely adopted to the point where companies are forced to use it, it’s better that it’s copyleft.