Optimizing Ruby Path Methods
weaksauce
76 points
27 comments
April 18, 2026
Related Discussions
Found 5 related stories in 53.8ms across 4,930 title embeddings via pgvector HNSW
- Four months of Ruby Central moving Ruby backward bigiain · 11 pts · March 04, 2026 · 47% similar
- Four months of Ruby Central moving Ruby backward martinhath · 13 pts · March 03, 2026 · 47% similar
- Returning to Rails in 2026 stanislavb · 356 pts · March 12, 2026 · 44% similar
- The future of code search is not regex – 100x faster than ripgrep neogoose · 14 pts · April 02, 2026 · 43% similar
- RubyGems Fracture Incident Report schneems · 91 pts · March 31, 2026 · 39% similar
Discussion Highlights (5 comments)
blinkbat
don't take this the wrong way, but -- people still use ruby?
nixpulvis
Would this be possible to mainline into ruby in some way?
vidarh
> More importantly, on CI systems it’s relatively common to check out code using git, and git doesn’t care about mtime git doesn't care about mtime, but git maintains trees whose hash changes if any constituent part of the tree changes. It'd seem tempting to check for a .git and if present use the git tree to determine whether to invalidate the cache.
somewhatrandom9
byroot sets a great example sharing his code optimization expertise. His blog has many great improvements like this. A 7x improvement in Dir.join and similar calls?! Thank you, byroot!
chi_features
> Given that the Intercom monolith CI runs with 1350 parallel workers by default Wow! I'd love to hear more about how that's achieved