> it is not okay to consider that this labor fell from the sky and is a gift, and that the people/person behind are just doing it for their own enjoyments.
I am. I enjoy making things, and it's even better when others enjoy them. Just because you have expectations that you should be compensated for everything line of code you write; doesn't make it ubiquitous, nor should your expectations be considered the default.
I'd argue If you're creating and releasing open source with the expectations of compensation, you're doing it wrong. Equally, if you expect someone creating open source owes you anything, you're also part of the problem, (and part of why people feel they deserve compensation for something that used to be considered a gift).
All that said, you should take care of your people, if you can help others; especially when you depend on them. I think you should try. Or rather, I hope you would.
My apologies - you’re correct. I didn’t mean that as “you should never expect anyone to have contributed code for free/the pleasure/for the puzzle solving aspect”. I do it all of the time.
I meant - it’s unfair to consider that because this labor “fell from the sky”, you should just accept it - and as others have said, in the case of projects that become popular, that the burden should just automatically fall on the shoulders of someone who happened to share code “for free”.
If/when someone ends up becoming responsible for work they hadn’t necessarily signed up for (who signs up for burnout?) - it’s ok/necessary/mandatory to see how everyone (and or Nvidia/Google/OpenAI etc) can, like, help.
My insistence is on the opt-out nature of this so that people who would be ok being compensated don't have to beg.
Consider how the xz malware situation happened [0]. Or the header & question 8 from the FAQ for PocketBase [1].
I agree with you, but I do think we have a bit of a problem in which an open source creator makes something and then suddenly finds themselves accidentally having created a load-bearing component that is not only used by a lot of people and companies, but where people are demanding that bugs be fixed, etc., and we lack great models for helping transition it from "I do this for fun, might fix the bug if I ever feel like it" to " I respect that this has become a critical dependency and we will find a way to make it someone's job to make it more like a product".
I gather that the open source maintainers who have found themselves in this situation sometimes get very unhappy about it, and I can see why -- it's not like they woke up one day and suddenly had a critical component on their hands, it kind of evolved over time and after a while they're like "uhoh, I don't think this is what I signed up for"
I'm pretty sure you didn't wake up at 5am to an urgent issue. Because I did last night, and for sure __MY WIFE__ expects me to get paid for it!!
In general, people's time is not free if only because they have rent/mortgage, food, transportation, medical bills, education, etc.
> I'd argue If you're creating and releasing open source with the expectations of compensation, you're doing it wrong.
I think this is a little unfair, given that many (especially younger maintainers) get into it for portfolio reasons where they otherwise might struggle to get a job but stick around because of the enjoyment and interest. It still sucks that so many big orgs rely on these packages and we're potentially experiencing a future when models trained on this code are going to replace jobs in the future.
I think a lack of unionisation is what puts the industry in such a tough spot. We have no big power brokers to enforce the rights of open source developers, unlike the other creative industries that can organise with combined legal action.
thanks grayhatter. well said. been programming for 20+ years never earned a dime from it dont want it. its a silly assumption that everyone's motivation is money. this is very far from the truth.
Agreed. I do this too.
Redistributing unwanted funds would be a good chore to have to do!
I think this is the piece so many that are stuck in the hustle culture mindset miss, and why they are so quick to dismiss anything like UBI or a strong social safety net that might “reduce people’s motivation”. There are many many creative, caring people that are motivated to create things or care for each other for the sake of it, not for some financial reward. Imagine the incredible programs, websites, games, crafts, artworks, animations, performances, literature, journalism, hobby clubs, support groups, community organizations that would spring into existence if we all just had more bandwidth for them while having our baseline needs met.
Would it be chaotic? Sure, in the same way that open source or any other form of self-organization is. But boy it sounds a whole lot better than our current model of slavery-with-extra-steps…