1182
Unpopular Opinion
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Sep 2023
1182 points (92.5% liked)
Memes
45902 readers
1305 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
So, don't mistake this as me telling you you're totally wrong, because you definitely do have a point and it gets under my skin too (that's why I believe licenses like AGPL and, dare I say, SSPL should be used), but many of these companies actively contribute back to the open source software they're using.
and are hardly the only companies using FOSS; everyone from non profits to miliary systems use it. this meme doesn't really work when you take the whole picture into account.
Regardless of how you slice it, foss devs don't get fairly compensated for their work.
I have two diverging responses to this - one, if they're credited for their commits, in the purview of FOSS projects, they're compensated as much as they expect; two - that said, I would love to see FOSS projects get more love and financial support from the community - which is why watching the GODOT project has been exciting. I'm not much of a dev, and not in a position to contribute to what they're doing in code, but sending them some coffee money has been worthwhile.
TIL what that is.
... and [whistles], that's a doozy!
From https://en.wikipedia.org/wiki/Server_Side_Public_License:
I get what they're going for and I sympathize with the goal, but I'm not sure there's any software in the world that could comply with that license because it would have to release an entire container or disc image with nothing but SSPL software from the kernel on up. Does a SSPL-licensed kernel or httpd even exist?
They gotta want to do it I guess, lots of companies use like GPL code but don't tell anyone.
Even if they want to do it, can they? The Wikipedia article claims that every piece of software necessary to run the service would have to be licensed as SSPL. Not just to have its source code released in compliance with whatever other copyleft or permissive license it was under, but relicensed as SSPL. That means (assuming the Wikipedia article is accurate, anyway) you can't even run it on top of Linux and be in compliance with the license! You'd have to write your SSPL service for the bare metal hardware, or write an entire new SSPL-licensed OS for it.
So, without getting too into the specifics about SSPL because you and many of the critics of it I agree with in that it seems poorly thought out or too aggressive, I do think AGPL fails in some ways. Mongo and (I think) Elastic were both licensed under AGPL but made/changed to SSPL because of a perceived abuse by cloud services like Amazon. As for what exactly the cloud providers were doing that they perceived as wrong and what the best solution is I'm not too sure. It could be that Elastic's own managed version of its product wasn't getting any use because Amazon's was benefiting from economy of scale and vendor lock in ("hey, we already have everything on AWS, let's use AWS's Elastic offering") and if that's the case then it's not really a failing of software licenses and just a shitty and unfortunate situation.
One of the things libre software is trying to accomplish is letting anyone use it for anything and allowing competitors to monetize it is a valid use. It seems like Elastic and Mongo may have been trying to have a primary revenue stream be money from offering their own managed service and cloud providers were out competing with them. It's hard to not see this as them being a parasite that will take over the host and eventually kill them both because the devs of the product will stop getting compensation.
Some products (I think QT is another example) offer a GPL/AGPL version but for a fee will give you a more traditional license (non copy left) and this allows users to have a way to keep their own code closed source while providing revenue for the creators. Win win. AGPL was made to fix a loophole of putting a GPLed product behind a web interface and then saying "hey I'm not technically distributing anything so I don't have to release my source code." You'd think that most enterprise folks would pay but it seems like the cloud providers didn't need to because they found ways around AGPL or just didn't modify anything.
Like I said in another comment, no matter how you look at the situation, open source devs are getting taken advantage of. Enterprise customers should set the example and monetarily support the devs of open source software they use. While they do sometimes it's not the norm. Even within the same company you see mixed behaviors. Microsoft has been contributing code back to git and adding new features but also "stole" AppGet. They even interviewed the dev and asked specific questions about it. It's just scummy. It's a reminder that something being legal isn't automatically ethical or moral.