<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: wmanley</title><link>https://news.ycombinator.com/user?id=wmanley</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 02 Jul 2026 00:18:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=wmanley" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by wmanley in "Free the Icons"]]></title><description><![CDATA[
<p>> seemingly because Zuck isn't aware of how untalented the guy is.<p>Maybe Zuck just wanted his laptop to get better.</p>
]]></description><pubDate>Tue, 30 Jun 2026 08:43:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48730023</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48730023</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48730023</guid></item><item><title><![CDATA[New comment by wmanley in "AI agent runs amok in Fedora and elsewhere"]]></title><description><![CDATA[
<p>> A good fix (which is the only acceptable fix in open-source software), is one that speaks for itself.<p>I disagree. Often if I'm making a PR to an open-source project I'm doing so because I have a use-case that the original author hadn't considered.  So the first step in getting the PR merged is explaining my point of view and convincing the maintainer that my use-case is valid.  Only when this is done can the "goodness" of the patch be evaluated.</p>
]]></description><pubDate>Thu, 11 Jun 2026 11:29:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=48488925</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48488925</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48488925</guid></item><item><title><![CDATA[New comment by wmanley in "Building an HTML-first site doubled our users overnight"]]></title><description><![CDATA[
<p>I disagree. An HTML website which uses links, forms, buttons and inputs will by default:<p>* Have working back/forward buttons
* Have working progress indicator as provided by the browser
* Show errors to the user - even if they are ugly
* Be accessible to keyboard navigation<p>With SPAs these are all things the developer has to get right.<p>So often when using a SPA I'll click a button, you get a spinner and then nothing will happen. Is it still in progress? Don't know. Eventually I'll open developer console and trace the network requests to find the JSON HTTP request that returned "ERR_BAD_EMAIL" and fix what I've entered. With a normal form submission at least the user will see the error message and can press back and then fix it.</p>
]]></description><pubDate>Wed, 10 Jun 2026 14:47:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48477121</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48477121</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48477121</guid></item><item><title><![CDATA[New comment by wmanley in "Building an HTML-first site doubled our users overnight"]]></title><description><![CDATA[
<p>The counterargument: In Defence of the Single Page Application:<p><a href="https://williamkennedy.ninja/javascript/2022/05/03/in-defence-of-the-single-page-application/" rel="nofollow">https://williamkennedy.ninja/javascript/2022/05/03/in-defenc...</a></p>
]]></description><pubDate>Wed, 10 Jun 2026 14:08:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=48476547</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48476547</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48476547</guid></item><item><title><![CDATA[New comment by wmanley in "Love systemd timers"]]></title><description><![CDATA[
<p>I design all my services expecting to receive sockets this way.  It makes sandboxing easy as the service itself doesn't need network access to have a listening socket.<p>It's a shame docker never supported it.  I feel like if they had got on board all those years ago there would be broad support across the software ecosystem for it and we wouldn't need half of these complicated iptables rules and proxies and service mesh.  It would be a step towards a capability based system.</p>
]]></description><pubDate>Tue, 02 Jun 2026 13:37:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=48370125</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48370125</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48370125</guid></item><item><title><![CDATA[New comment by wmanley in "Details of the Daring Airdrop at Tristan Da Cunha"]]></title><description><![CDATA[
<p>Wonderful. I love the poem at the end too.</p>
]]></description><pubDate>Fri, 15 May 2026 08:53:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=48146174</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=48146174</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48146174</guid></item><item><title><![CDATA[New comment by wmanley in "Durable queues, streams, pub/sub, and a cron scheduler – inside your SQLite file"]]></title><description><![CDATA[
<p>I've implemented something similar in the past, but using inotify.  You need to watch the -wal file for IN_MODIFY.  To make it work reliably I found I had to run:<p><pre><code>    BEGIN IMMEDIATE TRANSACTION; ROLLBACK;
</code></pre>
Otherwise the new changes weren't guaranteed to be visible to the process.  I'm sure there's a more targetted approach that would work instead - maybe flock on a particular byte in the `-shm` file.</p>
]]></description><pubDate>Thu, 30 Apr 2026 20:08:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=47967579</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=47967579</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47967579</guid></item><item><title><![CDATA[New comment by wmanley in "Do you even need a database?"]]></title><description><![CDATA[
<p>SQLite in mmap mode (not the default) will use mmap for reading.  It will still use write using `pwrite` so it can detect and recover from write failures.<p>See <a href="https://www.sqlite.org/mmap.html" rel="nofollow">https://www.sqlite.org/mmap.html</a> :<p>> The default mechanism by which SQLite accesses and updates database disk files is the xRead() and xWrite() methods of the sqlite3_io_methods VFS object. These methods are typically implemented as "read()" and "write()" system calls which cause the operating system to copy disk content between the kernel buffer cache and user space.<p>> Beginning with version 3.7.17 (2013-05-20), SQLite has the option of accessing disk content directly using memory-mapped I/O and the new xFetch() and xUnfetch() methods on sqlite3_io_methods.<p>The principal advantage to mmap in my mind is that the cache is shared among your SQLite connections.</p>
]]></description><pubDate>Thu, 16 Apr 2026 14:14:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=47793289</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=47793289</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47793289</guid></item><item><title><![CDATA[New comment by wmanley in "Do you even need a database?"]]></title><description><![CDATA[
<p>Business logic tests will rarely test what happens to your data if a machine loses power.</p>
]]></description><pubDate>Wed, 15 Apr 2026 15:45:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47780736</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=47780736</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47780736</guid></item><item><title><![CDATA[New comment by wmanley in "What does " 2>&1 " mean?"]]></title><description><![CDATA[
<p>It's a shame that unix tools don't support file descriptors better.  The ability to pass a file (or stream, or socket etc) directly into a process is so powerful, but few commands actually support being used this way and require filenames (or hostnames, etc) instead.  Shell is so limited in this regard too.<p>It would be great to be able to open a socket in bash[^1] and pass it to another program to read/write from without having an extra socat process and pipes running (and the buffering, odd flush behaviour, etc.).  It would be great if programs expected to receive input file arguments as open fds, rather than providing filenames and having the process open them itself.  Sandboxing would be trivial, as would understanding the inputs and outputs of any program.<p>It's frustrating to me because the underlying unix system supports this so well, it's just the conventions of userspace that get in the way.<p>[^1]: I know about /dev/tcp, but it's very limited.</p>
]]></description><pubDate>Fri, 27 Feb 2026 13:28:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=47180286</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=47180286</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47180286</guid></item><item><title><![CDATA[New comment by wmanley in "America vs. Singapore: You can't save your way out of economic shocks"]]></title><description><![CDATA[
<p>US borders are awful. I guess you get away with it because the USA is so large that most people rarely leave, so rarely have to experience it.</p>
]]></description><pubDate>Thu, 19 Feb 2026 23:56:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47081605</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=47081605</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47081605</guid></item><item><title><![CDATA[New comment by wmanley in "The state of the kernel Rust experiment"]]></title><description><![CDATA[
<p>I guess that means you're using the colloquial meaning of the word safety/unsafe rather than the rust definition.  It's worth being explicit about that (or choosing a different word) in these discussions to prevent confusion.<p>For Rust safety (meaning no UB) most definitely is a property of the language.  If a module does not contain unsafe and the modules it uses that do contain unsafe are implemented soundly then there is no UB.<p>In C UB is a part of the language.</p>
]]></description><pubDate>Fri, 19 Dec 2025 13:16:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=46325476</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=46325476</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46325476</guid></item><item><title><![CDATA[New comment by wmanley in "The state of the kernel Rust experiment"]]></title><description><![CDATA[
<p>> in C only specific language features are unsafe and not all code<p>Using rust's definition of unsafe which is roughly "can cause undefined behaviour" then it seems to me isolating use of these features isn't possible.  What is C without:<p>* Dereferencing pointers
* Array access
* Incrementing signed integers<p>You can do all of the above without invoking UB, but you can't separate the features in C that can cause UB from the ones that can't.</p>
]]></description><pubDate>Fri, 19 Dec 2025 11:23:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=46324592</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=46324592</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46324592</guid></item><item><title><![CDATA[New comment by wmanley in "100k TPS over a billion rows: the unreasonable effectiveness of SQLite"]]></title><description><![CDATA[
<p>Use a connection per-thread instead. By sharing a connection across threads you’ll be limiting concurrency - and transactions won’t work as you’d expect. SQLite connections are not heavy.<p>Also: use WAL mode and enable mmap.</p>
]]></description><pubDate>Tue, 02 Dec 2025 19:38:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=46125686</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=46125686</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46125686</guid></item><item><title><![CDATA[New comment by wmanley in "Migrating the main Zig repository from GitHub to Codeberg"]]></title><description><![CDATA[
<p>Retries won’t work in that case. Would be better to have two endpoints: get the time in x seconds and wait until time passed. That way retrying the wait endpoint will work fine and if time hasn’t elapsed it can just curl itself with the same arguments.</p>
]]></description><pubDate>Thu, 27 Nov 2025 07:41:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=46066755</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=46066755</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46066755</guid></item><item><title><![CDATA[New comment by wmanley in "Drawing Text Isn't Simple: Benchmarking Console vs. Graphical Rendering"]]></title><description><![CDATA[
<p>No, actually the biggest difference is removing the `filter` property from the `.wave2` class which is used for rendering the background.  With that removed the page is responsive even with the backdrop-filter - and it makes no visual difference AFAICS.</p>
]]></description><pubDate>Wed, 12 Nov 2025 11:03:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=45898710</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=45898710</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45898710</guid></item><item><title><![CDATA[New comment by wmanley in "Drawing Text Isn't Simple: Benchmarking Console vs. Graphical Rendering"]]></title><description><![CDATA[
<p>It's also perfectly responsive if you disable JavaScript.  Maybe something related to the --positionX and --positionY CSS variables that are updated on every mouse move?</p>
]]></description><pubDate>Wed, 12 Nov 2025 09:56:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=45898302</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=45898302</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45898302</guid></item><item><title><![CDATA[New comment by wmanley in "Laptops with Stickers"]]></title><description><![CDATA[
<p>What stickers did you used to have? I'm always fascinated with how people change their mind.</p>
]]></description><pubDate>Wed, 12 Nov 2025 09:53:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=45898270</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=45898270</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45898270</guid></item><item><title><![CDATA[New comment by wmanley in "Drawing Text Isn't Simple: Benchmarking Console vs. Graphical Rendering"]]></title><description><![CDATA[
<p>Looks like it's caused by `backdrop-filter: blur(6px);` on `.menu-content`. After disabling that it's slow, but not <i>that</i> slow.<p>Edit: This is with Firefox 144 on Ubuntu 22.04</p>
]]></description><pubDate>Tue, 11 Nov 2025 17:13:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=45889990</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=45889990</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45889990</guid></item><item><title><![CDATA[New comment by wmanley in "The future of Python web services looks GIL-free"]]></title><description><![CDATA[
<p>Even with volatile it’s a load and then a store no? It may not be undefined behaviour, but I don’t think it will be atomic.</p>
]]></description><pubDate>Sat, 25 Oct 2025 22:50:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=45707597</link><dc:creator>wmanley</dc:creator><comments>https://news.ycombinator.com/item?id=45707597</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45707597</guid></item></channel></rss>