Open Source Is Where Dreams Go To Die

Open source burnout is less a moral failing than a predictable outcome of a broken economic loop: maintainers pour in evenings and weekends, while users treat that volunteer labor like an entitlement—demanding fixes, new features, and immediate turnaround without paying, contributing, or even closing issues. The resignation of Linux on Apple silicon work—framed through Hector Martin’s exhaustion after years of reverse engineering hardware without documentation—lands as the clearest example of how “free software” can still carry an expensive human cost.

The discussion traces how that cost accumulates. A project often starts as a labor of love, then shifts into unpaid technical support as bug reports arrive like customer tickets. Communities can also escalate expectations beyond what maintainers can reasonably deliver: users ask for “more awesome” functionality, complain when it doesn’t match their ideal, and sometimes push for work the maintainer never built or even has the context to implement. Examples range from a developer who built emulators and faced relentless demands from an audience, to a maintainer who disabled GitHub issues for Laravel because the inflow of requests became unmanageable.

Financial sustainability is presented as the core mismatch. Most maintainers never see compensation despite powering billion-dollar companies and critical infrastructure. Sponsorships exist, but they’re described as a tiny minority solution—useful for some, not a systemic fix. Even when corporate sponsorship is discussed, the conversation highlights the friction: legal and marketing overhead can make it hard for companies to pledge money, while individuals often face the “damned if you do, damned if you don’t” dilemma of whether to pay at all.

The conversation also challenges the emotional contract behind open source. “It’s time to give back” can sound like a reverse entitlement—maintainers voluntarily released software, yet some users assume they’re owed something in return. Still, the practical takeaway is not to abandon open source, but to change behavior: say no, close issues, avoid “googleable” questions, and contribute when possible. One recurring theme is that many people underestimate how quickly a hobby becomes a job once maintenance and support dominate.

Several alternative models and tools are mentioned as partial relief. Open Collective and Sentry’s Open Source Pledge are cited as mechanisms to route money without forcing every project into a separate legal structure; the pledge model is described as a per-employee annual commitment rather than a complex redistribution algorithm. There’s also a broader “public source” mindset: release code for freedom and reuse, but don’t promise ongoing support—fork it, adapt it, and treat the maintainer’s time as finite.

By the end, the conversation widens beyond money to incentives and attention. The same way social media can feel like “shadowbanning” when creators don’t understand why audiences value their work, open source can feel crushing when popularity doesn’t translate into support. The most durable framing is pragmatic: build what you want, pick problems worth solving, don’t expect riches from free releases, and protect your time—because the system that extracts value from maintainers will eventually extract everything they have.