I get your point but that comes across as very callous to me, valuing a feature in software that benefits a small fraction of the most prosperous people in alre

I get your point but that comes across as very callous to me, valuing a feature in software that benefits a small fraction of the most prosperous people in already-prosperous countries over the health of a family. Consider reframing it: With a small donation you solve the problem for a family (where the problem is the risk that their children will die!), and you can solve it over and over just by repeating the action - it's the definition of scalability. You won't have to keep adding different colors of net to make that family safe. But there's always another software feature to be added, the job is never done - and when you add a feature it's only for the one package! If you want to do it again you have to start from scratch. Also, when you consider improvements in your projects, you no doubt consider both cost and impact. Compare the impact of the feature-add your donation might make in an open-source project, to the impact saving one or more family's lives.