why-not-rustlisted

Evaluate whether an existing project, service, subsystem, or migration RFC should adopt Rust. Compare staying, adopting an existing native tool, extracting a Rust kernel, replacing one component, and full migration through evidence-gated performance, safety, cost, compatibility, and delivery analysis. Produce a clear STAY / EXTRACT / PARTIAL / MIGRATE recommendation plus APPROVE / REJECT / DEFER–MEASURE authorization and a self-contained bilingual HTML report. Covers servers, CLIs and libraries as well as desktop applications — Electron, Tauri, Qt, AppKit and native Mac apps — including whether to keep an Electron shell and put Rust only at the OS seam. Use for questions such as “should we rewrite this in Rust?”, “would Rust make this faster?”, “should our Mac app be Rust?”, “is Tauri worth it over Electron?”, “评估迁移 Rust”, “要不要用 Rust 重写”, “桌面应用要不要换 Rust”, “why not rust”, or when reviewing a Rust migration RFC.
xiaotonng/why-not-rust · ★ 2 · API & Backend · score 70

Install: claude install-skill xiaotonng/why-not-rust

# why-not-rust Price a Rust decision instead of cheering for either stack. Treat every irreversible rewrite as a claim that must beat funded alternatives on the same measurable target. Say `MIGRATE` plainly when the case is real; say `DEFER–MEASURE` when the decisive evidence does not exist. Twenty worked reports produced by this method — ten desktop applications and ten systems projects, each pinned to a public commit — are published at <https://github.com/xiaotonng/why-not-rust/tree/main/examples>. Eight of them are also condensed into `references/case-library.md` as citable precedents. ## Operating principles 1. **Name the requirement first.** Start from an SLO, cost, safety, distribution, or correctness gap—not from a language preference. 2. **Compare like with like.** Separate language effects from redesign, algorithms, databases, caches, runtime versions, and baseline age. 3. **Take the smallest sufficient step.** Compare stay/adopt/extract/component/full; choose the first reversible option that meets the target. 4. **Keep unknown distinct.** Missing evidence yields `DEFER–MEASURE`, not a categorical pro- or anti-Rust claim. 5. **Test both biases.** Challenge migration hype and status-quo comfort with the same rigor. ## Files Resolve the directory containing this `SKILL.md` as `<skill-root>`. All paths below are relative to that directory, even while the shell is inside the repository being assessed. | File | Load when | |---|---| | `references/dim