4 ms·
I've recently left a Rust project and the maintainer's perfectionism was one part. From my observation, the causes tend to be: - Maintainers spread thin, putt
by epage 5y ago
I've recently left a Rust project and the maintainer's perfectionism was one part.
From my observation, the causes tend to be:
- Maintainers spread thin, putting more of a burden on contributors
- Some projects being critical and needing more attention and some taking themselves too seriously (dealt with a project whose CI took a couple hours for ~60 jobs because they exhaustively tested every combination.
- Maintainers who haven't learned to distinguish the important from unimportant.
- Contributors who don't realize their PR is a white eleplant (burdensome gift)
- Contributors who jump in with a PR without first seeing if it aligns with the project.
Most of this happens everywhere. Probably the more unique aspects to Rust are being spread thin, precedence of high quality crates, and that Rust gives a level of control that is addictive and effects other parts of projects.
- Mic92 5y agoYep. Second this. I also stopped contributing to rust-nix for the same reason. CI took forever. They wanted changelogs for everything but as soon as another PR was merged it would result in a merge conflict. Whenever I need a libc function not available in rust-nix I just add the abstraction to the project itself - this way I also don't have to care about someone else breaking my code by changing types.
- epage 5y ago> They wanted changelogs for everything but as soon as another PR was merged it would result in a merge conflict. I'm tempted to move to fragments that a changelog is generated from to avoid conflicts. I just haven't gotten around to exploring what tooling is out there.