Comment by PedroBatista
8 months ago
Why is that such a problem other than the human factor of seeing your code being used by some guys you don’t like?
8 months ago
Why is that such a problem other than the human factor of seeing your code being used by some guys you don’t like?
> seeing your code being used by some guys you don’t like?
This is not even in the list of my concerns. I just don't like to see efforts of hundreds if not thousands of volunteers are rolled into a closed source application and distributed for the profit of a couple of people who pat themselves on the back because they got their next car/house/whatever for free.
This is why I prefer GPL over BSD/MIT.
That sounds no different from "code being used by some guys you don't like" to me, to be honest. If some company took my permissively licensed work and turned it into a commercial product, why would I take issue? I put my work out there for the betterment of all, and it is still bettering the world even in its new form. I have no complaints with that.
In fact, it's very different. You, as a single person might not care about a patch you contributed, or a small utility you have written. However, not everyone thinks like you (e.g.: Me, as Fig. 1a).
When you put all this spectrum of views under a project, it becomes another thing to manage these expectations and what people want from the project in the end. When big shifts start to occur, people will react differently.
When it's a project people love and contribute with the expectation of keeping things the way it's, and the things change, people won't be happy. See: Go's opt-out by default telemetry proposal, HashiCorp's and Docker's license changes, Google's persistent push to block ad-blockers, Microsoft's breaking of VSCodium in subtle ways, etc.
So it's much more than you and your code, esp. in projects like these. I think licensing them with licenses allowing rug-pulls (esp. under community itself), is a red-flag in many cases.
I also put the code I develop myself out there for the betterment of all, but it's licensed with GPL, because I don't want someone take and run away with it for "betterment of themselves rather than everyone". Now, you might not agree with me, and I respect that, but that's the terms I put on my code. As I always say. If you like it that much, reimplement it. I don't care.
Conversely, I contribute to a project which allows no GPL code, because it's designed to be both open, and be customized and closed at the same time. We put it out very openly in the beginning, because that license is a requirement for the use case we (as in ~10 countries) have, and MIT is the best one for our use case.
...but, Ladybird is not that. The project tries to build an important, foundational commodity item. Allowing it to be taken private is a mistake, IMO.
I think the issue isn't the potential forking, but that the potential fork may become a dominant and closed one.
If one values the web being somewhat open/less monopolistic, an open source web browser would be more appealing.
I have faith in the Ladybird browser project to avoid such a situation though.
It supports capitalistic predatory tactics that erode our society. Better to exclude them...