<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: schamper</title><link>https://news.ycombinator.com/user?id=schamper</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 29 Jun 2026 22:38:51 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=schamper" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by schamper in "Dissecting Apple's Sparse Image Format (ASIF)"]]></title><description><![CDATA[
<p>Author here, this is a valid point but there are also valid reasons to choose C structures.
 The larger framework that this is a part of is primarily targeted towards people working in cybersecurity, not software engineers. Cybersecurity people are very often not great software engineers and there is a high throughput of “throwaway” scripts, or “make a quick hacky change”. C is commonly already well understood, a bespoke DSL usually is not and requires a learning step. You can “hit the ground running”, so to say.<p>And, as a bonus, creating, say, a filesystem implementation is now often as easy as copy/pasting existing C structure definitions, either from the original source (which is usually C) or from reversing tools such as IDA/Ghidra.<p>There’s no right or wrong way in my opinion, just preferences.</p>
]]></description><pubDate>Mon, 29 Jun 2026 11:28:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48717861</link><dc:creator>schamper</dc:creator><comments>https://news.ycombinator.com/item?id=48717861</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48717861</guid></item></channel></rss>