GitHub shouldn't be a dependency for publishing Rust on crates.io
Summary
An article discussing the reliance on GitHub for publishing Rust packages on crates.io, arguing that it should not be a mandatory dependency.
Similar Articles
GitHub is sinking
The article argues that GitHub's reliability and culture have significantly declined since Microsoft's acquisition, citing uptime issues and 'slop' as reasons for developers to migrate to alternatives.
github and the crime against software
This article criticizes GitHub for frequent outages, poor reliability, and prioritizing AI features over fundamental infrastructure, arguing it reflects broader decay in big tech software services.
Why stdx is not on crates.io
Explains the rationale behind stdx not being published on crates.io, the Rust package registry.
Who Should Pay For Source Code Availability?
A blog post discusses the fragility of depending on centralized hosts like GitHub, explores forking and vendoring as mitigation strategies, and questions who should pay for reliable source code availability.
Dependencies should be fetched directly from VCS
The author argues that fetching dependencies directly from VCS (as done in Go) is more secure and easier to audit than using package registries with a publish step (as in Ruby, npm, PyPI).