this post was submitted on 02 Apr 2024
1066 points (95.9% liked)
Programming
17668 readers
315 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 [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Exactly: I'm not mad about important things being run by volunteers -- arguably, that's a good thing because it means project decisions are made uncorrupted by profit motive -- but I am mad about the profit being reaped elsewhere on the backs of their free labor.
@grue @vzq this is such an interesting space. The general public has no idea how much of their software relies on open source code and voluntary community contributions. There have been so many attempts to figure out a way to compensate these maintainers, but it doesn't seem like anything has really become the defacto solution. Open Collective and Tidelift are the closest things I can think of.
@grue @vzq The key is that these folks are supposed to have both freedom & power to set direction independent of corporate shit, *and* compensation for their labor.
Argue-er here, chiming in. This statement could be interpreted as considering only half of the central relationship of capitalism. (Capitalism isn't just about deriving profit from the control of surplus, it's about the relationship between surplus and scarcity. Surplus doesn't mean shit if no one wants what you have.)
The decisions that volunteers make may not be motivated by the desire/ability to make profit, but they can be (and often are) motivated by the opposite; they have to account for the fact that their volunteer work is labor that isn't contributing to their survival -- aka, their day job. The demands placed on them by their other responsibilities will have to take precedence over the volunteer project.
In practice, this means they have to take shortcuts and/or do less than they would like to, because they don't have time to devote to it. It's not exactly the same end product as if it was profit-seeking, since that can tempt maintainers into using dark patterns etc, but they're similar.
Ideally, they would have all the money they needed, didn't have to have regular jobs, but also had families/friends/hobbies that would keep them from over-engineering ffmpeg.
To say this in a simpler/shorter way (TD;DR), their decisions can be motivated by the fact that they aren't making money from it, don't have enough time or resources to do everything they might want.
(Why is this so long?? I'm bored in the train, gotta kill the time somehow..why not say in 1000 words what I could have said in 100)
Interesting point! I'm not sure that that motivates the quality or type of decisions so much as the mere quantity, though. (In other words, I agree the pace of development suffers, but I'm not sure the quality of the end result does.)