The editor: https://editor.graphite.art/

A non-exhaustive list of Rust usage.

This means that no matter how good (and fast) Clippy is, or how great the memory safety caused by the borrow checker is. The first language that’s taught in many universities is still Java. People use Javascript for everything and C++ is still used in planes. This is why I find it important to highlight and underscore which projects have tried Rust, how the process went and what they learned along the way.

This data structure seems efficient and interesting

Typo-squatting: using URLs is a false solution. "By making crate IDs longer, whether by namespacing within crates.io, GitHub organizations, or via domains, you only make it harder for users to remember them precisely, and thus harder to recognize typo-squatting."

Sandboxing can not be handled by the language itself.

It's the developer responsability to use crates on crates.io. It's an audit to make. Rust provides tool for it: cargo-vet, crates.io 90 day download plot, cargo chef or Nix to build isolation.

Also Rust itself does not have the resources for it at the moment. They simply can't. The compiler and std are primarily developed by volunteers, who don’t get anything out of it except for rare donations from other members of the community. The Rust project is not the same as GitHub or Linux. They don't have the same support.

We’re not nearly close to the level of security a centralized registry can provide. On the software side, in 2025 Rust teams made or piloted tools for typo squatting detection, dynamic build script analysis, and real-time code scanning. On the personal side, Rust Foundation hired on-call engineers in 2025 and a second infrastructure engineer in 2026. If that sounds overdue, well, they had net loss in 2023 – software isn’t cheap.

More efficient but this is typically the tool that should be used when needed :)

A list of available project

and the development is significant

In a recent analysis, Adam Harvey found that among the 999 most popular crates on crates.io, around 17% contained code that do not match their code repository.

How?

• buy compromised cookies or credentials
• typosquatting or misleading create names
• macros

How to solve?
Again, like Go: having a comprehensive standard library.

It should have: base32, base64, bytes, crc32 and crc64, crypto, gzip, hex, http, json, net, rand, regex, tar, tls, uuid, zip, zstd.

How to fix now?

• Use Dev Containers!
• Password manager for the SSH keys and secrets
• fetch the dependencies from source
• audit the dependencies: cargo-audit and cargo-vet

The post landed today on Lobsters

1. Implement the Copy trait
2. Take parameters by reference
3. Use the proper iterator
4. Have closures capturing by value also return the value

Declare identity to be used by other tools, so the information declaration process can be automated.
A bit sad that AI is the main branding of it.

Export to VCF is added: https://hachyderm.io/@ducks/116324991938693684

The related blog post https://jakegoldsborough.com/blog/2026/whoami-spec-declarative-identity/

They use common logic in Rust. The diagram is definitely interesting.

An introduction from unsafe to safe Rust lifetimes

1. Share immutable data in threads
2. Mutex while sharing mutable data

An recommended example is provided in the "[Fearless Concurrency]"(https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-In-Firefox-Quantum.html) post of Mozilla about the success they has in parallelizing the CSS renderer.

Comme les humains sont assez mauvais à créer des logiciels sans bugs, Rust est grâce au compilateur un très bon moyen d'en éviter un certain nombre.

A feedback about handling errors properly instead of a one big error enum.