77 points

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

permalink
report
reply
31 points

If some company wants to keep their code closed

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.

permalink
report
parent
reply
11 points

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.

permalink
report
parent
reply
6 points

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.

permalink
report
parent
reply
10 points

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.

permalink
report
parent
reply
59 points

This seems like complaining that the BSD license does exactly what it intends to do.

permalink
report
reply
19 points

Yeah, as if the authors had no idea what terms the license has…

permalink
report
parent
reply
26 points

ignorance is one thing, but it’s a whole nother level of loser behaviour to intentionally do unpaid work for big tech companies in your free time

permalink
report
parent
reply
18 points

“Unpaid work” is pretty much all OSS development. “Here’s a thing I made, anyone can use it for whatever they want as long as they give credit” is a very simple philosophy. Not everybody who works on OSS is opposed to the existence of closed source commercial software, and rather a lot of people don’t like viral licenses like the GPL. Really out of line to call people who contribute their time and effort to making free software available to everyone losers just because you disagree with their choice of license.

permalink
report
parent
reply
11 points

I take it that you’re in the first camp

You’re doing it for yourself/for fun/to better humanity

If some corporate fucks want to abuse that then it’s their problem not yours

permalink
report
parent
reply
4 points

You’re clearly someone who never contributed to open source.

permalink
report
parent
reply
3 points

You’re making it for fun. You’ve achieved your desired fun, and lost nothing if some rando takes it and makes another fun project, or big mega corp uses it.

What’s gonna stop them from just stealing it anyways? Why would they care about Joe Shmoe when they have infinite number the lawers you have? Also AI kinda makes this irrelevant because it will rewrite the code in a way that’s probably not protected, or at least provide enough shielding that their 10000 lawyers will.

Also also, what about all the mega corps that already use linux? That’s free an open source and they’re free to run their proprietary code on it. If you’ve ever contributed to linux, or any tool that’s built into a distro you’re not this supposed loser who’s done free work for a big tech company. It’s silly to complain about this.

permalink
report
parent
reply
57 points

Someone biulds a thing and puts it on the curb in front of his house with a sign:

I had fun building this and learnt a lot. Do with it whatever you want.  

Then someone else comes along, takes it, and sells it.
I fail to see how the inventor was taken advantage of. They presumably thought about which license they want to use and specifically chose this one.

permalink
report
reply
59 points

Taking without giving is always viewed negatively in social settings.

Maybe “taking advantage of” is wrong but then again, it is a dick move anyway.

permalink
report
parent
reply
33 points

If I’m putting BSD or MIT license on something, I’m explicitly saying you can use it however you want, you can change it however you want, you don’t have to share back, I just ask for credit for my part in it

It’s not taking so much as being given freely

permalink
report
parent
reply
21 points

Exactly this. I have a couple of small projects that are MIT licensed specifically because I don’t care how people use them or what they use them for. If someone finds it useful then they’re welcome to do whatever they want with it.

This idea that I’m being somehow hoodwinked or taken advantage of because the thing that I explicitly said could be used freely is being used in a way that doesn’t align with the values of some other completely uninvolved third party is beyond absurd.

permalink
report
parent
reply
0 points

I think you are missing the point. I am not saying it wasn’t. But if you makes a gift for your friend’s birthday, and they don’t bother at all to return the favor/attention, would you be upset as you would think it is kinda a dick move?

permalink
report
parent
reply
28 points

With software there would be infinite copies of that free item for everyone to get. So the dick move is to sell it to people who are unaware that they could get it for free.

permalink
report
parent
reply
11 points

It’s a little different than that, isn’t it? More like: " look at what I built, here’s a step by step guide that makes it work. Do with it whatever you want." Some people want to use it for their job. Others might use it for personal use, or to build more open source projects.

permalink
report
parent
reply
9 points

This person takes advantage of people who are unaware that they could just get it for free as well.

However, if this person is putting in an effort to sell this item (like advertisement or creating a platform to distribute this item more easily) then I don’t see anything wrong in charging money for that.

permalink
report
parent
reply
8 points

That’s not really a common situation though. Sure, people might use the BSD license on something they did as a hobby, or just to learn things. But, the scenario described here is more like:

A group of people all have the same little problem, and they work together to come up with a solution for it. They solve the main problem, but their solution has a few rough edges and there are similar problems they didn’t solve, but they’re not motivated to keep working on it because what they have is good enough for their current needs. So, they put out some flyers describing how to do what they did, and inviting anybody who’s interested to keep working on improving their fix.

