What's with the move to MIT over AGPL for utilities?
-
Squeek, squack. Your opinion is whack
lol grow up
-
I would understand if Canonical want a new cow to milk, but why are developers even agreeing to this? Are they out of their minds?? Do they actually want companies to steal their code? Or is this some reverse-uno move I don't see yet? I cannot fathom any FOSS project not using the AGPL anymore. It's like they're painting their faces with "here, take my stuff and don't contribute anything back, that's totally fine"
Or on the flip side, they want usage to be pervasive so they win. I mean come on man it's like "move this file" and "make this directory".
these applications aren't rocket science and providing them under a license that people will use outside of the hardcore Linux space is just good marketing.
-
I wohld agree, because you really downplay the scenario.
As soon as you accidentallt create something, which everyone starts to use or has an use case, then some Cooperation will copy that thing, make it better and make your community dissappear because there is the newer tool which you cant change the code of anymore and need to use a monthly subscription or something to even use.
So, it somehow seems like you're gaslighting yourself by downplaying the use case.
Mostly it will be small buisnesses and hobbyists, which I would like to code for them too. Especially when they are nice and friendly. But as soon as Microsoft, Google, Meta, Amazon gets hands on it and sees a potential to squeeze money through it by destroying it, then they will surely do it.
This can happen.
The flip side is noone uses it. I've never worked at any company that allowed even lgpl code to be used. If it has a commercial license we'll buy it, if not...find another tool.
-
Does anyone use MPL anymore? Is it a decent middle ground or the worst of both worlds?
For what use case?
-
Bruh instead of all this speculation, you guys could have just looked it up.
https://github.com/uutils/coreutils/discussions/4358#discussioncomment-8027681
There is a big difference between what someone says they are doing vs why they are actually doing it
-
lol grow up
Sorry, but I or rather many hate your Opinion.
Its ok if you dislike my Opinion about that. But I will show you, that many dislike your Opinion with a little fun and humour.
I believe that this has nothing to do with growing up, but I think thats your opinion you can attempt to follow.
-
This can happen.
The flip side is noone uses it. I've never worked at any company that allowed even lgpl code to be used. If it has a commercial license we'll buy it, if not...find another tool.
In my Company, we do use such code. But its mainly because we distribute our own Propriatary Linux OS
-
Yes. I did not say otherwise.
I get downvoted for stating a fact, and yet the only answer essentially agrees with why I said... shrugs
A glitch in the matrix.
Ok idk. Your message felt like it wants to explain why we shouldnt use GPL/lgpl
-
I edited my comment to better and more fully reflect my thoughts. It's hard to properly express myself when I've been as sick as I have been with bronchitis and possible pneumonia for the past 4 weeks.
Hopefully my comment now better reflects my thoughts.
I still feel like, the point where you say more people can use it and will use it, can create a dark pattern.
Imagine you create something and make people depending on it. Another cooperation copies it and advances it with a lot of money. Somehow, the ecosystem is so changed, that when you depend on that project, you need to use the newer version of the cooperation and soon they will paywall it heavily.
Then, your wish for people using the code as much as possible got nuked.
I assume that many scenarios will allow the usage of your old MIT project without relying on the new version of someone. But rare cases exist, where this happens. Its like predicting the 30th step in chess or smth. (Idk chess that well)
Its... unlikely that it will happen, but yeah. I can understand your perspective, but slowly going to AGPL sounds right.
-
I edited my comment to better and more fully reflect my thoughts. It's hard to properly express myself when I've been as sick as I have been with bronchitis and possible pneumonia for the past 4 weeks.
Hopefully my comment now better reflects my thoughts.
Had bronchitis as a child nearly every few weeks for years. All gone but sucks to have it.
Get well soon.
-
Sorry, but I or rather many hate your Opinion.
Its ok if you dislike my Opinion about that. But I will show you, that many dislike your Opinion with a little fun and humour.
I believe that this has nothing to do with growing up, but I think thats your opinion you can attempt to follow.
Lol even GNU and fsf failed at implementing gplv3 at all levels in Linux. And with gplv3 redhat gets awa with what they do. Also see recent agplv3 lawsuit. Gpl enforcement is real issue. If fsf wants why no create true copy left strong license no exceptions!
-
I write code for a living. I cannot, by any means, utilize a GPL library to support the needs of our customers and will either have to write my own replacement or dig to find something with less restrictions like MIT.
On many occasions, we will find bugs or usage gaps or slowdowns that can get pushed back to the MIT licensed open source cause we were able to use it in the first place. If your goal is to make sure your library gets used and gets external contributors, I don't see how GPL helps the situation as it limits what developers can even choose your library in the first place. If your goal is spreading the ideology that all software should be free, go keep banging your drum for GPL.
I work in a company that deals with both commercial and government (military) software. The government is becoming more and more fixated on the software supply chain, or sw dependencies so to speak.
Existing dependencies are largely getting a pass for now, but with each new one I need to give a justification for. This includes the license of that software. I can't use GPL at work.
-
System shared this topic
-
There is a big difference between what someone says they are doing vs why they are actually doing it
Well the dev said that he does not care about the license. He wanted to create a coreutils alternative with better concurency using Rust as a pet project. He had even stated that he was not interested in the MIT vs GPL drama, yet people here were acting like children over it.
People think it's some kind of Canonical evil master plan, yet it's just some random dude slapping a license on his cool new code, without really thinking about it. Also this conspiracy does not make sense at so many levels. For one Canonical would shoot themselves into their foot if they created their own proprietary coreutils, because admins would not want to deal with non-portable scripts. Also there are already the BSD utils, so if they wanted to create their own fork, they would have already done that by now. They won't because they prefer free labor from FOSS devs.
-
System shared this topic
-
Well the dev said that he does not care about the license. He wanted to create a coreutils alternative with better concurency using Rust as a pet project. He had even stated that he was not interested in the MIT vs GPL drama, yet people here were acting like children over it.
People think it's some kind of Canonical evil master plan, yet it's just some random dude slapping a license on his cool new code, without really thinking about it. Also this conspiracy does not make sense at so many levels. For one Canonical would shoot themselves into their foot if they created their own proprietary coreutils, because admins would not want to deal with non-portable scripts. Also there are already the BSD utils, so if they wanted to create their own fork, they would have already done that by now. They won't because they prefer free labor from FOSS devs.
The license matters. MIT allows for the embrace extend extinguish approach, or for companies to completely ignore contributions back to the main src.
Whatever he says he is doing doesn’t matter. In the long run a MIT license won’t be good. There’s a reason why the gnu core utils get so much work done on them. Because it’s required if you wish to use the code in your commercial applications
