homebrew-core has one Ruby file per package formula, and every brew update used to clone or fetch the whole repository until it got large enough that GitHub explicitly asked them to stop. Homebrew 4.0 switched to downloading a JSON file over HTTP, because users wanted the current state of a package rather than its commit history. But updating a formula still means opening a pull request against homebrew-core, because git is where the collaboration tooling lives. Instead of using git as a database, what if you used a database as a git?
Additional reporting by Jack Gray
。关于这个话题，WPS下载最新地址提供了深入分析
“形式主义少一些、真抓实干多一些，矛盾也会少一些，实绩也会多一些。”
Жители Санкт-Петербурга устроили «крысогон»17:52