How to Speed Up Your App With rust-anything
Your app feels slow, and a full rewrite in Rust sounds like a good way to break everything you have built. There is a middle path — move one piece at a time and prove it still gives the same answers, without writing any Rust yourself. That is what rust-anything is for.
The trick is an answer key. rust-anything runs your old code and saves every answer it gives, even on weird inputs. Claude Code then rewrites the slow part in Rust and cannot move on until every answer matches. Same product, slow part up to 20x faster.

What You Need
- Claude Code, already installed.
- A project in Python, JS, TS, Go, Ruby, Java or C.
Tutorial
- Open Claude Code in your project folder. Any of those seven languages works as the starting point.
- Paste this prompt, then restart Claude Code when it tells you to. It installs Rust first if you do not already have it.
```
install Rust if I don't have it, then run cargo install rust-anything and rust-anything setup. Tell me when to restart you.
```
- Point it at the problem with this prompt. It starts by hunting for the slowest part of the app.
```
My app feels slow. Use rust-anything to find the slowest part and move it to Rust
```
- Watch it find the slow spot, write the Rust, and check every answer. The rest of your code stays exactly the same.
- Give it real user inputs. This is the step everyone skips — it only checks what is in the answer key, so real inputs are what make that check worth anything.
- Ask for a benchmark before you ship. You see old versus new speed side by side.
```
Bench it with rust-anything and tell me whether to ship it.
```
- Ask for the whole app in Rust, one piece at a time. It proves each piece behaves the same as it goes.
```
Rewrite this whole app in Rust with rust-anything, piece by piece, and prove it behaves the same
```
Wrapping Up
You now have the whole loop: build the answer key, rewrite only the slow part, benchmark before you ship. Start with the single slowest piece of your app and leave the rest of the codebase alone. If the benchmark says no, the original code is still untouched.
Does this still work?
Nobody's checked yet
Sign in to tell everyone how it went.
Continue with GoogleBe the first — one tap saves the next person an hour.
It takes 3 reports in 30 days to set the status.
More shares you might like
NewsAnthropic Hackathon Winner Open-Sources Full Claude Code SetupCalvin · 1d · 34 views
AIHow to Install Hallmark, the Anti-Slop Design SkillCalvin · 2d · 41 views
ToolsHow to Claim GoPay Balance From IM3 PointsCalvin · 3d · 45 views
ToolsHow to Claim 10k–15k GoPay Coins From WeTVCalvin · 4d · 48 views
AIHow to Polish AI Academic Writing With Academic HumanizerCalvin · 6d · 57 views
ToolsHow to Start Amazon Affiliate Marketing From IndonesiaCalvin · 6d · 67 views
Comments
Join the conversation — sign in to comment.
No comments yet — start the conversation!