<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: mxey</title><link>https://news.ycombinator.com/user?id=mxey</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 22 Apr 2026 12:47:38 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mxey" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mxey in "We tasked Opus 4.6 using agent teams to build a C Compiler"]]></title><description><![CDATA[
<p>That’s the opposite of clean-room. The whole point of clean-room design is that you have your software written by people who have not looked into the competing, existing implementation, to prevent any claim of plagiarism.<p>“Typically, a clean-room design is done by having someone examine the system to be reimplemented and having this person write a specification. This specification is then reviewed by a lawyer to ensure that no copyrighted material is included. The specification is then implemented by a team with no connection to the original examiners.”</p>
]]></description><pubDate>Thu, 05 Feb 2026 22:26:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=46906286</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46906286</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46906286</guid></item><item><title><![CDATA[New comment by mxey in "Unconventional PostgreSQL Optimizations"]]></title><description><![CDATA[
<p>PostgreSQL shares other caches between processes so they probably could have a global plan cache if they wanted. I wonder why they don’t though.<p>One possible reason is that the planner configuration can be different per connection, so the plans might not transfer</p>
]]></description><pubDate>Wed, 21 Jan 2026 08:35:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=46702720</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46702720</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46702720</guid></item><item><title><![CDATA[New comment by mxey in "Unconventional PostgreSQL Optimizations"]]></title><description><![CDATA[
<p>This is very good to know because it means this exclusion constraint workaround is a better approach over using a SQL hash function and a btree if you want to enforce uniqueness on values too long for a btree index.</p>
]]></description><pubDate>Wed, 21 Jan 2026 08:33:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=46702702</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46702702</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46702702</guid></item><item><title><![CDATA[New comment by mxey in "Cue Does It All, but Can It Literate?"]]></title><description><![CDATA[
<p>No, that’s why I said deploy. All it does is run kubectl apply and kubectl rollout status.<p>Only those are directly tied to the data in CUE. there’s not much advantage to running other commands with it. You can run arbitrary processes with cue cmd though.</p>
]]></description><pubDate>Sat, 17 Jan 2026 11:19:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=46657142</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46657142</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46657142</guid></item><item><title><![CDATA[New comment by mxey in "psc: The ps utility, with an eBPF twist and container context"]]></title><description><![CDATA[
<p>“ss” also has filters, no need for grep<p>ss -o state established '( dport = :ssh or sport = :ssh )'</p>
]]></description><pubDate>Fri, 16 Jan 2026 20:06:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=46651478</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46651478</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46651478</guid></item><item><title><![CDATA[New comment by mxey in "6-Day and IP Address Certificates Are Generally Available"]]></title><description><![CDATA[
<p>There will be no certificates longer than 45 days by any CA in browsers in a few years.</p>
]]></description><pubDate>Fri, 16 Jan 2026 18:50:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=46650370</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46650370</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46650370</guid></item><item><title><![CDATA[New comment by mxey in "Cue Does It All, but Can It Literate?"]]></title><description><![CDATA[
<p>Not sure if that’s what you mean but we have apps where all you need to deploy them to Kubernetes is run “cue cmd deploy”.<p>> The problem is, once you have to wrap CUE, the loss of flexibility within a special-purpose language like CUE is enough for people to ask why not just bother writing the scripts in a general purpose language with better ecosystem support.<p>cue cmd is nice but it’s not the reason to use CUE. The data parts are. I would still use if I had to use “cue export” to get the data out of it with a bit of shell.</p>
]]></description><pubDate>Fri, 16 Jan 2026 13:19:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=46646082</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46646082</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46646082</guid></item><item><title><![CDATA[New comment by mxey in "CSRF protection without tokens or hidden form fields"]]></title><description><![CDATA[
<p>Without those headers, you can as a fallback compare the Origin header to the Host header.<p>See <a href="https://words.filippo.io/csrf/" rel="nofollow">https://words.filippo.io/csrf/</a></p>
]]></description><pubDate>Thu, 25 Dec 2025 10:24:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=46383503</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46383503</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46383503</guid></item><item><title><![CDATA[New comment by mxey in "Fifty problems with standard web APIs in 2025"]]></title><description><![CDATA[
<p>I had the same thought about the idea that Safari is “behind”. My hypothesis is that features only “exist” to people if they are implemented in Chrome. If a feature exists in WebKit but not in Chrome, nobody talks about it.</p>
]]></description><pubDate>Wed, 24 Dec 2025 12:49:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=46375132</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46375132</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46375132</guid></item><item><title><![CDATA[New comment by mxey in "Fifty problems with standard web APIs in 2025"]]></title><description><![CDATA[
<p>iPhones tend to have dramatically better JavaScript performance so you might wanna also test on an average Android phone.</p>
]]></description><pubDate>Wed, 24 Dec 2025 12:47:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=46375118</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46375118</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46375118</guid></item><item><title><![CDATA[New comment by mxey in "Fifty problems with standard web APIs in 2025"]]></title><description><![CDATA[
<p>I can’t wait for websites to tell me I need to install Chrome on my phone.</p>
]]></description><pubDate>Wed, 24 Dec 2025 12:45:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=46375108</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46375108</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46375108</guid></item><item><title><![CDATA[New comment by mxey in "Fifty problems with standard web APIs in 2025"]]></title><description><![CDATA[
<p>Safari adds support for new web features in point releases throughout the year.</p>
]]></description><pubDate>Wed, 24 Dec 2025 12:45:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=46375100</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46375100</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46375100</guid></item><item><title><![CDATA[New comment by mxey in "Fabrice Bellard Releases MicroQuickJS"]]></title><description><![CDATA[
<p>you know you CAN make small websites with the existing standards already</p>
]]></description><pubDate>Wed, 24 Dec 2025 11:23:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=46374623</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46374623</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46374623</guid></item><item><title><![CDATA[New comment by mxey in "Debian's Git Transition"]]></title><description><![CDATA[
<p>Quilt was AFAIK used before Git, so you’re not wrong. But now that it’s there, it has some advantages.<p>I’m not arguing against replacing Quilt, but it should be more than just Git. I haven’t done Debian packaging in a long time but apparently there are some Git-based tools now?</p>
]]></description><pubDate>Wed, 24 Dec 2025 11:00:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=46374474</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46374474</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46374474</guid></item><item><title><![CDATA[New comment by mxey in "Debian's Git Transition"]]></title><description><![CDATA[
<p>So there’s no way to have commit messages on changes to patches? 
There’s also <a href="https://dep-team.pages.debian.net/deps/dep3/" rel="nofollow">https://dep-team.pages.debian.net/deps/dep3/</a><p>People keep saying “just use Git commits” without understanding the advantages of the Quilt approach. There are tools to keep patches as Git commits that solve this, but “just Git commits” do not.</p>
]]></description><pubDate>Wed, 24 Dec 2025 07:20:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=46373265</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46373265</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46373265</guid></item><item><title><![CDATA[New comment by mxey in "Debian's Git Transition"]]></title><description><![CDATA[
<p>How do you track changes to the patches themselves?</p>
]]></description><pubDate>Tue, 23 Dec 2025 12:11:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=46364668</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46364668</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46364668</guid></item><item><title><![CDATA[New comment by mxey in "Rue: Higher level than Rust, lower level than Go"]]></title><description><![CDATA[
<p>> For everyone else, keeping checked-in auto-generated code is a continuous toil and maintenance burden. The Google go developers don't see it that way of course, because they are biased due to their google3 experience.<p>The golang/go repo itself has various checked-in generated repo</p>
]]></description><pubDate>Mon, 22 Dec 2025 09:54:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=46352722</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46352722</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46352722</guid></item><item><title><![CDATA[New comment by mxey in "Rue: Higher level than Rust, lower level than Go"]]></title><description><![CDATA[
<p>> On the other hand, these auto generation tools in Go are only somewhat standardized, you don't have a central tool that takes care of things (or at least I'm not aware of it).<p><a href="https://pkg.go.dev/cmd/go#hdr-Generate_Go_files_by_processing_source" rel="nofollow">https://pkg.go.dev/cmd/go#hdr-Generate_Go_files_by_processin...</a></p>
]]></description><pubDate>Mon, 22 Dec 2025 09:52:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=46352707</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46352707</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46352707</guid></item><item><title><![CDATA[New comment by mxey in "Don MacKinnon: Why Simplicity Beats Cleverness in Software Design [audio]"]]></title><description><![CDATA[
<p>What do you mean that there is no standard decoder? For what, UTF-8?<p>I agree on the composability. Accepting Unicode code points is more generic. I guess it depends on your environment. If every caller will combine it with a UTF-8 decoder, you might want to include it.</p>
]]></description><pubDate>Thu, 18 Dec 2025 13:13:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=46312209</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46312209</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46312209</guid></item><item><title><![CDATA[New comment by mxey in "Don MacKinnon: Why Simplicity Beats Cleverness in Software Design [audio]"]]></title><description><![CDATA[
<p>> Unfortunately, in software, manufacturing costs are too cheap to meter, so we're fine with using bench-top prototypes in production, because we're not the ones paying the costs for the waste anyway, our users are.<p>I’m not sure what you’re trying to say - UTF-8 is the standard text encoding by a mile. It’s not a prototype.</p>
]]></description><pubDate>Thu, 18 Dec 2025 13:12:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=46312201</link><dc:creator>mxey</dc:creator><comments>https://news.ycombinator.com/item?id=46312201</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46312201</guid></item></channel></rss>