From Rust to Ruby
xlii.space
May 26, 2026
4 min read
🔥🔥🔥🔥🔥
53/100
Summary
A project originally written in Rust, consisting of approximately 30,000 lines of code, is being revisited with an interest in Ruby and Ruby on Rails. Ruby and Ruby on Rails continue to perform well in the current programming landscape.
Key Takeaways
- The author converted a Rust web application with approximately 14,943 lines of code to Ruby on Rails, resulting in a 77% decrease in line count to 3,322 lines of Ruby code.
- The author estimates a 1.47x improvement in overall project outcomes when using Ruby on Rails compared to the original Rust implementation.
- The conversion process took about 30 minutes, and the author anticipates that testing will be significantly easier in Ruby on Rails.
- The author noted that while stability may decrease due to Ruby's lack of types, the use of Sorbet can provide type safety in Ruby applications.
Community Sentiment
Positives
- Ruby's meta programming capabilities allow for significant reductions in boilerplate code, streamlining the development process and enhancing productivity.
- Despite concerns about speed, Ruby has been reported to outperform Python in certain scenarios, which could shift perceptions about its efficiency.
- The ability of LLMs to assist in programming tasks indicates a future where software development could become more accessible and less reliant on traditional coding skills.
Concerns
- The reliance on LLMs for coding tasks raises concerns about the depth of understanding and craftsmanship in software development, potentially undermining the value of traditional programming skills.
- Many developers express frustration with Ruby on Rails, citing issues with maintainability and performance, which can lead to dissatisfaction in long-term projects.
- The perception that Ruby is slower than Rust, despite recent performance improvements, highlights ongoing misconceptions that could affect its adoption in performance-critical applications.
