A sad day for Rust

The author describes a ontroversy over the use of unsafe code in a popular web framework package.

@jmwright Also shows how dependence on just one project is super dangerous.

Obviously, it doesn't help anyone when a library just straight-up goes unmaintained, but I do find it important that the Rust community rejects libraries with bad code quality. The worst-case scenario for me would be an ecosystem like JS/NPM where dirty hacks get published indistinguishably from the rest.

Maybe a metric on showing the percentage of unsafe code in a library (with a big, fat disclaimer that this may not mean anything) would help with that.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!