<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: gavinhoward</title><link>https://news.ycombinator.com/user?id=gavinhoward</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 21 Nov 2026 08:13:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=gavinhoward" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by gavinhoward in "90% of US working hours are spent on tasks not covered well by AI benchmarks"]]></title><description><![CDATA[
<p><a href="https://www.youtube.com/watch?v=5ESJH1NLMLs" rel="nofollow">https://www.youtube.com/watch?v=5ESJH1NLMLs</a></p>
]]></description><pubDate>Sat, 17 Oct 2026 05:39:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=50128273</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=50128273</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50128273</guid></item><item><title><![CDATA[Compiler bootstrapping depends on more than you might think]]></title><description><![CDATA[
<p>Article URL: <a href="https://utcc.utoronto.ca/~cks/space/blog/programming/CompilerBootstrappingVsOSChanges">https://utcc.utoronto.ca/~cks/space/blog/programming/CompilerBootstrappingVsOSChanges</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=50090027">https://news.ycombinator.com/item?id=50090027</a></p>
<p>Points: 26</p>
<p># Comments: 2</p>
]]></description><pubDate>Wed, 14 Oct 2026 16:13:25 +0000</pubDate><link>https://utcc.utoronto.ca/~cks/space/blog/programming/CompilerBootstrappingVsOSChanges</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=50090027</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50090027</guid></item><item><title><![CDATA[New comment by gavinhoward in "Our $445M Series D"]]></title><description><![CDATA[
<p>As someone who has applied less than 6 weeks ago, this is great news. I can't wait to hear back!</p>
]]></description><pubDate>Fri, 09 Oct 2026 15:40:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=50022131</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=50022131</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50022131</guid></item><item><title><![CDATA[What If the Spec Doesn't Match the Code?]]></title><description><![CDATA[
<p>Article URL: <a href="https://buttondown.com/hillelwayne/archive/what-if-the-spec-doesnt-match-the-code/">https://buttondown.com/hillelwayne/archive/what-if-the-spec-doesnt-match-the-code/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49954953">https://news.ycombinator.com/item?id=49954953</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Sun, 04 Oct 2026 15:50:14 +0000</pubDate><link>https://buttondown.com/hillelwayne/archive/what-if-the-spec-doesnt-match-the-code/</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49954953</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49954953</guid></item><item><title><![CDATA[New comment by gavinhoward in "US sanctions force The Netherlands off Microsoft and toward alternative NixOS"]]></title><description><![CDATA[
<p>I'm okay dropping the philosophy and just making something that truly does what Nix claims: atomic upgrades, fully-reproducible environments, etc. In fact, dropping the philosophy is exactly why I am making my own.<p>Your idea sounds interesting and (by your bio) right up your alley. I'd be interested to see the result.</p>
]]></description><pubDate>Tue, 29 Sep 2026 16:36:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=49896134</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49896134</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49896134</guid></item><item><title><![CDATA[New comment by gavinhoward in "US sanctions force The Netherlands off Microsoft and toward alternative NixOS"]]></title><description><![CDATA[
<p>Huh.<p>I'm no Nix user, but I want to build an alternative.<p>Do you think these problems could be fixed?</p>
]]></description><pubDate>Tue, 29 Sep 2026 15:34:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=49895128</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49895128</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49895128</guid></item><item><title><![CDATA[New comment by gavinhoward in "On caring for user data: NeoVim caused Vim undo files to be deleted"]]></title><description><![CDATA[
<p>As a Neovim user, this stopped me dead with painful realization: I may have suffered the same thing but didn't realize it. There was a time when I could not undo something, and it was after a Neovim upgrade.<p>Unlike Dr. Chisnall, I started my editor journey on Neovim, so it wasn't a transition that bit me. However, if the format of the persistent undo file is unstable, and Neovim just deletes it when it doesn't recognize the previous format, then it seems conceivable (to me) that an upgrade after changing the format would delete the file too.<p>Ouch. This is making me think about getting off of Neovim. Yes, FOSS comes as-is, but if there's an alternative...</p>
]]></description><pubDate>Sun, 27 Sep 2026 15:23:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=49867454</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49867454</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49867454</guid></item><item><title><![CDATA[What Improves Developer Productivity at Google? Code Quality]]></title><description><![CDATA[
<p>Article URL: <a href="https://dl.acm.org/doi/pdf/10.1145/3540250.3558940">https://dl.acm.org/doi/pdf/10.1145/3540250.3558940</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49867306">https://news.ycombinator.com/item?id=49867306</a></p>
<p>Points: 4</p>
<p># Comments: 2</p>
]]></description><pubDate>Sun, 27 Sep 2026 15:09:24 +0000</pubDate><link>https://dl.acm.org/doi/pdf/10.1145/3540250.3558940</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49867306</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49867306</guid></item><item><title><![CDATA[Missile Task]]></title><description><![CDATA[
<p>Article URL: <a href="https://beza1e1.tuxen.de/lore/missile_task.html">https://beza1e1.tuxen.de/lore/missile_task.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49846143">https://news.ycombinator.com/item?id=49846143</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 25 Sep 2026 15:42:44 +0000</pubDate><link>https://beza1e1.tuxen.de/lore/missile_task.html</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49846143</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49846143</guid></item><item><title><![CDATA[New comment by gavinhoward in "Ask HN: What are you working on? (September 2026)"]]></title><description><![CDATA[
<p>Not something I'm working on, but want to: a competitor to Perforce that will be cheaper and easier.<p>Unfortunately, I'm not sure that being better is enough to compete, so I'm sitting on it for now.</p>
]]></description><pubDate>Mon, 14 Sep 2026 04:50:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=49692123</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49692123</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49692123</guid></item><item><title><![CDATA[New comment by gavinhoward in "Stop sending me huge PRs; a rant"]]></title><description><![CDATA[
<p>This is the first time I've heard a use for LLMs that I think might be good.</p>
]]></description><pubDate>Sat, 15 Aug 2026 02:53:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=49307151</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=49307151</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49307151</guid></item><item><title><![CDATA[New comment by gavinhoward in "Lore – Open source version control system designed for scalability"]]></title><description><![CDATA[
<p>> Looks like operational transforms to me.<p>Sort of. I add provenance, which helps properly identify collisions, and require a well-defined order by stacking [1] changelists.<p>> The doc claims it's the first with this technique.<p>More like the first with the particular angle on the technique. I specifically mention patch theory as another side of the same coin.<p>>  A 30 second search reminded me of Darcs, and taught me about Pijul, and Weave.<p>Darcs is Pijul's ancestor, and I mentioned Pijul. I also mentioned the weave and how reference sets scale better.<p>> The example in the doc uses text, and unfortunately I think it's for a reason.<p>Readability. Nothing more. The real stuff will be a compact binary format.<p>>  I think with large, binary game assets, the most common operation is going to be strings of "replace A with B", and depending on your chunk size relative to the distribution of changes you make on your assets, I see it as pretty close to a wash, for efficiency.<p>Yore will dedup change data instead because as the Lore document itself identifies, dedupping content is hard using chunks; you either get dedupping or canonical addresses. Change data doesn't have one canonical address; the address is in the commit data instead.<p>Dedupping changes has another benefit. If most instances are "replace A with B," and A replaces B in multiple places, Yore will be able to store just one instance of A, no matter its size. This matters because the larger the chunk, the less likely it will match any other chunk.<p>> Especially considering that content-addressable blocks also solves de-duplication, which for a multi-game studio is probably going to be significant. Especially if they're managing multiple releases, patches, development branches, etc.<p>True, but that should be table stakes. The fact that Git does not is a poor reflection on Git, not an innovation in Lore.<p>[1]: <a href="https://www.stacking.dev/" rel="nofollow">https://www.stacking.dev/</a></p>
]]></description><pubDate>Wed, 17 Jun 2026 21:53:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=48577424</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=48577424</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48577424</guid></item><item><title><![CDATA[New comment by gavinhoward in "Lore – Open source version control system designed for scalability"]]></title><description><![CDATA[
<p>The best answer I have is for you to read the "History Model" section of that design doc through the "Implementing CRDTs" subsection.</p>
]]></description><pubDate>Wed, 17 Jun 2026 17:15:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48573462</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=48573462</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48573462</guid></item><item><title><![CDATA[New comment by gavinhoward in "Epic Games announces Lore version control system"]]></title><description><![CDATA[
<p>When it comes to large assets, wasting large chunks of space is a problem. If your chunks are 64 kib average (from the Lore document), but changes only average 1 kib (which could be a high estimate), then you will still run out of space 64 times faster and need to read 64 times more data off of the disk for certain operations.<p>It also makes diffing hard, as well as diff viewing.</p>
]]></description><pubDate>Wed, 17 Jun 2026 16:30:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=48572814</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=48572814</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48572814</guid></item><item><title><![CDATA[New comment by gavinhoward in "Lore – Open source version control system designed for scalability"]]></title><description><![CDATA[
<p>As someone who has thought a lot about VCS design [1] [2], the chunking approach is the wrong one and will still waste space.<p>[1]: <a href="https://gavinhoward.com/uploads/designs/yore.md" rel="nofollow">https://gavinhoward.com/uploads/designs/yore.md</a><p>[2]: My WIP VCS has been named Yore for at least two years; I did not copy Lore's name.</p>
]]></description><pubDate>Wed, 17 Jun 2026 16:14:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48572559</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=48572559</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48572559</guid></item><item><title><![CDATA[New comment by gavinhoward in "GitHub CLI now collects pseudoanonymous telemetry"]]></title><description><![CDATA[
<p>Because Git was faster.<p>This mattered because speed is the killer feature [1], and speed is often seen by users as a proxy for reliability [2].<p>[1]: <a href="https://bdickason.com/posts/speed-is-the-killer-feature/" rel="nofollow">https://bdickason.com/posts/speed-is-the-killer-feature/</a><p>[2]: <a href="https://craigmod.com/essays/fast_software/" rel="nofollow">https://craigmod.com/essays/fast_software/</a></p>
]]></description><pubDate>Wed, 22 Apr 2026 14:42:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47864370</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=47864370</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47864370</guid></item><item><title><![CDATA[New comment by gavinhoward in "The future of version control"]]></title><description><![CDATA[
<p>> At this point if your VCS isn't a layer above git plumbing, nobody gonna waste time using it.<p>Probably true, but it's a shame because there are better ways of storing and processing the data, ways that <i>natively</i> handle binary files, semantics, and large files without falling over.</p>
]]></description><pubDate>Mon, 23 Mar 2026 20:15:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=47494512</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=47494512</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47494512</guid></item><item><title><![CDATA[New comment by gavinhoward in "A case against currying"]]></title><description><![CDATA[
<p>Okay, but if you combine the curried and tuple styles, and add a dash of runtime function pointers, you can solve the expression problem. [1]<p>[1]: <a href="https://gavinhoward.com/2025/04/how-i-solved-the-expression-problem/" rel="nofollow">https://gavinhoward.com/2025/04/how-i-solved-the-expression-...</a></p>
]]></description><pubDate>Sun, 22 Mar 2026 18:51:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=47480769</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=47480769</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47480769</guid></item><item><title><![CDATA[New comment by gavinhoward in "The future of version control"]]></title><description><![CDATA[
<p>Bram Cohen is awesome, but this feels a little bare. I've put much more thought into version control ([1]), including the use of CRDTs (search for "# History Model" and read through the "Implementing CRDTs" section).<p>[1]: <a href="https://gavinhoward.com/uploads/designs/yore.md" rel="nofollow">https://gavinhoward.com/uploads/designs/yore.md</a></p>
]]></description><pubDate>Sun, 22 Mar 2026 18:44:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47480695</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=47480695</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47480695</guid></item><item><title><![CDATA[New comment by gavinhoward in "Software engineers should be a little bit cynical"]]></title><description><![CDATA[
<p>> For instance, you might think that big tech engineers are being deliberately demoralized as part of an anti-labor strategy to prevent them from unionizing, which is nuts. Tech companies are simply not set up to engage in these kind of conspiracies.<p><a href="https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_Litigation" rel="nofollow">https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...</a></p>
]]></description><pubDate>Sun, 28 Dec 2025 21:56:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=46414905</link><dc:creator>gavinhoward</dc:creator><comments>https://news.ycombinator.com/item?id=46414905</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46414905</guid></item></channel></rss>