Show HN: OmniDiff – Opensource, super fast, content aware Git difftool, in Rust
- ID
- 41919
- Status
- summarized
- Published
- 01 Nov 2026, 9:02 PM
- Fetched
- 02 Nov 2026, 5:06 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/ivankovic/omnidiff
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 02 Nov 2026, 5:06 PM
- Tags
- Audience
- developersvibe_coders
What happened
OmniDiff is a Rust-based, content-aware git difftool that claims to handle 99.95% of code changes, with 98.8% routed through content-specific algorithms, and diffs in under 100ms on a ThinkPad T14s (Core i7-1370P, 32GB RAM). The repo shows 567 stars and 9 forks, and the HN thread drew 226 points and 55 comments. Install is `cargo install --locked omnidiff`, requiring a C compiler on PATH and rustc 1.92 or later; the repo ships both a LICENSE and a LICENSE-COMMERCIAL file, though terms aren't in the excerpt. Its own accuracy table is uneven: near-perfect on code, pictures, cursors and fonts, but 57% on PDFs, where there are fewer than ten judged test cases.
Why it matters
If you spend time reading diffs, this is a concrete alternative to plain `git diff` for binary-ish and structured files (fonts, images, ODF, message catalogs), but the vendor's own numbers say don't trust it on PDFs yet (57% accuracy, tiny sample). Decide based on the install cost: you need rustc 1.92+ and a C compiler, and you should read the commercial license file before wiring it into a team or CI workflow. There is no Malaysia or Southeast Asia angle in this text.
Discussion angle
The headline 99.95%/98.8% figures come from the project's own benchmark — what would you need to see (corpus, test methodology, third-party runs) before replacing your `git difftool` config, and is a content-aware diff worth it if PDFs still fail 43% of the time?