I'm committing at least 10% of my GitHub sponsorships to other open-source Rust authors. I currently sponsor ~27 authors at $1 a month so a little short at the moment. Who should I look at? github.com/sponsors/robjtede

Not accurate. If you read the .zig and the .rs files side by side you’ll notice something - the original zig code and the new rust code looks basically the same, and that is intentional. It is a port.

Ubuntu 26.04 (Long Term Support) is shipping tomorrow… and Canonical has published an update on their quest to replace GNU CoreUtils with Rust-based re-writes. Highlights: - After developers raised “some serious concerns”, Canonical hired an external security research firm to evaluate the Rust re-writes (known as “uutils”). - That security firm quickly found 113 significant issues, with a large portion of them being severe security issues warranting a CVE. - Only some of those issues in the Rust re-writes have been fixed for the Ubuntu 26.04 release. - Repeat: Ubuntu 26.04 is shipping with significant known issues in the new Rust coreutils. - Some of the most critical Rust-Re-Written commands (cp, mv, and rm) were found to contain a large number of significant “Time-of-Check to Time-of-Use” issues, the kind of issues which create race condition vulnerabilities. The kind often exploited by hackers. - As such, cp, mv, and rm will not be shipping in Ubuntu 26.04. Even with their clear “it’s fine if Ubuntu 26.04’s rust re-writes contain significant bugs” policy… the issues with cp, mv, and rm were simply TOO severe. - Despite this undeniably disastrous rollout of the Rust-based rewrites of Coreutils, the Ubuntu team plans to ship the next release, in 6 months (26.10), with 100% of the GNU Coreutils replaced with the (currently comically broken) Rust re-writes. discourse.ubuntu.com/t/an-up…