Citable: quotable in opinions and templates
Every source here meets all four criteria. The Since column shows the length of each record, and any independence concern, conflict of interest, or usage limit is in the source's section under Source notes.
The table lists 23 sources: 12 people and 11 publications.
| id | Kind | Source | Focus | Since |
|---|---|---|---|---|
alice-ryhl |
person | Alice Ryhl | Tokio and async design, Rust for Linux, smart pointers and in-place init | 2020 |
anssi-rust |
publication | ANSSI: Secure Rust Guidelines | Secure development, unsafe, FFI, tooling for security-critical software |
2018 |
awesome-rust |
publication | awesome-rust | Curated crate and tool list | 2014 |
blessed-rs |
publication | Blessed.rs | Hand-picked default crates by task | 2022 |
burntsushi |
person | Andrew Gallant: burntsushi.net and the Jiff design documents | Error handling, regex and text search internals, datetime API design | 2014 |
corrode |
person | Matthias Endler: corrode.dev and endler.dev | API design, defensive programming, standard library pitfalls, compile times | 2017 |
fasterthanlime |
person | Amos Wenger: fasterthanli.me | Long-form deep dives: async, networking, compilation, serialization | ~2019 |
ferrous-systems |
publication | Ferrous Systems blog | Embedded and safety-critical Rust, compiler internals | 2018 |
lib-rs |
publication | lib.rs | Quality-ranked crate index | 2018 |
matklad |
person | Alex Kladov: matklad | Project structure, xtask, testing, compiler and IDE architecture |
2017 |
niko-matsakis |
person | Niko Matsakis: Baby Steps | Borrow checker and trait solving, async design, language direction | 2011 |
nnethercote |
person | Nicholas Nethercote: The Rust Performance Book and blog | Program and compiler performance, profiling, allocations, build times | 2020 |
predrag |
person | Predrag Gruevski: predr.ag | SemVer and API compatibility, sealed traits, Cargo features | 2022 |
ralf-jung |
person | Ralf Jung: Ralf's Ramblings | unsafe and undefined behaviour, Miri, aliasing and the memory model |
2015 |
raph-levien |
person | Raph Levien and posts on the Linebender blog | 2D graphics and GPU compute, UI architecture, SIMD | 2017 |
rust-blog |
publication | Rust Blog and Inside Rust | Release announcements, language and compiler status, security advisories | 2014 |
rust-docs |
publication | Rust documentation: the Book, Reference, Rustonomicon, Edition Guide, Cargo Book, Clippy, and std |
Official documentation: language, Cargo, lints, and the standard library | 2015 |
rust-patterns |
publication | Rust Design Patterns | Idioms, design patterns, and anti-patterns | 2015 |
sunshowers |
person | Rain: sunshowers.io | Async cancellation, testing and cargo-nextest, Unix process behaviour |
2020 |
this-week-in-rust |
publication | This Week in Rust | Weekly newsletter aggregation | 2013 |
tokio-blog |
publication | Tokio blog and tutorial | The Tokio runtime, axum, tracing, runtime tooling | 2017 |
tweede-golf |
publication | Tweede golf blog | Embedded and async Rust, memory-safe infrastructure, compiler work | 2019 |
yoshua-wuyts |
person | Yoshua Wuyts | Async and effects design, iterators, structured concurrency, WebAssembly | 2016 |
Source notes
alice-ryhl: Citable
Citable on async and Tokio design, and on the Rust for Linux abstractions, from a Tokio maintainer.
- Longevity: Rust writing since 2020-08-15, at one to three posts a year. The longest gap in the last three years is about eight months, from 2023-11-01 to 2024-07-11.
- Depth: "Actors with Tokio" works through handles, backpressure, and shutdown.
"Async: What is blocking?" gives a measurable rule for how long a task may run between
.awaitpoints. - Cite: The async and Tokio posts for practice.
The 2024 to 2025 posts are RFCs and design write-ups for the Rust project, such as
#[derive(SmartPointer)]and in-place initialization, so cite them for design, never as stable Rust. - Re-evaluate: The latest post is from 2025-11-05. If nothing follows by 2026-11-05, check whether the design writing continues elsewhere before demoting.
anssi-rust: Citable
Citable for security.md: a government security agency's rule-and-rationale guide, maintained since 2018.
- Longevity: First commit 2018-12-13, with content changes through 2026-04-07.
- Depth: Each rule states a requirement and its rationale, with examples, but no measurements.
- Cite: Rules by their ID.
The guide calls itself unstable and names no Rust version or edition, so check a rule against
rust-docsbefore an opinion rests on it.
awesome-rust: Citable, Discovery-only.
A curated list of crates and tools since 2014-07-17, still taking additions in 2026-10. Its contribution rules gate entries on popularity, such as 50 GitHub stars or 2,000 downloads, not on review.
blessed-rs: Citable, Discovery-only.
A hand-curated guide to default crates, maintained by Nico Burns since 2022-03-13, with updates through 2026-08-03. It makes editorial calls between crates, so follow each to the crate's own material and a roster source.
burntsushi: Citable
Citable on error handling, regex and text search, and datetime design, under the dormancy exception.
- Dormancy: The blog's latest technical post is from 2023-07-05.
The writing continues in the Jiff documentation:
COMPARE.mdgained new benchmarks on 2026-01-05 and an updated comparison withtimeon 2026-02-06, both written by Andrew Gallant. - Depth: "Regex engine internals as a library" is a guided tour of the
regex-automatadesign. "Error Handling in Rust" and "Using unwrap() in Rust is Okay" reason from invariants to rules. - Conflict of interest: Author of
regex,ripgrep, andjiff. Never cite Andrew Gallant alone on adoptingjiffoverchronoortime. - Cite: "Error Handling in Rust" dates from 2015, before
?and the error crates in use today, so cite it for the reasoning, not its code. - Re-evaluate: If the Jiff documentation goes a year without new writing.
corrode: Citable
Citable on practical Rust, with a consultancy conflict on whether to adopt Rust at all.
- Scope: Covers both corrode.dev and Matthias Endler's personal blog, endler.dev, where the Rust writing goes back to 2017.
- Depth: "Tips for Faster Rust Compile Times" is practical and measured. The corrode posts on standard library sharp edges and defensive programming give rules with code.
- Conflict of interest: corrode is a Rust consultancy that sells migration, training, and mentoring.
Several posts argue for adopting Rust, so never cite it alone on that question.
Endler also maintains
lychee, the link checker this repository uses. - Cite: The technical posts. Most endler.dev posts since 2026 are on careers and craft, which are out of scope.
fasterthanlime: Citable
Citable on long-form technical articles, text only.
- Scope: Articles only. The videos are out of scope. Some articles start as sponsor early access, so cite only an article that's public.
- Longevity: Articles since 2013, with Rust the main subject since about 2019. The latest is from 2025-12-31, which keeps the source inside the dormancy line until 2026-12-31.
- Conflict of interest: Funded by sponsors, and articles promote Amos Wenger's own crates, such as
facet. Never cite the source alone on adopting one of them. - Re-evaluate: If no public article appears by 2026-12-31.
ferrous-systems: Citable
Citable on engineering posts, with a vendor limit.
- Depth: "Query cycles: A compiler murder mystery" traces a hung build to three interacting query-cycle bugs.
- Independence: Ferrous Systems sells Ferrocene, a qualified toolchain, with training and consulting. About half of the 2025 to 2026 posts are product announcements, events, and hiring, and engineering posts end with sales links.
- Cite: Engineering posts for how something works. Never cite it on adopting Ferrocene, or on whether a project needs a qualified toolchain.
lib-rs: Citable, Discovery-only.
An alternative crates.io front end, announced 2018-06-04 and maintained by one person. It ranks crates by reverse dependencies, maintenance, and documentation, as its About page describes, which helps find candidates but isn't a recommendation.
matklad: Citable
Citable on project structure, xtask, testing, and software design.
- Longevity: About 240 posts from 2017-03-12 to 2026-10-07.
- Cite: The Rust posts and the general design posts that apply to Rust. Most posts since 2024 are on Zig or general craft, so an opinion on a Rust detail needs a Rust post.
niko-matsakis: Citable
Citable on language design and direction.
- Longevity: Since 2011-12-02, with 22 posts in 2025 and the latest on 2026-10-14.
- Depth: Design reasoning on the borrow checker, trait solving, and async.
- Cite: For how the language works and where it's going. Most posts are proposals, such as "Battery packs", so never cite a proposal as current Rust. Use a "Coming next" note for a proposal.
nnethercote: Citable
Citable on performance, with measurements in both the book and the blog.
- Scope: Covers The Rust Performance Book, first published in 2020-11, and Nicholas Nethercote's blog.
- Longevity: The book has updates through 2026-04-23, and the blog runs from 2021 to 2026-09-30. The longest gap in the last three years is about nine months, from 2024-03-06 to 2024-12-19.
- Depth: The Heap Allocations chapter works from DHAT output to a general rule.
"How much code does that proc macro generate?" measures the code
serde's derive generates.
predrag: Citable
Citable on SemVer and API compatibility, with a conflict on cargo-semver-checks.
- Longevity: Rust writing since 2022-02-03, and the latest post is from 2026-08-15.
- Depth: "A definitive guide to sealed traits in Rust" and the posts on how Cargo features break compatibility are practical and exact.
- Conflict of interest: Author of
cargo-semver-checks, which many posts are built around. Never cite Predrag Gruevski alone on adopting it. - Cite: Not the 2026-04-01 or other April Fools posts.
ralf-jung: Citable
The reference on unsafe Rust semantics, undefined behaviour, and Miri.
- Longevity: Since 2015-10-08, and the latest post is from 2026-03-13. The longest gap in the last three years is about six and a half months, from 2023-06 to 2023-12.
- Cite: For
unsafecode and its rules. Where a post describes a proposed model, such as Tree Borrows, say whether the Reference has adopted it.
raph-levien: Citable
Citable on graphics, GPU compute, UI architecture, and SIMD, with the writing moved to the Linebender blog.
- Dormancy: The personal blog's latest post is from 2025-03-21. The writing continues on the Linebender blog, where Raph Levien wrote "A plan for SIMD" (2025-06-06), "Linebender in 2026 Q1" (2026-04-19), and a post on hyperbezier curves (2026-08-08).
- Accuracy: Publishes retrospectives on failed or replaced projects, such as the xi-editor retrospective.
- Conflict of interest: Leads the Linebender projects, including Xilem, Vello, and
kurbo. Never cite Raph Levien alone on adopting one of them. - Cite: Not the 2023-04-01 April Fools post, "Moving from Rust to C++".
rust-blog: Citable
The Rust project's canonical record of what shipped in each release.
- Cite: Release announcements for what changed and when. Inside Rust posts on process and governance make no technical claim.
rust-docs: Citable
The Rust project's official documentation.
- Accuracy: The Rustonomicon says it's incomplete in places, and that the Reference is more correct where the two disagree.
- Cite: The Reference before the Rustonomicon on language rules, and the Book for the idiom it teaches. Check the Book's stated Rust version before citing a version-specific claim.
rust-patterns: Citable, Corroborate.
Marked for uneven depth: community-written, maintained, and shallow in places.
- Longevity: Since 2015-08-30, with a new pattern on 2025-12-14 and changes through 2026-09-21.
- Depth: Each entry lists trade-offs, but argues in prose without measurements.
sunshowers: Citable
Citable on async cancellation, testing, and process behaviour, with a conflict on cargo-nextest.
- Longevity: Since 2020-08-22, and the latest Rust post is from 2026-06-02. The longest gap between Rust posts in the last three years is about ten months, from 2023-10-09 to 2024-08-04.
- Depth: "Cancelling async Rust" separates cancel safety from cancel correctness, with mitigations for
select!and Tokio's mutexes. - Accuracy: "Cancelling async Rust" fixed a code sample on 2025-10-24, crediting the reader who found the bug.
- Conflict of interest: Rain writes
cargo-nextest, and posts such as "Why nextest is process-per-test" argue for its design. Never cite them alone on adopting it. This repository's own checks run oncargo-nextest. - Cite: The Rust posts. Many other posts are personal essays, which are out of scope.
this-week-in-rust: Citable, Discovery-only.
A weekly newsletter since 2013-06-07, at issue 673 on 2026-10-14.
tokio-blog: Citable
Citable on how Tokio works, with a project limit.
- Depth: "Introducing dial9" works from production traces to scheduling delays and lock contention. The tutorial explains futures and the runtime in worked steps, but gives no date or Tokio version.
- Independence: A project's view of itself: since 2025, most posts announce TokioConf, Toasty, or Topcoat.
- Cite: How Tokio and axum work.
Never cite it on whether to adopt Tokio or any other tokio-rs crate, axum included.
One exception: cite it on using
tokio-util'sTaskTrackerandCancellationToken, once another roster source supports adopting Tokio. They're built in the tokio-rs/tokio repository and only extend Tokio's task API. Choosing them over Tokio's own types, such asJoinSet, picks between two tokio-rs options, so the project has no stake in the choice. The rest oftokio-util, such as its codecs, keeps the limit, because crates outside tokio-rs compete with it. Check a tutorial claim against the current docs.rs pages, because the tutorial names no version.
tweede-golf: Citable
Citable on engineering posts, with a vendor limit.
- Longevity: Rust posts since 2019-02-20, monthly through 2026-10-14.
- Depth: "Async Rust never left the MVP state" measures async state machine sizes and proposes compiler fixes.
- Independence: A Rust consultancy that sells engineering, training, and consulting. Some posts are client case studies or ask for funding, and many end with a sales link.
- Cite: Engineering posts for how something works. Never cite it on adopting a product or service it sells, or alone on adopting Rust.
yoshua-wuyts: Citable
Citable on async and effects design, from 177 posts since 2016.
- Depth: Mostly language design: effects, linear types, and in-place initialization.
A minority is practical, such as "A Survey of Every Iterator Variant" and the
futures-concurrencyposts. - Conflict of interest: Maintains
futures-concurrency, and took part in the keyword generics initiative. Never cite Yoshua Wuyts alone on adoptingfutures-concurrency, or on a proposal of their own. - Cite: For design and mechanism. Never cite a proposal as current Rust. Use a "Coming next" note.