But wait, I thought fame and accomplishment and helping lots of people were supposed to be enough for software authors, that somehow making people pay for software was evil, that it's OK if everyone just copies your source code and uses it, that an Open And Free Internet would be self-sustaining?
Making people pay for software might still be evil, but supporting software with teaching how to use it, documenting it, publishing books about it, making conferences, supporting it is what I think is a reasonable way for oss spirited souls to make money.
SQLite comes as an example - while completely free, public-domain, what might (I don't know for sure) be making money for the three people behind it is the extensive test suite, various other extensions (compression, security) and possibly support/integration/customizations for specific needs (less memory/cpu usage, or who knows what..)
When you buy a dinner at a restaurant, the chef ought to be compelled to share the recipe? No one forces you to eat at restaurants or use software. You are free to make your own.
Free until Apple decides to stop offering it. Or if they stop allowing users to install the software you develop. Or if future versions are released with onerous, unacceptable licensing terms.
When you use proprietary software, you are at the mercy of the company who distributes software to you.
Just one of many obvious examples that plenty of tools are available "allowing them the freedom to improve their lot." Nobody is stopping them, nobody is "keeping your users under your thumb". Improve your lot? do it yourself, or pay the engineers accordingly.
Oh, sure, Apple et al can change their minds and charge outrageous fees and demand outrageous licensing terms. Nonetheless, lots of affordable tools are available.
And before you take the opposing view any farther: I come from an era & mindset of building advanced computers from scratch. I reject the argument you offer of "by not giving them the source code you are [oppressing them]", because I'm trained in building computers starting from sand, and writing software starting with toggling in op codes with manual switches. I've written format converters (with no guiding documentation) to overcome the bounds you imply.
If you want someone to put in the effort to create complex software, maybe you should understand that they should be paid for that effort - one price to use it, and a higher price to get the detailed source code. If you're paying the price of a few cups of coffee to use it, heck yeah you're not getting the complete body of work a team spent years creating.
Rhetorical question: If nobody is stopping them, there is no harm in giving them the source code, right? So why don’t you?
> I've written format converters (with no guiding documentation) to overcome the bounds you imply.
Please do not assume that everybody should be like yourself.
> If you're paying the price of a few cups of coffee to use it, heck yeah you're not getting the complete body of work a team spent years creating.
There’s an easy way to rectify this – just don’t call it selling. Call it renting, which is what it practically is. The thing which I get when I buy software today is by no practical definition my property: its utility is deliberately limited by the manufacturer, and I am both legally and practically prohibited to extend that limit or repair it.
/sarc