Welcome to my lovingly hand-oxidized Rust monorepo, Repoxide—where dreams of simplicity oxidize into convoluted magnificence. Imagine GitHub, but after leaving it out in the rain overnight—yep, that's Repoxide.
crates/repoxide— The beating, rusted heart of a CLI/library that occasionally works (terms & conditions apply).apps/web/server— A rust-powered web API, still alive for now. (Web-scale guaranteed by the law of wishful thinking.)apps/web/client— A former VitePress/Vue frontend. Retired, but haunting the repo because deleting code is emotional.
Using https://github.com/yamadashy/repomix.git as the input workload and running 5 measured iterations per tool in default mode, repoxide still beat the TypeScript repomix CLI by a clear margin:
| Tool | CPU time | Latency | Peak RAM |
|---|---|---|---|
repomix (TS) |
6.393 s |
2.213 s |
444.9 MiB |
repoxide (Rust) |
1.434 s |
0.856 s |
78.0 MiB |
That works out to roughly 4.46x less CPU time, 2.59x lower latency, and 5.70x lower RAM usage for the Rust version on the measured host.
See BENCHMARKS.md for methodology, raw runs, tool versions, and the exact benchmark setup.
# For rusty help, type from the root:
cargo run -- --help # If stuck, yell at terminal louder
# If you're feeling confident and optimistic (I'm not):
cargo build --release # "Optimized" means bugs run faster
# Spin up my Docker-powered tech circus:
docker compose up --build # "But it builds on my machine..."- The current web-stack™️ (buzzword-compliant) lives bravely at
apps/web/server. - The original frontend (
apps/web/client) is now a relic, useful only as a warning to future generations. - Runs locally on
127.0.0.1:93because 92 was too mainstream.