Commenters debated upcoming Git changes: some, like eviks and 112233, asked whether reftable and binary formats are a step toward replacing file-based storage with a “proper” database and whether that’s desirable. KolmogorovComp and jayd16 worried that switching from SHA-1 to SHA-256 might require force-pushing or rewriting history and could open opportunities for malicious history changes, while em-bee and vlovich123 said SHA‑1 support will remain and new repos may be the default change, with blobs remaining verifiable. nextaccountic, infogulch, and others suggested practical mitigations - dual-hashing or history-scanning tools to verify byte-equality - and WCSTombs praised a new convenience command (git add --resolved).
A separate debate centered on introducing Rust into Git. coliveira argued that adopting Rust is coercive and largely symbolic, while tombert, jcranmer, and aw1621107 defended Rust as a way to reduce memory-safety CVEs in new code and pointed to talks and experience motivating the change. coliveira countered that small amounts of Rust won’t fix systemic C exposure, and cxr pressed for specific CVEs that Rust would have prevented. nvme0n1p1 framed using Rust as part of iterative codebase improvement rather than a wholesale rewrite, and wtfwhateven and others cited past security incidents as context for the debate.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.