Open source maintainers are increasingly burdened by escalating demands and dwindling resources. The "2025 State of Open Source" report reveals maintainers face growing user bases expecting faster response times and more features, while simultaneously struggling with burnout, lack of funding, and insufficient institutional support. This pressure is forcing many maintainers to consider stepping back or abandoning their projects altogether, posing a significant threat to the sustainability of the open source ecosystem. The report highlights the need for better funding models, improved communication tools, and greater recognition of the crucial role maintainers play in powering much of the modern internet.
Taner Şener, the creator of FFmpegKit, a commercial wrapper around FFmpeg for mobile development, announced that he's ceasing development and support. Due to complexities in maintaining FFmpeg across various architectures and operating systems, increasing maintenance burden, and inadequate revenue to justify continued development, he's chosen to shut down. Existing clients can continue using their purchased licenses, but future updates and support are discontinued. The core issue is the difficulty of sustainably supporting a complex project like FFmpegKit, even as a paid product, given the rapid pace of mobile development and the substantial engineering effort required for compatibility. While acknowledging the disappointment this will cause some users, Şener emphasizes the unsustainable nature of the project's current trajectory and thanks users for their support over the years.
Hacker News users discuss the author's decision to discontinue FFmpegKit, an iOS/Android FFmpeg library. Several commenters express disappointment, highlighting FFmpegKit's ease of use compared to alternatives like MobileFFmpeg. Some suggest the decision stems from the difficulty of maintaining cross-platform compatibility and the complex build process involved with FFmpeg. Others speculate about the author's motivation, including burnout or lack of financial viability. A few offer alternative solutions or express hope for a successor project. The lack of clear documentation for building FFmpeg directly is also a recurring concern, reinforcing the value of projects like FFmpegKit.
Summary of Comments ( 27 )
https://news.ycombinator.com/item?id=43077833
HN commenters generally agree with the article's premise that open-source maintainers are underappreciated and overworked. Several share personal anecdotes of burnout and the difficulty of balancing maintenance with other commitments. Some suggest potential solutions, including better funding models, improved tooling for managing contributions, and fostering more empathetic communities. The most compelling comments highlight the inherent conflict between the "free" nature of open source and the very real costs associated with maintaining it – time, effort, and emotional labor. One commenter poignantly describes the feeling of being "on call" indefinitely, responsible for a project used by thousands without adequate support or compensation. Another suggests that the problem lies in a disconnect between users who treat open-source software as a product and maintainers who often view it as a passion project, leading to mismatched expectations and resentment.
The Hacker News post "Open source maintainers are feeling the squeeze" (linking to a The Register article about the pressures on open-source maintainers) generated a moderate amount of discussion, with a number of commenters echoing and expanding upon the article's themes.
Several commenters highlighted the increasing demands placed on maintainers, particularly in popular projects. One commenter described it as a "thankless job" where maintainers are expected to provide free support and deal with entitled users. Another pointed out the discrepancy between the immense value open source provides to companies and the often meager (or nonexistent) compensation maintainers receive.
The topic of burnout was prominent, with commenters discussing the emotional toll of managing a project, dealing with demanding users, and the constant pressure to fix bugs and add features. One user shared a personal anecdote of stepping away from a project due to burnout, emphasizing the need for maintainers to prioritize their own well-being.
Funding and sustainability were also recurring themes. Commenters discussed various funding models, including GitHub Sponsors, donations, and corporate backing, but also acknowledged the challenges of securing consistent funding. One commenter suggested that companies relying heavily on open source should contribute financially, while another proposed a model where companies "adopt" specific projects and provide dedicated resources.
Some commenters shared their own experiences as maintainers, offering insights into the day-to-day challenges. One maintainer described the difficulty of balancing their own commitments with the demands of the project, highlighting the constant time pressure and the feeling of being "always on call."
There was also discussion about the role of the community in supporting maintainers. Several commenters emphasized the importance of contributing back to projects, whether through code contributions, documentation improvements, or simply by showing appreciation for the maintainers' work. One commenter suggested that even small contributions, like triaging issues or writing clear bug reports, can significantly reduce the burden on maintainers.
Finally, a few commenters mentioned the legal and security aspects of maintaining open source projects, pointing out the increasing complexity of licensing and the potential risks of vulnerabilities. One commenter emphasized the importance of having clear legal guidance and security protocols in place to protect both maintainers and users.
In summary, the comments on the Hacker News post reflect a widespread understanding of the challenges faced by open source maintainers. The discussion highlights the need for greater support, both financial and emotional, and underscores the importance of community involvement in ensuring the long-term sustainability of open source projects.