Git 3.0 plans to switch its default hashing algorithm from SHA-1 to SHA-256 to address theoretical collision vulnerabilities, but the author argues this breaking change will impose significant costs on users for minimal practical benefit, as SHA-1 collisions have never occurred in billions of real repositories despite being mathematically possible.