It's indeed ridiculous how the world's trillion dollar private companies run on essential software that idealistic open-source maintainers build basically for free while scrambling to even make basic income.
I'm all for open ideals, but we shouldn't be as naive to ignore how stuff we build on these ideals - if offered completely free - will eventually almost exclusively profit only those private entities that best know how to use them, hide them in a 'proprietary chain' and use VC capital to invest more in PR, markting and sales than engineering to reap all the benefits off them.
Therefore, I think, the original problem was that most software wasn't automatically defaulting to a limited-commercial (e.g. business of > million revenue must pay for usage in their product) or AGPL licenses that would benefit all - by either allowing maintainers to get a share from the success the helped build, or making the resulting products build on top, instead of private profit, available freely to all.
> It's indeed ridiculous how the world's trillion dollar private companies run on essential software that idealistic open-source maintainers build basically for free while scrambling to even make basic income.
The most ridiculous thing is that idealistic open-source maintainers are still doing it, while this is being an established status quo for at least 30 years. Or maybe they have their incentive, and, while I don't find it palatable too, large corporations understands that. What's _your_ incentive in having such strong opinions about that ?
Agreed, and furthermore, I would imagine since some projects (thinking ghostty, linux, and others) are non-profits there are tax incentives for donating and supporting. Software stacks are still neglected, and that points to inefficiencies (companies and corps not valuing open source) and willful malice (hiding them in the "proprietary chain"), and just general abuse of the commons (take and don't pay).
AI has made the "hard" things more important. Everyone can now build an e-commerce website or demo, but the utilities, OSes, and browsers now serve as the base of those projects. They are beginning to be overwhelmed, whether it be through AI bug reports, exponential load on some platforms, or other indirect factors, and there isn't much relief in sight.
We need a large re-alignment of Math, Software and Sciences. I'm not elucidating anything new here, simply musing. Science and math workers can be focused on replication and application, and software expertise focuses on the "foundational" systems.
> idealistic open-source maintainers build basically for free while scrambling to even make basic income.
Maybe these maintainers could simply cease doing all this free work? There are other ways to make a living. Perhaps even doing the same thing but with better negotiation skills. No one is forcing anyone to do this. The reality is that if 100% of the tzdb and SQLite teams disappeared today, Microsoft and Google would have these projects back under stable operation before the weekend.
We cannot expect a realistic economy to arbitrarily compensate people who originally did not seek compensation without a lot of really bad side effects. Does anyone on HN have any actual evidence that the maintainers of truly load bearing infrastructure (billions of devices+) are genuinely struggling economically?
Maybe some countries could pay stipend to software developers who do that? I mean, this open source software enables other companies to produce cheaper software and to earn more money and they pay taxes from that money, so tiny bit of these taxes could also be redistributed back to some independent developers.
I only make MIT because, after a decade of GPL, I actually find lawyers and license bullshit more annoying. Just let me build stuff.
>e.g. business of > million revenue must pay for usage in their product
That happens with linux, if businesses don't want their supply chain to vanish.
But, hey, we are trying communism :)
I mean, it is called "Free software", it has been made purely for free.
Now AI has made software abundant, there really isn't any need to pay maintainers really.
Enterprises can just fork it, rebuild the software for their own needs and not contribute anything back.
Even if the license is AGPL, they ignore it anyway and it is unenforceable.
True. It's really cases like this that demonstrate the shortcomings of BSD/MIT licenses -- at least if you are of the position, that companies could and should contribute a sliver of profits back to the projects enabling that success.
(Much like contributing back in taxes for the infrastructure used and the educational system producing the qualified employees. But that may be a bridge too far for some of HNs readership :) )