A company comes along, sees the info, and builds a tool that solves the problem but not quite as well, and for a small fee. They spend tons of money promoting their solution, drowning out the little pamphlet that the original guys did. They use as much IP protection as possible, patenting their designs, trademarking the look and feel, copyrighting the instructions, etc. Often they accidentally(?) issue legal threats or takedown notices to people who are merely hosting the original design or original pamphlets.

Maybe the original inventor didn’t get screwed in this scenario, but you could say that the public did.

permalink
report
parent
reply
2 points

This is perfectly fine to do under GPL as well. I don’t see the problem.

There are companies that sell Linux distros on a DVD or USB drive.

permalink
report
parent
reply
52 points

I feel like most people base their decision on license purely on anecdotes of a handful of cases where the outcome was not how they would have wanted it. Yet, most people will never be in that spot, because they don’t have anything that anyone would want to consume.

If I had produced something of value I want to protect, I wouldn’t make it open in the first place. Every piece of your code will be used to feed LLMs, regardless of your license.

It is perfectly fine to slap MIT on your JavaScript widget and let some junior in some shop use it to get their project done. Makes people’s life easier, and you don’t want to sue anyone anyway in case of license violations.

If you’re building a kernel module for a TCP reimplementation which dramatically outperforms the current implementation, yeah, probably a different story

permalink
report
reply
20 points
*

I once read that the license should be smaller than your code. Gives me a good baseline:

  • Permissive license for small projects and little tests

  • Copyleft license for big projects

permalink
report
parent
reply
2 points

I’m stealing this 👍

permalink
report
parent
reply
1 point

Cries in left-pad.

permalink
report
parent
reply
19 points

Well, ideally you’re choosing your license based on the cases where it differs from others and not the majority of times where it doesn’t make a difference.

Someone aiming to make Free software should use a copyleft license that protects the four freedoms, instead of hoping people abide by the honor system.

Also, no one can 100% accurately predict which of their projects will get big. Sure, a radical overhaul of TCP has good odds, but remember left-pad? Who could have foreseen that? Or maybe the TCP revision still never makes it big: QUIC and HTTP/3 are great ideas, and yet they are still struggling to unseat HTTP/2 as the worldwide standard.

permalink
report
parent
reply
7 points

Seems like using a copyleft on the reference implementation of a new protocol is a great way to ensure the protocol is never widely adopted.

permalink
report
parent
reply
1 point

People who used left-pad deserved everything that happened to them. But, very valid point.

There is no honor system. If your code is open for commercial reuse, that’s it. If you have any expectations that are not in line with that, then yes pick a different license.

I guess I agree with you, I’m just phrasing it from a different perspective.

permalink
report
parent
reply
34 points

I read a story of someone that contributed to a BSD project, including fixes over some period of time, but later they ended up having to use a proprietary UNIX for work, that included their code, in a an intermediate, buggy state, but they were legally forbidden from applying their own bug fixes!

At the very least the GPL guarantees that if I am ever downstream of myself, I has fix my own damn mistakes and don’t have to suffer them.

I am still willing to contribute to BSD stuff, but vastly prefer something like the AGPLv3.

permalink
report
reply
-6 points
*

So it’s an argument against restrictive licenses? The more freedom the better? I mean Unix in this case had a too restrictive license?

permalink
report
parent
reply
11 points

What? GPL does not restrict freedom, it ensures its continued existence.

permalink
report
parent
reply
1 point
*

Read above please. You cannot import GPL code into BSD licensed code without restricting the code distribution. In the other direction, you can do it and just add a notice about the license. It does not add restrictions to the distribution. Otherwise Linux distributions wouldn’t even have OpenSSH in base install images.

permalink
report
parent
reply
7 points

It’s an argument against a license that permits relicensing under a more restrictive license. (E.g. BSD)

permalink
report
parent
reply
2 points

Of other software, yes. For example Linux distributions can use the BSD or MIT licensed code without any problems.

But it does not allow to remove the license from the software.

On the other hand GPL code cannot be imported into BSD code without introducing restrictions.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

Hint: :q!


Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules
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 sudo in 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!

Community stats

  • 6.7K

    Monthly active users

  • 1K

    Posts

  • 20K

    Comments