3 ms·
Ruby is not the problem at all. The vast majority of time with homebrew is spent doing git operations, downloading tarballs, running makefiles, and the like. Yo
by OskarS 7y ago
Ruby is not the problem at all. The vast majority of time with homebrew is spent doing git operations, downloading tarballs, running makefiles, and the like. You could rewrite the entire thing in Rust and not notice any difference.
The thing that might make a difference is to build some custom infrastructure, so that `brew update` didn't have to do a `git fetch` every time, but instead downloaded the updated formula registry in a more efficient manner. But that's a lot to ask of a project like this.
- Fnoord 7y ago> The thing that might make a difference is to build some custom infrastructure, so that `brew update` didn't have to do a `git fetch` every time, but instead downloaded the updated formula registry in a more efficient manner. But that's a lot to ask of a project like this. How would this impact privacy? If I do brew search, does that impact privacy?
- saagarjha 7y agoHomebrew stores a lot of information in the Git repository that it really doesn’t need. A simple list of packages would work with the search feature and probably be faster to work with.
- sitzkrieg 7y agoim not convinced, just typing brew takes seconds to return the list of commands often
- samdixon 7y agoStill isn't a ruby issue. Likely an issue with the control flow doing things in a way that locks the front end and runs an expensive process.