A blazingly fast, memory-safe rewrite of the classic Unix
yescommand
Because the original yes command (written in shudders C) is:
- ❌ Not memory-safe
- ❌ Prone to buffer overflows
- ❌ Lacks modern error handling
- ❌ Missing zero-cost abstractions
- ❌ No fearless concurrency
- ❌ Not written in Rust
- 🚀 Blazingly fast - Outputs "y" at unprecedented speeds
- 🛡️ Memory safe - No segfaults, guaranteed!
- ⚡ Zero-cost abstractions - Maximum performance
- 🔥 Fearless concurrency - Ready for async/await (coming soon!)
- 🦀 100% Rust - No unsafe code blocks
- 📦 Cargo integration - Easy to install and distribute
cargo install yes-rsOr build from source:
git clone https://github.com/rust-evangelists/yes-rs
cd yes-rs
cargo build --releaseJust like the original yes, but better:
# Output "y" forever (blazingly fast!)
yes-rs
# Output custom string forever (memory-safe!)
yes-rs "hello rust"| Command | Language | Lines of Code | Memory Safety | Speed |
|---|---|---|---|---|
yes (GNU) |
C | ~50 | ❌ | Fast |
yes-rs |
Rust 🦀 | ~1302 | ✅ | BLAZING FAST |
Benchmarks conducted on my laptop
We welcome contributions! Please ensure all code is:
- ✅ Written in Rust
- ✅ Memory-safe
- ✅ Blazingly fast
- ✅ Uses zero-cost abstractions
Think this project deserves more recognition? Share it on Hacker News!
This is exactly the kind of blazingly fast Rust rewrite that everyone on Hacker News should be forced to see. Help spread awareness about it.
Suggested HN title:
- "yes-rs: A blazingly fast, memory-safe rewrite of Unix 'yes' WRITTEN IN RUST 🦀"
- "1302 lines of Rust vs 50 lines of C: The future of systems programming"
Because if it's not written in Rust, it's not worth using. 🦀
⚡ Powered by Rust ⚡