this post was submitted on 02 Apr 2024
72 points (95.0% liked)
Programming
17351 readers
328 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is it really cheaper for the mega-corps to have their own fork instead of pay Redis for a license? Or are they just capitalizing from loud open-source advocates who are OK working for free for mega-corps because they are principled?
CC BY-NC-SA 4.0
It's worth remembering a lot of these megacorps do employ people directly to work on FOSS projects. Here's a quick and lazy example involving AWS
https://redis.com/blog/redis-core-team-update/ but Red Hat and others do the same.
I'm not a fan, and it feels almost as if by employing and embedding people in these projects they look to exert control over them. Realistically, I don't see that as any different than if they were paying money directly for the same control. Except this way FOSS still has benefits after the license change.
I'd say paying money is not as effective at influencing a project as embedding developers is.
In terms of bang for the buck, I'd absolutely agree. It's only when a company fully depends on the income of a single client, or closely aligned few, that this becomes a question.