<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: semanticintent</title><link>https://news.ycombinator.com/user?id=semanticintent</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 14 Apr 2026 11:05:24 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=semanticintent" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by semanticintent in "How to build a `Git diff` driver"]]></title><description><![CDATA[
<p>The point about textconv being sufficient in many cases is worth emphasizing — the cases where you actually need a full diff driver are when the file has semantics that text diff destroys. OpenAPI specs are a good example: a field rename looks like a deletion + addition in text diff but is a single semantic change.<p>I ran into the same thing building a semantic diff for a DSL compiler — text diff would report noise on every whitespace or reorder change, but the meaningful question is "which fields changed type, which statements were added or removed." Once you're operating on the AST the signal-to-noise ratio is completely different.</p>
]]></description><pubDate>Sun, 12 Apr 2026 01:30:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47735431</link><dc:creator>semanticintent</dc:creator><comments>https://news.ycombinator.com/item?id=47735431</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47735431</guid></item></channel></rss>