Optimizing Ruby Path Methods
byroot.github.io
Optimizing Ruby Path Methods
1–10 of 66 posts
Re: Optimizing Ruby Path Methods
#2don't take this the wrong way, but -- people still use ruby?
Re: Optimizing Ruby Path Methods
#3Would this be possible to mainline into ruby in some way?
Re: Optimizing Ruby Path Methods
#4don't take this the wrong way, but -- people still use ruby?
People should. I seriously miss using it at my day job. It's not for code where type systems make things a lot more stable, but it's great for scripting and quick things. Also ORMs in ruby are truly nice, and I haven't found anything as good anywhere else.
Generally speaking Ruby has the best APIs.
Re: Optimizing Ruby Path Methods
#5don't take this the wrong way, but -- people still use ruby?
Ruby on Rails is the GOAT. Nothing comes close in joy and productivity, even in 2026.
Re: Optimizing Ruby Path Methods
#6> 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.
Re: Optimizing Ruby Path Methods
#7Would this be possible to mainline into ruby in some way?
From the article: "This new feature will be available in Ruby 4.1.0."
Re: Optimizing Ruby Path Methods
#8don't take this the wrong way, but -- people still use ruby?
For pretty much everything. My terminal is in Ruby, with a Ruby font renderer, running Ruby shell, and my editor is in Ruby, my window manager, my file manager.
(Yes, I'm taking it a bit far; my prototype Ruby compiler is self-hosting finally, so I guess sometime in the next 20 years I'll end up booting into a Ruby kernel for no good reason...)
Re: Optimizing Ruby Path Methods
#9> 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.
Aside from the oddness of making this cache git aware, with the new implementation I suspect querying git to revalidate the cache would take longer than just rebuilding it.
Re: Optimizing Ruby Path Methods
#10don't take this the wrong way, but -- people still use ruby?
ruby and rails is the only stuff that keep me doing web development.
when I touch js, and python... I prefer ONLY AI agentic style of working.