Weave: Merging based on language structure and not lines

A new tool called Weave is making a bold promise in one of coding’s messiest relationship dramas: the dreaded merge conflict. In plain English, when two people — or two AI helpers — edit different parts of the same file, Git, the popular code-saving tool, often panics and screams conflict even when the changes don’t actually clash. Weave says it can look at the meaning and structure of the code instead of just matching raw lines, which means separate edits to separate functions can slide together cleanly.

And yes, the community instantly turned this into a mix of hype, suspicion, and “haven’t we seen this before?” One commenter basically demanded a better trailer, saying the first image should show the merge difference up front — a very "show me, don’t tell me" energy. Another jumped straight to the comparison game: how does it stack up against SemanticDiff? Someone else brought receipts and linked Mergiraf, with the unmistakable vibe of “cool, but is this just that other thing with better branding?”

The hottest practical concern came from people thinking beyond toy demos. One commenter wondered how this survives the chaos of big company repositories, where code gets checked, scanned, and approved six different ways before lunch. Meanwhile, the most approving take was also the most blunt: this is how merges always should have worked. No giant flame war yet — just that delicious early-stage tech-comment tension where half the crowd is excited, and the other half is already preparing the comparison chart.