802
Seeing big companies take advantage of BSD or MIT licensed projects without sharing their contributions will always pain me.
(lemmy.world)
this post was submitted on 28 Aug 2024
802 points (97.9% liked)
linuxmemes
21197 readers
42 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
This is not a hypothetical and is in fact quite common. Say you're working for a non profit, write code for a standard specification that is better than all other open options. It is better for everyone that companies adopt this code for interoperability.