The Rust project has a burnout problem
Burnout among core contributors to the Rust programming language is emerging as a serious problem, driven by constant review workload, high quality expectations, and a culture where people feel “nothing gets done unless I do it.” Commenters connect this to broader open source dynamics: unpaid or underpaid maintainers absorbing endless issues, PRs, and user demands, amplified by GitHub’s engagement-driven model and a lack of strong boundaries around time and responsibility. Many argue that healthier norms—clearer “no”s, better tooling and triage, explicit time limits, paid support, and governance that reduces individual heroics—are essential if Rust and similar large projects are to remain sustainable.
Scope of the Burnout Problem
- Many see the described experience as typical of large open‑source (“open contributions”) projects, not just Rust.
- Others argue Rust suffers more than peers, citing high ideals, rapid release cadence, complex compiler work, and a young, highly idealistic contributor base.
- Strong theme: burnout driven by caring, conscientious people in environments that feel uncaring or chaotic.
Main Burnout Drivers
- Sense that “if I don’t do it, it won’t get done,” especially for pet features or neglected areas.
- Review load: constant stream of PRs from inexperienced contributors; reviewers feel personally responsible for catching subtle mistakes that CI and tests can’t.
- Community expectations and “entitled users”: complaints, low‑effort issues/PRs, pressure for speed.
- Internal culture issues: conflict avoidance, difficulty saying “no” quickly, heavily bottom‑up decision‑making making coordination hard.
- Emotional over‑investment in volunteer work; contributors treat it like a second unpaid job.
Mitigations and Governance Ideas
- Personal boundaries: work hour budgets, treating paid OSS work like a job (no chronic overtime), accepting that some things won’t get done.
- Organizational practices: rotate review responsibilities, formal “hiatus” options, more people whose role is triage/“running interference” rather than coding.
- Technical/process solutions: stronger CI/lints where possible, higher testing requirements for PRs, clearer contributor guidelines, checklists for common subtle pitfalls.
- Community hygiene: closing low‑quality PRs, banning toxic users, moving questions off GitHub Issues to forums/mailing lists, using bots/actions for auto‑closing and sentiment filtering.
- Some advocate for more direct, even harsh, rejection of entitled behavior; others warn this can create toxicity and drive away good contributors.
Rust‑Specific Observations
- Rust is perceived as both slow to stabilize features and fast‑moving (6‑week releases), which can raise pressure.
- Companies do fund some core work, but reliance on emotionally invested volunteers remains high.
- Some worry about insularity and culture (including demographic and stylistic norms), potentially reinforcing groupthink and excluding different personalities.
Meta: Writing Style Debate
- Long subthread on the blog’s all‑lowercase style: many find it significantly harder to read and perceive it as inconsiderate; others see it as a valid aesthetic choice or deliberate “filter.”