- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
At first I was sceptical, but after a few thought, I came to the solution that, if uutils can do the same stuff, is/stays actively maintained and more secure/safe (like memory bugs), this is a good change.
What are your thoughts abouth this?
And how does this hurt all of us who use it for open source projects?
Competitive improvements the company makes make be kept secret, re packaged, and sold without making contributions to the src code.
Basically embrace, extend, extinguish
Ideas can only be patented, not copyrighted. If a company designs something novel enough to qualify for a patent, and so good that people willingly pay for the feature, that’s impressive, and arguably still a good thing. If instead they design a better user experience, or an improvement in performance, the ideas can be used in open source, even when the code cannot be.
@prime_number_314159 @thedeadwalking4242 this is how Google killed RSS
Patents kill innovation. No one should be granted rights to a concept purely because they got to it first. It’s still really.
I didn’t even say anything about copyright or patent?
Imagine a contributor of the project. He would have been fixing the bug for free and give the work to the public project. Right before he submits the code change, he sees an ad from a big tech bro: “Hiring. Whoever can fix this bug gets this job and a sweet bonus.” He hesitated and worked for the company instead.
Now that he is the employee of the company. He can’t submit the same bug fix to the open source project because it is now company property. The company’s product is bug free, and the open source counterpart remains buggy.
means it can also be captured by a corpo takeover and taken private
It can be forked by anyone, but what is already out there will always be there.
To give you an example, if git was under the MIT license instead of GPL , then Microsoft can silently add incompatible features to GitHub without anyone knowing. The regular git client appears to work for a while. Then they start advertising msgit with some extra GitHub features and shortcuts. Once they get to 50% adoption they simply kill the open source version off.
If GitHub required a special client to be installed tomorrow… I would have to concede and use it. It’s GPL that stops that because everyone has to get every new feature.
When Slack was first rolling out the dev team in my office of 50 people we all hated it. Thankfully it had an IRC bridge so we could use Slack through IRC. It was seemingly the same experience as before except more business users were in the chat rooms. Once the Corp side of the business were onboard, they dropped IRC support, forcing us to use their clients.
Now it doesn’t matter that rules or laws or privacy invasion they do. They have captured the companies communications and can hold it hostage.
I’ve seen it again and again. When is the last time you downloaded an MP3 file?
Until you’re left with choosing between an abandoned open source version and an up to date closed source blob.