Why do common Rust packages depend on C code? (2023)
Summary
The article explores why many common Rust packages have dependencies on C code, likely discussing technical reasons and implications for the ecosystem.
Similar Articles
GitHub shouldn't be a dependency for publishing Rust on crates.io
An article discussing the reliance on GitHub for publishing Rust packages on crates.io, arguing that it should not be a mandatory dependency.
Memory safety CVEs differ between Rust and C/C++
An analysis of how memory safety CVEs are reported differently in Rust vs C/C++, arguing that Rust's design reduces certain classes of vulnerabilities even when bugs exist.
C for Rust Programmers
A blog post by a Rust programmer detailing quirky C language behaviors learned while self-teaching C, including booleans via <stdbool.h>, null-terminated strings versus Rust's length-prefixed &str, and related memory trade-offs. It serves as a practical companion guide for developers transitioning from Rust to C.
The Two Factions of C++
The article discusses the internal conflicts within the C++ community regarding ABI breaks and memory safety, alongside government warnings and big tech companies shifting towards Rust.
How (and why) we rewrote our production C++ frontend infrastructure in Rust
NearlyFreeSpeech.NET rewrote their production C++ frontend infrastructure (nfsncore) in Rust, a critical system that handles routing, caching, and access control for all incoming requests. The migration was motivated by Rust's safety guarantees, performance, ecosystem strength, and the aging C++ codebase's limitations.