Feed fetched in 538 ms.
Warning Content type is application/atom+xml, not text/xml or applicaton/xml.
Feed is 171,288 characters long.
Feed has an ETag of "2a5c5-65075cbb07a36".
Feed has a last modified date of Mon, 27 Apr 2026 19:05:19 GMT.
Feed is well-formed XML.
Warning Feed has no styling.
This is an Atom feed.
Feed title: ongoing by Tim Bray
Feed self link matches feed URL.
Feed has an image at rsslogo.jpg.
Feed has 20 items.
First item published on 2026-04-27T19:05:14.000Z
Last item published on 2025-11-23T20:00:00.000Z
All items have published dates.
Newest item was published on 2026-04-27T19:05:14.000Z.
Info Feed's Last-Modified date is newer than the newest item's published date (2026-04-27T19:05:19.000Z > 2026-04-27T19:05:14.000Z).
Home page URL: https://www.tbray.org/ongoing/
Home page has feed discovery link in <head>.
Home page has a link to the feed in the <body>
<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0" xml:lang="en-us">
<title>ongoing by Tim Bray</title>
<link rel="hub" href="http://pubsubhubbub.appspot.com/"/>
<id>https://www.tbray.org/ongoing/</id>
<link href="https://www.tbray.org/ongoing/"/>
<link rel="self" href="https://www.tbray.org/ongoing/ongoing.atom"/>
<link rel="replies" thr:count="101" href="https://www.tbray.org/ongoing/comments.atom"/>
<logo>rsslogo.jpg</logo>
<icon>/favicon.ico</icon>
<updated>2026-04-27T12:05:18-07:00</updated>
<author>
<name>Tim Bray</name>
</author>
<subtitle>ongoing fragmented essay by Tim Bray</subtitle>
<rights>All content written by Tim Bray and photos by Tim Bray Copyright Tim Bray, some rights reserved, see /ongoing/misc/Copyright</rights>
<generator uri="/misc/Colophon">Generated from XML source code using Perl, Expat, Emacs, Mysql, Ruby, and ImageMagick. Industrial-strength technology, baby.</generator>
<entry>
<title>Corey’s Captives</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/04/26/Coreys-Captives#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives</id>
<published>2026-04-26T12:00:00-07:00</published>
<updated>2026-04-27T12:05:14-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts/Books"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Books"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">That’s <a href="https://en.wikipedia.org/wiki/James_S._A._Corey">James S.A. Corey</a>, which is to say Daniel Abraham and Ty Franck, and their new series <a href="https://en.wikipedia.org/wiki/The_Captive%27s_War">The Captive’s War</a>, an in-progress work comprising 2¼ or so novels. The Coreys are of course best-known for their deservedly wildly popular <cite>The Expanse</cite> series and the subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should wade in, the following is for you</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
That’s
<a href="https://en.wikipedia.org/wiki/James_S._A._Corey">James S.A. Corey</a>
, which is to say Daniel Abraham and Ty Franck,
and their new series
<a href="https://en.wikipedia.org/wiki/The_Captive%27s_War">The Captive’s War</a>
, an in-progress work comprising 2¼
or so novels. The Coreys are of course best-known for their deservedly wildly popular
<cite>The Expanse</cite>
series and the
subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should
wade in, the following is for you.
</p>
<h2 id="p-1">Minor and meta spoilers</h2>
<p>Don’t worry, you can go on reading this even if you plan to read the books. Here’s a spoiler that has appeared in every public
mention of the book, which I’ll give away with a quote from page 102: “I think some important scientific questions have finally
been answered. Alien life exists, and they are assholes.” Which is to say, it doesn’t go well for the humans.</p>
<p>
Now for the meta-spoilers. The novels are
<cite>The Mercy of Gods</cite>
and
<cite>The Faith of Beasts</cite>
, then there’s a
novella,
<cite>Livesuit</cite>
. I found
<cite>The Mercy of Gods</cite>
a bit of a grind, and if that’s all I’d read I would have
been pretty negative about this project. There is a major,
<em>major</em>
reveal partway into
<cite>The Faith of Beasts</cite>
that changed my whole outlook on the series; it makes the storytelling velocity really pick up. It’s a little annoying that
<cite>Livesuit</cite>
was published between the two full novels because it only really makes sense if you’ve finished both of
them. So do like I did, and read the novella last.
</p>
<p>I have to ask why the Coreys couldn’t have pulled the curtain aside a little earlier on. And while I’m griping, let me add
that the sped-up storytelling runs into a big honking cliffhanger ending at high velocity. Harumph.</p>
<h2 id="p-2">My take-away</h2>
<p>
It could go off the rails but if they can maintain their
<cite>Expanse</cite>
form, I suspect this series is going to be
pretty great. The characters are fun to know and the narrative revolves around the great mother of all trolley-problem ethical
challenges, which was not nearly resolved at cliffhanger-ending time.
</p>
<p>Those of us who are fussy about the plausibility of future technologies (hey, Charlie Stross) should avert their eyes from
the Coreys’ fairly low-effort attempts to explain how the aliens and humans in this story accomplish the things they do. Doesn’t
bother me much, though.</p>
<p>
Having said all that, this series is not cheerful stuff; I do
<em>not</em>
recommend it to those who, like many in these
troubled times, are having trouble seeing the bright side of, well, anything.
</p>
<h2 id="p-3">Will I read the next volume?</h2>
<p>Yep, no hesitation. And they’ve already started working on a streaming version. Unfortunately it’s going to be on Amazon
Prime, which I haven’t missed since unsubscribing a couple years ago. Getting this thing on the screen is
going to be an extended, difficult, task. There are multiple species of aliens that the show is going to have to absolutely nail, with
emotional credibility, for the story to work. Don’t hold your breath.</p>
</div>
</content>
</entry>
<entry>
<title>Spring Evening</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/04/13/Modern-Cameras#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras</id>
<published>2026-04-13T12:00:00-07:00</published>
<updated>2026-04-15T22:23:17-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts/Photos"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Photos"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">On impulse, Lauren and I went out for a short walk<span class="dashes"> —</span> around just a few blocks<span class="dashes"> —</span> as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera on the way out the door</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
On impulse, Lauren and I went out for a short walk
<span class="dashes"> —</span>
around just a few
blocks
<span class="dashes"> —</span>
as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera
on the way out the door.
</p>
<p>
In our local community garden, here’s (I think) a
<a href="https://en.wikipedia.org/wiki/Chard">chard</a>
.
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56259.png" alt="Looking down on a vegetable plant with glossy green leaves and orange-yellow stalks"/>
<p>That was in Vancouver’s Mount Pleasant park, small but nice and apparently never not used. Also this old blackened
fruit tree, we’re a bit past the fruit-blossom peak for this year. Nice to see I’m not the only old citizen trying to brighten
things up.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56264.png" alt="Fruit-tree blossoms on a blackened branch"/>
<p>Now we’re walking up a locally-main street called Main Street or “The Main” if you’re trying to sound
hip. Someone put work into that window! I’ve bought my daughter a couple of cool birthday presents from the store behind it. My
thanks to the building across the street for providing a dark background reflection.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56265.png" alt="Used-fashion store window "/>
<p>Back to the next block over from ours. A while ago a bunch of people were building little fairy/elf/hobbit villages at the
bottoms of the big old trees. This isn’t that. What is it?</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56270.png" alt="Dolls and related tree artifacts at the base of a tree in dim light"/>
<p>The colors of the natural surfaces are real.</p>
<h2 id="p-1">Cameras</h2>
<p>When I shot these, it
was getting dark but I didn’t think much, mostly just pointed and shot. (Fiddled with the aperture dial a bit.) Then I came
home and pulled them into Lightroom and didn’t need to do really anything about colors. A bit of contrast and highlights here
and there. Oh, and fairly brutal cropping, especially on that fruit-tree-flowers pic. Because like I said, I didn’t think very
much when I was shooting and I didn’t have to because on a Twenties camera you don’t.</p>
<p>I could take that heavily-cropped fruit-tree
picture and print it big enough to occupy any domestic wall in your place and yeah, there’d be grain but it wouldn’t
bother your eyes.</p>
<p>Anyhow, modern cameras are pretty great. The lowest ISO in today’s set is 2500 and the highest is 6400; the apertures range
from 2.8 to 5.6.
Bet you can’t tell the differences. My camera is a reasonably modern Fujifilm but not remotely
bleeding-edge in camera tech. (Note: 35mm F1.4, now all the Fuji fanfolk are smiling and nodding.)</p>
<p>
Anyhow, there are very
<em>very</em>
few photographers for whom the camera they carry is the limiting factor in the
goodness of their pictures. Certainly not me.
</p>
<p>Consider getting a camera. Used is fine, anything built in the last five years, maybe more, will effortlessly take brilliant
pictures in almost any conditions. Sure, your phone can take great shots too, but the feeling of walking along with something
that fits your hand and you only have to press one physical button once, that feeling, it helps you see the good pictures when they happen.</p>
<p>Then go out after and take a walk in the Spring dusk.</p>
</div>
</content>
</entry>
<entry>
<title>Password Manager Angst</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst"/>
<link rel="replies" thr:count="13" type="application/xhtml+xml" href="/ongoing/When/202x/2026/04/09/Password-Manager-Angst#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst</id>
<published>2026-04-09T12:00:00-07:00</published>
<updated>2026-04-10T10:42:16-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Identity"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Identity"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Security"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Security"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Our family has used <a href="https://1password.com">1Password</a> for many years. Most recently 1Password 7, now at least three years out of date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring <a href="https://bitwarden.com">Bitwarden</a>. The best choice isn’t obvious; here’s the story thus far</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Our family has used
<a href="https://1password.com">1Password</a>
for many years. Most recently 1Password 7, now at least three years out of
date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring
<a href="https://bitwarden.com">Bitwarden</a>
. The best choice isn’t obvious; here’s the story thus far.
</p>
<p>
Important note: I suspect that most-to-all of the people reading this already are using a password manager. If you’re not,
please,
<i>
<b>PLEASE</b>
</i>
start now. Your browser probably has an OK one built-in, which is much better than
nothing.
<a href="https://www.cyber.gc.ca/en/guidance/password-managers-security-itsap30025">Here</a>
is a good write-up on the basics.
</p>
<h2 id="p-6">Our needs</h2>
<p>They’re not fancy. The house contains Macs and Androids and Windows and an iPad.
We have hundreds of accounts (some require an authenticator) and a basketfull of secure notes: Government-ID numbers, recovery
codes, and so on.</p>
<h2 id="p-5">1Password7 and 8</h2>
<p>1Password had this nice feature where you could sync between devices without involving any 1Password servers, in a variety
of ways. We used one of those and liked it.
1Password8 insists on storing your data (encrypted, more on that later). That always bothered me because, obviously, that
repository is a top-priority juicy target for all the bad guys, who range from employees of the Chinese government to geeky
narcos.</p>
<p>So we’ve been ignoring 1Password’s increasingly plaintive reminders that we were using years-out-of-date software
and chugging along with version 7. But, early this year, they broke our sync mode on the Android app and were pretty blunt that the only
way to get it back was to go to 1P8.</p>
<h2 id="p-7">Alternatives</h2>
<p>There are plenty of password managers (Let’s just say “PMs”) out there, but as a regular scanner of the landscape,
it seems to me that 1Password
(hereinafter “1P”) and Bitwarden (“Bw”) stand out as leaders. The rest of this piece will focus on those two.
If you think I’m wrong, say so below but also please say why.</p>
<p>Note that Bw comes in two flavors: That offered as a subscription service by the company of the same name, or as an open-source
software suite you can build and run yourself.</p>
<p>This is not to say that the PMs that are starting to appear built-in to browsers and OSes are worthless or unimportant,
just that some of us need a little more.</p>
<h2 id="p-8">The threat models</h2>
<p>
Two are obvious. The first is incompetence, like for example
<a href="https://en.wikipedia.org/wiki/LastPass#Security_incidents">LastPass</a>
, who apparently left the doors more or less
wide open to those bad guys I mentioned a few paragraphs ago. Complete horror-show.
</p>
<p>
The second is legal compulsion, where a government applies pressure to a PM provider to cough up our
secrets. Anybody who thinks governments won’t try is fooling themselves, because they’ve repeatedly said they want to, and are
eager to pass ill-considered legislation such as the
<a href="https://en.wikipedia.org/wiki/CLOUD_Act">CLOUD Act</a>
. So we care about that aspect a lot.
</p>
<h2 id="p-9">1P vs Bw: Security</h2>
<p>
I think they both have acceptably-good security postures; check out
<a href="https://bitwarden.com/help/bitwarden-security-white-paper/">Bitwarden Security Whitepaper</a>
and
<a href="https://support.1password.com/1password-security/">About the 1Password security model</a>
.
</p>
<p>Both of them offer to host your data outside of the US, specifically in Canada or the EU.</p>
<p>
But it doesn’t matter
<em>that</em>
much if a bad guy or bad government gets their hands on your password store; what
matters is whether or not they can decrypt it. I’m not an infosec professional but I know some and listen to them, and both
those security postures give me a good feeling. It’s not an accident that they’re pretty similar.
</p>
<p>
The actual threat isn’t so much that an adversary cracks the crypto; that’s very unlikely. It’s that they find a way to force
a PM vendor to build a back door into their software to get access to keys and passwords. For that reason, it would warm
my heart if either or both of Bw and 1P were to post a
<a href="https://en.wikipedia.org/wiki/Warrant_canary">Warrant Canary</a>
.
</p>
<p>But I’m going to give Bw a very slight edge. First, because of the fact that you can build and run it yourself, if you’re
willing to take responsibility for operating a server with strong security requirements. (I’m not.)</p>
<p>
The source being open potentially offers a second, and more important I think, advantage: If they were able to get a
<a href="https://en.wikipedia.org/wiki/Reproducible_builds">Reproducible build</a>
working, you’d have assurance that the code
you can download is the one their service is running. Which reduces the attack surface. (Mind you,
<a href="https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf">not to zero</a>
.) Reproducible
builds are hard, but if they did that, it would make a difference to me.
</p>
<p>
On the other hand, Bw’s software development process
<a href="https://contributing.bitwarden.com/contributing/ai/">embraces GenAI</a>
generally and Claude specifically.
At this stage in the growth of those technologies, this sends a chill up my spine. To be fair, 1P’s website
shouts that it’s just the thing for agentic security, whatever that means. And we don’t know anything about 1P’s internal
software-dev process.
</p>
<h2 id="p-10">1P vs Bw: Fit and finish</h2>
<p>1P wins this one. The problem is, do they always pop up when needed and never when they’re not? Can they fill every login
field that needs filling? Does the popup show you just what you need and nothing extraneous? I’ve used both and 1P is just
better.</p>
<h2 id="p-11">Business issues</h2>
<p>This one is also pretty well a saw-off. Both of them have taken substantial chunks of VC money and thus are going to
come under relentless pressure to enshittify. I worry a little less about this because from what I read,
there’s not much lock-in.</p>
<p>Personal experience too: I recently did an export of everything out of 1P and into Bw and it all Just Worked, albeit putting all
my stuff into a folder named "No Folder" that I can’t figure out how to rename.</p>
<p>Both Bw and 1P are subscription-only, at prices that seem fair to me.</p>
<h2 id="p-12">Death and recovery and pen and paper</h2>
<p>As I was reading up on this stuff, the issue of recovering access to your PM after it had been lost came up a couple of times.
Here’s a scenario where that could be really important: I die. And then my wife needs to get access to bank accounts and
business emails and so on.</p>
<p>Somebody (I’ve lost the link) was horrified that one of the PMs suggested writing the password down on a piece of paper as a
last-resort measure, but I’m here to tell you that they’re wrong. My wife has an envelope containing a piece of paper on which
appear the passwords for my PM and Mac, my mobile-phone PIN, and a very small number of other secret things she might really
need if I’m suddenly gone. I have no idea where she put it, but she’s really smart so I don’t worry.</p>
<p>You should probably do something like this too.</p>
<h2 id="p-13">What will we do?</h2>
<p>We’ve paid for a year’s worth of both Bw and 1P. At the moment, we’re leaning to 1P because it’s a little more polished.
Which matters because my PM is something I use many times every day. Also they’re somewhat Canadian.</p>
<p>If you think we’ve missed something, please do let us know.</p>
</div>
</content>
</entry>
<entry>
<title>Long Links</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links"/>
<link rel="replies" thr:count="2" type="application/xhtml+xml" href="/ongoing/When/202x/2026/03/24/Long-Links#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links</id>
<published>2026-03-24T12:00:00-07:00</published>
<updated>2026-03-26T16:36:32-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="The World"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="The World"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">This will be the 30<sup>th</sup> Long-Links outing. I’m 100% sure that there does not live a human being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to open one occasionally. All aboard!</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
This will be the 30
<sup>th</sup>
Long-Links outing. I’m 100% sure that there does not live a human
being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to
open one occasionally. All aboard!
</p>
<p>Sadly, more than half the Long Links, this time out, are about AI. I almost decided to bury the piece but, whatever you or I
think, the subject matters. And the ones I posted are a tiny fraction of those I read (or tried to) and I think are
useful and not immoral.</p>
<p>But, let’s put all the non-AI stuff at the front so you can stop reading partway through if you’ve just had enough of
that stuff.</p>
<h2 id="p-1">Not about GenAI</h2>
<p>
Paul Ford has, after a lengthy gap, started writing again at
<a href="https://ftrain.com">ftrain.com</a>
. Excellent!
Go there any day and there’ll almost certainly be something good at the top of the
page. He’s a technologist and, yeah, writes about AI sometimes, but
<a href="https://ftrain.com/warp-and-woof">Warp and Woof</a>
is about dogs and their people. Charming.
</p>
<p>
I think most people who aren’t ultra-wealthy now agree that inequality is currently a central problem of our society. But it
would be nice to put some numbers behind that assertion.
<a href="https://paulkrugman.substack.com/p/talking-with-gabriel-zucman">Here</a>
is a conversation between Paul Krugman,
Nobel-prizewinning economist, and Gabriel Zucman, a French specialist in the subject and frequent Piketty collaborator.
Now, there are quite a few paragraphs up front of talk about general macroeconomic issues and comparisons between the US and Europe,
which I enjoyed reading. And then inequality; here’s Zucman: “And so everybody now understands what was long understood for
centuries, very much including in the West, which is that extreme wealth is never virtual, it is always extreme power.”
</p>
<p>
CO
<sub>2</sub>
densities in Parts Per Million are a good measure of how full your inhalations are of others’ exhalations. And
thus of how likely you are to catch something by breathing. Especially, Covid, which everyone with a half a brain knows is not
nearly over. Anyhow, A. Grieve-Smith offers
<a href="https://grieve-smith.com/ftn/2026/03/nine-observations-from-carbon-dioxide-monitoring/">Nine observations from carbon
dioxide monitoring</a>
: “I’ve been checking carbon dioxide levels for over three years now, and I’ve started to see patterns.”
This piece could save your life, and that’s not a metaphor.
</p>
<p>
Patrick McKenzie, who writes
<cite>Bits About Money</cite>
, has an icy-cool style and this Link could be a Little Less Long,
but I learn interesting things every time I read one of his pieces.
<a href="https://www.bitsaboutmoney.com/archive/fraud-investigation/">Fraud Investigation is Believing Your Lying
Eyes</a>
launches from the Minnesota child-care fraud story, but is mostly, as the title suggests, relates the conventional wisdom
(which I didn’t know) about how to go sniffing around for in-progress fraud.
From which “As a fraud investigator, you are allowed and encouraged to read Facebook at work.”
</p>
<p>
Hari Kunzru has written good books and is a former London native.
<cite>Harpers</cite>
gave him an assignment:
Walk around and write about the city, thus
<a href="https://harpers.org/archive/2026/02/another-london-situationists-hari-kunzru/">Another London: Excavating the
disenchanted city</a>
. It’s a tour through time as much as space
<span class="dashes"> —</span>
London, obviously, is
history-drenched
<span class="dashes"> —</span>
and not just politics and power either, but arts and ideas. The writing is
beautiful. It’ll take a chunk out of your day but the trade-off is good.
</p>
<p>
Here’s something beautiful:
<a href="https://thehtml.review/05/">The HTML Review</a>
. Now I want to publish there, but I’d have to up my
writing game.
</p>
<h2 id="p-5">Lankum</h2>
<p>
They’re an Irish band I just discovered, courtesy of Qobuz. The music grows out of traditional Irish acoustic folk. They play
old and new songs and throw in a heavy dose of snarl and drone. Some of the chords are like rotated model augmented 11ths or some
such, scratchy around the edges but helped with an itch I hadn’t known I had. Terrific musicians. Here’s
<a href="https://www.youtube.com/watch?v=lUReQ9GhT8s">Hunting the Wren</a>
. I might get over-excited and fly to Ireland to see them.
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/24/Lankum.png" alt="Lankum in concert"/>
<h2 id="p-2">Tech, but not GenAI</h2>
<p>
Sebastian Pipping is, among other things, an Open-Source software developer, with whom
<a href="/ongoing/When/202x/2021/03/24/XMLWF-dash-k">I’ve collaborated</a>
. His recent
<a href="https://blog.hartwork.org/posts/learn-from-me/">Learn from me!</a>
begins “Not too long ago, someone literally asked me
what they "could learn from me", and that question has stuck with me since.” So he offers a few candidate lessons. What a nice
idea! What could people learn from
<em>you</em>
?
</p>
<p>
Filippo Valsorda, another OSS dev, is particularly interesting because he and a few partners have apparently figured out
<a href="https://geomys.org">how to make a living from their work</a>
.
He recently published
<a href="https://words.filippo.io/dependabot/">Turn Dependabot Off</a>
and I’m not going to offer a word of explanation because
if you understand the title I guarantee you’ll be interested in the piece. (I’m terrified of Dependabot.)
</p>
<p>
It seems like every day I hear from another person who’s trying to get their personal lives off Big Tech. Me too. So…
In
<cite>The Verge</cite>
,
<a href="https://www.theverge.com/tech/879114/best-big-tech-app-alternatives-installer">How to un-Big Tech your online life</a>
.
And from Paris Marx,
<a href="https://disconnect.blog/getting-off-us-tech-a-guide/">Getting off US tech: a guide</a>
. We are in the early stages of
de-Googling our family life, so this stuff is super useful. I expect to see more of it.
</p>
<h2 id="p-4">Amazon polemics, maybe a little AI</h2>
<p>I don’t loathe Amazon any more nor less than the rest of the Big Techs, but boy are there are a lot of people
publishing diatribes against the company. Not sure I understand why. But, worth reading.</p>
<p>
In
<a href="https://markatwood.substack.com/p/how-amazon-dies-a-possible-maybe?">How Amazon Dies: A Possible, Maybe Likely
Future</a>
Mark Atwood predicts that the infestation of amazon.com with highly-profitable advertising is a perhaps-fatal
blunder. What’s maybe more interesting is that he points out several potential Amazon alternatives that don’t suffer from
that same infestation; they hadn’t occurred to me.
</p>
<p>
And from a year ago, Cory Doctorow’s
<a href="https://pluralistic.net/2025/03/13/electronic-whipping/#youre-next">The future of Amazon coders is the present of
Amazon warehouse workers</a>
introduces the “shitty technology adoption curve”. I missed this piece at the time but boy, is it
easy to believe.
</p>
<p>
Finally, reading
<a href="https://www.bigtechnology.com/p/writing-crystalized-thinking-at-amazon?">Writing Crystalized Thinking At Amazon. Is AI
Muddying It?</a>
angered me. While I have no remaining respect or affection for any of the Big Techs, I enjoyed my time at AWS
and part of it was the writing culture. I think the Way Of The Six-pager is the best business-process innovation I witnessed in
my working life. If Amazon really is slopifying it, I predict disastrous outcomes.
</p>
<h2 id="p-3">OK, here’s the AI stuff</h2>
<p>My own position, just to be clear: There are going to be LLM applications in a few domains here and there, and one of them is
software development, but they won’t be nearly big enough to damage earth’s climate any further, nor to prevent the bubble from
popping. That said…</p>
<p>
Let’s do the worst first:
<a href="https://www.heavybit.com/library/article/write-only-code">Write-Only Code</a>
lays out a genuinely frightening future.
Quote: “I was maniacally insistent that any proposed change to our SDLC (software development life cycle) be evaluated first
through the lens of developer velocity.”
I think I’d rather not go there.
</p>
<p>
Most of us who watch the space, and have no idea where it’s going or what the future holds, are I think particularly
interested in Anthropic’s Claude. If you’re one, you’ll probably enjoy
<a href="https://www.newyorker.com/magazine/2026/02/16/what-is-claude-anthropic-doesnt-know-either">What Is Claude? Anthropic
Doesn’t Know, Either</a>
.
</p>
<p>
It’s probably not that GenAI is intrinsically immoral. As Karl Bode writes,
<a href="https://karlbode.com/the-problem-with-ai-is-shitty-human-beings/">The Problem With AI Is Shitty Human Beings</a>
. I
covered some of the same territory last year in
<a href="/ongoing/When/202x/2025/07/06/AI-Manifesto">The Real GenAI Issue</a>
, but Bode is excellent:
“…the grand vision of modern automation's benefits can never materialize if its stewards are
<i>foundationally fucking terrible
human beings disinterested in the contours of empathy.</i>
If we're not talking prominently about that, we aren't really talking at
all.” (Emphasis his.)
</p>
<p>
One of the things that shitty people do is lie. Like for example charismatic leaders of AI “startups” valued in the tens of
billions. But then so do the less-visible, which provoked Kyle Kingsbury A.K.A. Aphyr to write
<a href="https://aphyr.com/posts/405-trudging-through-nonsense">Trudging Through Nonsense</a>
. It’s sad and angry but I think
usefully so.
</p>
<p>
Armin Ronacher is not bursting with rage, but he is skeptical about all the right things in
<a href="https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/">Some Things Just Take Time</a>
. Quote:
“There’s a feeling that all the things that create friction in your life should be automated away. That human involvement should
be replaced by AI-based decision-making. Because it is the friction of the process that is the problem. When in fact many times
the friction, or that things just take time, is precisely the point.”
</p>
<p>
For another cool-voiced critique, here’s Rishi Baldawa:
<a href="https://rishi.baldawa.com/posts/ai-mandates-manufacture-noise/">AI Mandates Manufacture Noise</a>
. While I’m not
entirely a burn-it-all-with-fire GenAI foe, the “boss mandate” always struck me as dumb, and Rishi spells it out clearly
and simply. It’s really good, so here are a couple of quotes: “But those not in the weeds had no way to know any of this
because… well they aren’t in the weeds. So they feel compelled to solve their information gap with a policy hammer.” and
“As said before, none of this is revolutionary and that’s sort of the point. AI is a ’mirror and multiplier‘. It intensifies
whatever was already happening.”
</p>
<h2 id="p-6">That’s all</h2>
<p>Let’s really hope the bubble bursts soonest. Because when the money goes away, so will a lot of the shitty people.</p>
</div>
</content>
</entry>
<entry>
<title>Nash Burns Saves the Day</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2026/03/20/Nash-Burns#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns</id>
<published>2026-03-20T12:00:00-07:00</published>
<updated>2026-03-20T13:53:25-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Web"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Web"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their emails to us were bouncing. Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on. Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly price, and has been trouble-free</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their
emails to us were bouncing.
Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on.
Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly
price, and has been trouble-free.</p>
<p>So, what could be wrong? We investigated and discovered that Google was offering a new-and-improved MX-record option,
although they emphasized that the old setup should still work. Anyhow, we installed the New Thing and it didn’t help.</p>
<p>
So, we filed a ticket with CWH tech support and somebody got back to us pretty quick, saying they’d changed a firewall
setting that was blocking connections to Germany. I detect the scent of GDPR, but whatever.
<br/>
Euro-email: Bounce, bounce.
</p>
<p>
CWH: Probably an MX-record issue, and we should wait for DNS propagation. Several days passed and
bounce, bounce, bounce.
<br/>
Us: “Not DNS propagation.”
<br/>
CWH: “Still could be.”
</p>
<p>So we VPN’ed to Germany and discovered we couldn’t ping
Textuality’s IP address. Smells like a firewall to me. We told CWH that.</p>
<p>
CWH: We have made some changes to firewall settings.
<br/>
EMail: bounce, bounce, bounce.
<br/>
VPN+Ping: Request timeout, request timeout, request timeout.
</p>
<p>
CWH: Try traceroute?
<br/>
VPN+Traceroute: 14 hops, no joy.
</p>
<p>
CWH: Your VPN settings must be wrong. Here are instructions to use Windows PC VPN correctly.
<br/>
Us: Thanks but no.
</p>
<p>
CWH: Your MX records are configured incorrectly.
<br/>
Us: No, they are correct per Google guidance. We sent an email beginning
“Please believe us.”
</p>
<p>CWH: It must be DNSSEC. Check to see if your registrar implements DNSSEC. <br/>Us: We are using your DNS servers.</p>
<p>CWH: Perhaps your registrar is broadcasting an old record? <br/>Us: Our registrar doesn’t do DNSSEC.</p>
<p>At this point we consulted a friend who’s an expert on DNS and Email and even DNSSEC. He verified that not only could
you not ping
Textuality from Germany, you also couldn’t ping CWH or its name servers. Firewall firewall firewall!</p>
<p>
CWH: “I did test the site access using a 3rd party application, and it seems to be accessible on all parts.”
<br/>
Us: Look at the
output, it shows we can’t be reached from anywhere in Germany.
</p>
<p>
Also, for all the remaining messages in the email trail, we prefixed our input with bold face extra-large text reading:
<b>Systems located in Germany cannot ping Textuality.com’s IP address, nor can they ping the IP addresses of textuality.com’s
designated name servers. This is the problem.</b>
</p>
<p>CWH: Let’s try migrating you to a different server; try pinging these hostnames. <br/>VPN+Ping: Nope.</p>
<p>
CWH: Are you sure it’s not your VPN settings?
<br/>
Us: Are you sure it’s not your GDPR settings?
<br/>
CWH: Raising your issue to Tier 3.
</p>
<p>20 hours pass, then we get email from:</p>
<h2 id="p-1">Nash Burns!</h2>
<p>…who said “This has been fixed.” It was.
Nash’s email signature was “Nash(Rajaneesh) B”. What a great name, though. Thanks, Nash.</p>
<h2 id="p-2">Am we mad?</h2>
<p>Not really. Consumer-facing tech support is hard. None of their suggestions were unreasonable.
Doing GDPR correctly is hard.
They’ve been just fine for years and were having a bad week.
Could we expect better from any of CWH’s local competitors? Probably not.</p>
<p>It wasn’t funny at the time, but looking back, it kind
of is.</p>
</div>
</content>
</entry>
<entry>
<title>Pure Sound Please</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2026/03/16/Pure-Sound-Please#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please</id>
<published>2026-03-16T12:00:00-07:00</published>
<updated>2026-03-18T14:34:31-07:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts/Music"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Music"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">This last weekend we attended a concert entitled <cite>Lenten Reflection</cite> at Vancouver’s Catholic <a href="https://en.wikipedia.org/wiki/Holy_Rosary_Cathedral_(Vancouver)">Holy Rosary Cathedral</a> featuring the <a href="https://bellevoci.ca">Belle Voci</a> vocal group and the <a href="https://chilliwacksymphony.com/cantare-super-orchestram/">Cantare Super Orchestram</a> early-music band. The music was fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below). And so I get to report on good music and yell at production people</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
This last weekend we attended a concert entitled
<cite>Lenten Reflection</cite>
at Vancouver’s Catholic
<a href="https://en.wikipedia.org/wiki/Holy_Rosary_Cathedral_(Vancouver)">Holy Rosary Cathedral</a>
featuring the
<a href="https://bellevoci.ca">Belle Voci</a>
vocal group and the
<a href="https://chilliwacksymphony.com/cantare-super-orchestram/">Cantare Super Orchestram</a>
early-music band. The music was
fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below).
And so I get to report on good music and yell at production people.
</p>
<p>A cathedral is a nice place for a concert!</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_215727574.png" alt="Interior of Vancouver’s Holy Rosary Cathedral"/>
<p>
The concert opened with just the singers, their voices drifting down from a high place behind us, a balcony or choir loft.
There was no incremental accompaniment and no amplification; the music flowed from vocal cords to
eardrums
<span class="dashes"> —</span>
not directly, of course, there was lots of reflection and reverberation introduced by the
Cathedral space. The singers were polished and expressive and the sound, drifting through the vast space, beyond exquisite.
</p>
<p>
They sang a lovely piece by Byrd (1539-1623). Then the instrumentalists played a number by von Biber (1644-1704) while the
singers snuck downstairs. Joined, they performed Bach’s BWV
<a href="https://en.wikipedia.org/wiki/Komm,_Jesu,_komm,_BWV_229">229</a>
and
<a href="https://en.wikipedia.org/wiki/Nach_dir,_Herr,_verlanget_mich,_BWV_150">150</a>
, then pieces by Pergolesi (1710-1736)
and Steffani (1654-1728).
</p>
<p>
The Bach pieces, as usual, had more music in the music, but the others were also fun. It was a small ensemble: In
the choir, five sopranos, five altos, a countertenor, four each tenors and basses. The band had five baroque
violins, a baroque viola, a baroque cello, a
<a href="https://en.wikipedia.org/wiki/Violone">violone</a>
(think, string bass with frets), a baroque bassoon, and a player
doubling on harpsichord and organ. Thus, an ensemble quite likely not too much bigger or smaller than the ones playing this
music in the 1700s, when it was new.
</p>
<h2 id="p-2">That sound</h2>
<p>Once again, the sound was something special and yeah, the musicians were excellent, but for me, the key thing was the lack of
amplification: vocal cord to eardrum via cathedral. It’s always seemed obvious to me that you can’t run music through a bunch of
electronics and speaker mechanics without changing it; if only spatially, with the sounds coming from speaker diaphragms located
somewhere away from the human musician.
To my ears, there is a fragile magic in pure unamplified sound. I lack the words to describe the difference but it’s not
subtle.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_212418188.png" alt="“Lenten Reflections” concert singers and players"/>
<p>Does this mean that everything was perfect? No; the choir was a little bit male-heavy; some of the soprano and especially
alto lines were part-hidden behind the massed male voices. Also, the bassoon was right at the front of the stage;
While the playing was fine, it felt as though it were musically, not just physically “in front of” the band and
singers.</p>
<p>Both of these could have been fixed, by telling the men to take it down a notch or having one or two fewer of them. And by
moving the bassoon back to the usual woodwinds spot behind the strings. Still, these were very minor imperfections.</p>
<p>Oh, and the performance and sound of the bass line on that violone was absolutely awesome; clearly audible as a thing on its
own while it wove all the other musical threads together.</p>
<p>
I’ve discovered that few classical musicians share my passion for unamplification. I hear things like “I want a
<em>full</em>
sound or “The soloists need to cut through the orchestra.” Which, well, OK, but somehow people managed to
accomplish those things for centuries, before amplifiers and speakers were invented.
</p>
<h2 id="p-1">22 months?</h2>
<p>
That’s since May of 2024 when I took in the
<a href="/ongoing/When/202x/2024/05/26/TTB">Tedeschi-Trucks Band</a>
, whose music couldn’t be more different from anything
called “Lenten Reflections”: electric not acoustic, profane not sacred. But crystal clear and perfectly balanced
sound; so much better than most electric bands achieve.
</p>
<p>My sincere thanks to the musicians and their leaders for a lovely experience. And my message to everyone co-ordinating and
leading live music performances: Of course the first priority has to be the quality of the music, but think about the sound and
try to be better. Better than than most performances manage, these days.</p>
<p>We know it’s possible.</p>
</div>
</content>
</entry>
<entry>
<title>Because Algospeak</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak"/>
<link rel="replies" thr:count="2" type="application/xhtml+xml" href="/ongoing/When/202x/2026/03/05/Because-Algospeak#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak</id>
<published>2026-03-05T12:00:00-08:00</published>
<updated>2026-03-07T10:29:41-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Language"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Language"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Life Online"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Life Online"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Recently I read <a href="https://en.wikipedia.org/wiki/Because_Internet">Because Internet</a> by <a href="https://gretchenmcculloch.com">Gretchen McCulloch</a> and <a href="https://en.wikipedia.org/wiki/Algospeak_(book)">Algospeak</a> by <a href="https://en.wikipedia.org/wiki/Adam_Aleksic">Adam Aleksic</a>. The language we speak (and text) to each other is at the core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth. So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Recently I read
<a href="https://en.wikipedia.org/wiki/Because_Internet">Because Internet</a>
by
<a href="https://gretchenmcculloch.com">Gretchen McCulloch</a>
and
<a href="https://en.wikipedia.org/wiki/Algospeak_(book)">Algospeak</a>
by
<a href="https://en.wikipedia.org/wiki/Adam_Aleksic">Adam Aleksic</a>
. The language we speak (and text) to each other is at the
core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth.
So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry.
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/covers.png" alt="The covers of “Because Internet” and “Algospeak”"/>
<h2 id="p-1">Because Internet (2019)</h2>
<p>Its approach is historical and its voice fairly uninflected. It smiles and
argues, but it doesn’t ROFL nor does it YELL AT YOU. The history is longer, perhaps, than most people reading this have
been online (or even alive). Ms McCulloch goes back to the days of BBSes (“bulletin-board systems”) and ListServs and IRC. Some of
the jargon and formulations of those days live on; you’d be surprised.</p>
<p>Here’s her table of contents.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/BI-toc.png" alt="Table of Contents from “Because Internet”"/>
<p>The analysis is grounded in the formalisms of the author’s profession, academic linguistics. Nothing wrong with that.</p>
<p>Let’s look at a couple of her ideas, beginning with Chapter 1’s “Informal Writing”. A few of us, back in the late
Eighties, noticed that computers in general and the then-nascent Internet in particular were driving a writing
renaissance.</p>
<p>Before computers, a knowledge worker who had laboriously constructed essays in college quite likely wrote
almost nothing for the rest of their working life. People talked face-to-face or on the phone, and dictated to
secretaries. Written communication was seen as necessarily formal and disjoint from the way we spoke, or that we wrote in
personal correspondence. Then, suddenly, everyone was sitting at a keyboard only seconds away from everyone else’s screen.
McCulloch goes deep on this:</p>
<blockquote>
<p>In the future, the era of writing between the invention of the printing press and the internet may come to be
seen as an anomaly—an era when there arose a significant gap between how easy it was to be a writer versus a reader. An era when
we collectively stopped paying attention to the informal, unedited side of writing and let typography become static and
disembodied.</p>
<p>The internet didn’t create informal writing, but it did make it more common, changing some of our previously spoken
interactions into near-real-time text exchanges.</p>
</blockquote>
<p>From which all of this follows. It feels like a central insight. I suppose you could argue that centrality of informal text
is fading in the face of short-form video. Maybe,
it’s too soon to tell.</p>
<p>Then consider chapter 5, about emojis. Linguists obviously need to think about them because now they’re an
integral part of written language. McCulloch’s insight is that they correspond almost exactly to gestures, the way we use
our hands to add force to our speech. Obviously, for example, “👍”. Or when you’re talking about something completely
loopy and you twirl your index finger by your ear? You meant “🤪”.</p>
<p>I offer the emoji story for flavor, an example of a linguist’s approach to what we’re doing to our language with our
networks.</p>
<p>
McCulloch has lots more of this stuff.
I enjoyed
<cite>Because Internet</cite>
a lot, partly because I’m old and my memories stretch back to those BBS and
IRC days and I had a front-row seat for the decades of linguistic seething and heaving. And also because I’m a
<a href="https://www.rfc-editor.org/rfc/rfc9839.html">Unicode geek</a>
.
</p>
<h2 id="p-2">Algospeak (2025)</h2>
<p>The subtitle is “How Social Media Is Transforming the Future of Language”. OK, but…
Social media is a fertile field for language evolution. Thing is, corporate social media discourse
lives in the dire grip of the proprietors’ algorithms. And that’s where Adam Aleksic focuses. He treats all of them
as a single opaque object, “The Algorithm”, which I think is fair because they all are designed with one goal: To
maximize the effectiveness of human conversation at generating advertising revenue.</p>
<p>First, the Table of Contents.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/AS-toc.png" alt="Table of Contents from “Algospeak"/>
<p>Aleksic knows whereof he speaks: As “Etymology Nerd”, his aggregate following across TikTok, Instagram, and YouTube is
over three million. He’s all about cool bits and pieces of
linguistics, often Internet-specific usages.
If I had the patience for podcasts I suppose his would be near the top of my list.</p>
<p>
He really enjoys his work and has fun talking about some of Social Media’s more colorful linguistic extrusions; check
that Table of Contents. I’m kind of old and I learned a lot about the words and emojis younger folk emit, and I think most folks,
even those just out of their teens, would too. I’m on a Discord for a
<a href="/ongoing/What/Sports/Soccer/">Major League Soccer</a>
team’s fans, and while it’s totally all-ages, I can say I am regularly
less mystified than I was before I read
<cite>Algospeak</cite>
.
For example, now I know what it means when someone tosses “💀” into a chat. Do you?
</p>
<p>
Aleksic isn’t averse to a little history himself. Looking back over the successive online-jargon volcanoes, he argues
convincingly that two stand out as extra productive. First of all, the short-lived (but hot stuff at the time)
<a href="https://en.wikipedia.org/wiki/Vine_(service)">Vine</a>
video platform. Second, the incel cesspool; sad but
(apparently) true.
</p>
<h2 id="p-3">The Algorithm</h2>
<p>Remember, it’s all about what advertisers want. And wow, do they ever want a lot of things. I’ll just touch on a few of
Aleksic’s points.</p>
<p>First of all, they don’t want to find themselves next to downers. So if you want to talk about death or suicide or rape or
racism or rage,
you need to fool The Algorithm. Thus “unalive” and many other dodges. Of course, The Algorithm learns about them so you
have to keep dodging. Neither side of this struggle can stay ahead for long.</p>
<p>Here’s another thing I didn’t know: Apparently written Chinese is particularly rich in techniques for euphemizing, making it
easier for users of that language to evade, for a time, The Algorithm.</p>
<h2 id="p-4">Partitioning people</h2>
<p>Another big thing The Algorithm likes is grouping people into smaller and smaller baskets based on interests, generations,
and many other criteria. This is because advertisers can aim very specific campaigns at just exactly the right cohort of people who
are likely to buy what they’re selling. Here’s a quote; See how the language fills in behind advertisers’ pressure?</p>
<blockquote>
<p>
It doesn’t matter how much I label myself. If I’m a demisexual goblincore Gen
Z Swiftie, I guarantee there are still others like me. The only thing these labels really change about me is that they make me
easier to classify and market to. Ironically, true individuality may come out of a
<em>lack</em>
of labels and stories, because
there’s greater freedom of expression with a blank slate. If everybody’s the “main character,” then nobody is.
</p>
</blockquote>
<p>
<cite>Algospeak</cite>
, unlike
<cite>Because Internet</cite>
, doesn’t limit itself to written language. One of its most
compelling studies concerns the vocal techniques of podcasters and YouTubers. The finding is simple: It’s hard to build and hold an
audience for your show unless you sound like MrBeast. No, really.
</p>
<p>
Anyhow, they’re both good books.
<cite>Because Internet</cite>
educated and entertained me.
<cite>Algospeak</cite>
is way
more intense, intentionally more like the subject it addresses. Also it made me angry. I am a lover of human language and of its
patterns of growth and mutation and simplification and complexification. Linguistics is one of the disciplines I regret not
having chosen.
</p>
<p>Aleksic makes it clear that there’s an amusing narrative about how the people living and speaking in the shade of the Algorithm
can never defeat it, but they can still manage to get their messages across. But they shouldn’t have to struggle!</p>
<p>In fact, a few million of us have found a place to talk to each other that isn’t in The
Algorithm’s shadow: Decentralized social media. Specifically the Fediverse (what people mean when they say “Mastodon”) and maybe
the ATmosphere (same for “Bluesky”).</p>
<p>I want to see how language grows in a place where new forms arrive when they’re needed, to say new things that need to be
said. Not to either serve or resist The Algorithm.</p>
</div>
</content>
</entry>
<entry>
<title>Kansas and AI</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI"/>
<link rel="replies" thr:count="2" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/27/Kansas-and-GenAI#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI</id>
<published>2026-02-27T12:00:00-08:00</published>
<updated>2026-02-27T16:06:19-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="AI"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud. Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural changes.” Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud.
Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural
changes.”
Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010.</p>
<h2 id="p-1">The Kansas Experiment</h2>
<p>As long as I can remember, a certain class of right-wing evangelists has preached that cutting taxes would stimulate business
growth and everyone would come out ahead. There are a couple of problems with this theory. First, mainstream economists
almost universally think it’s just wrong. Second, most of the people pushing it are rich and would
benefit from the cuts.</p>
<p>
Anyhow, in 2010 US Senator Sam Brownback won the race for governor of Kansas on what was then called the “Tea Party” program:
Prosperity through tax cuts. Tea-party Republicans also won a large majority in the state legislature. Unsurprisingly they
immediately
<a href="https://en.wikipedia.org/wiki/Kansas_experiment">did what they said they were going to do</a>
: Slashed a wide variety
of taxes, some to zero.
</p>
<p>The predicted prosperity failed to happen. The state government’s revenue plunged and it had to dig deep into rainy-day
reserves just to keep the doors open. There were brutal cuts to policing, road repair, and schools. Also a nasty
feedback loop: As the state’s fiscal position worsened, its credit rating fell and interest rates rose, leading to yet more
brutal austerity measures.</p>
<p>Another result was that affluent Kansans made out like bandits; the cost of running the state was substantially
transferred to the less financially fortunate.</p>
<p>In 2017, the legislature threw in their cards and repealed the tax cuts, overriding Brownback’s veto.</p>
<p>While this was a terrible experience for most Kansans, it is historically useful, because whenever you encounter a
tax-cut nut (probably self-interestedly wealthy) you can say “But, Kansas!” Having said that, there are still plenty of
those nuts, and they’ll tell you that the Kansas experiment failed because of one fine-tuning effort or another. That’s a position
that’s hard to defend, though.</p>
<h2 id="p-3">Sidebar: Trans oppression too</h2>
<blockquote>
<p>
Before I move onto the AI angle, I gotta pause to acknowledge this week’s news story about the Kansas
government’s vicious, brutal, and ignorant
<a href="https://www.theguardian.com/us-news/2026/feb/26/kansas-trans-drivers-license-law-assault-on-rights">assault on trans
people</a>
. To be clear, I think the shitty people who hate trans folk are aren’t necessarily the same shitty people as the shitty
people who don’t want to contribute to the public good. But, something about Kansas seems to attract both
flavors.
</p>
</blockquote>
<h2 id="p-2">The GenAI experiment</h2>
<p>The core value proposition of contemporary AI technology is exactly what Dorsey seems to think: Fire half your
employees and profits will soar! If that’s true, the trillion dollars or so invested so far will seem like small potatoes. Since
we don’t know if
this will actually work, anyone who actually does it is conducting an experiment. Just like Sam Brownback did.
Unsurprisingly, the investor class loves this experiment and is putting their money on it working.</p>
<p>
To be fair, voices have been raised to argue that the tech sector is a special case: That following on
feverish over-hiring during the Covid lockdown, they need to slash headcount anyhow, and are using AI as an excuse.
For example
<a href="https://daringfireball.net/linked/2026/02/27/block-layoffs">John Gruber</a>
.
</p>
<p>I personally
am unconvinced, but even if they’re right, it’s irrelevant. The shareholding class won’t be able to see past that 24% payoff. So
as of today, they’ll be yelling at every CEO on the planet to start pulling the mass-firing trigger. Or else.</p>
<p>I think I know how the experiment will turn out. Just like in Kansas, it’s not going to be fun.</p>
</div>
</content>
</entry>
<entry>
<title>Crocuses of 2026</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/24/Crocuses-of-2026#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026</id>
<published>2026-02-24T12:00:00-08:00</published>
<updated>2026-02-26T13:46:17-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts/Photos"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Photos"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth in early 2003. Except for last year. Because <a href="/ongoing/When/202x/2025/02/28/Moved">we moved</a> and the new place didn’t have any. Only now it does, and they’re (just barely) up. <i>[Update: Up and open, too.]</i></div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth
in early 2003. Except for last year. Because
<a href="/ongoing/When/202x/2025/02/28/Moved">we moved</a>
and the new place didn’t have any. Only now it does, and they’re
(just barely) up.
<i>[Update: Up and open, too.]</i>
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56234.png" alt="Crocuses of February 2026"/>
<p>
Long-time followers may note that they’re pale and fragile compared to the exuberant blossoms of previous
years. Not sure why, but our new place faces north and there’s this enormous
<a href="https://en.wikipedia.org/wiki/Fraxinus_americana">White Ash</a>
tree right in front of it, so they’re not getting as
much sun as at the south-facing former joint.
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56235.png" alt="Crocuses of February 2026"/>
<p>And also this is their first spring. We bought the bulbs and hired a professional with the right tools to jam them
into the earth last autumn, between the big tree’s roots. So they really haven’t had a chance to get their own root systems going.</p>
<p>And finally, it really is the first day that’s bright and warm enough to get out the camera. Maybe they’ll
be better in another few days. And quite likely next Spring.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56244.png" alt="Crocuses of February 2026"/>
<p>This would be the place to introduce whatever metaphor this year’s blossoms, fighting their way through the leaf cover in
chilly air toward the sun, fit into, but I’m not gonna.</p>
<p>
I, like many, am
<a href="/ongoing/When/202x/2023/10/25/Wild-World">not dealing very well</a>
with what I see when I look at the world in either
the big or the ultra-local landscapes.
The world in tough shape and its worst people are making it worse.
People I love are in ugly corners and not finding help.
</p>
<p>But you know, the flowers, in their low-key way, look great and so does the tree, still in wintersleep. Today the
sun was shining on them. It’ll be warmer and nicer soon.</p>
<p>Metaphors can go to hell. It’s just late-winter light on pale violet petals. Enjoy the moments you have with it.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56249.png" alt="Spring crocus, now open for business"/>
<div class="caption">
<p>Update: Now open for business.</p>
</div>
</div>
</content>
</entry>
<entry>
<title>Open Source and GenAI?</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion"/>
<link rel="replies" thr:count="2" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion</id>
<published>2026-02-16T12:00:00-08:00</published>
<updated>2026-02-18T13:41:14-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="AI"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">I’ve been puttering away on my <a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a> project since 2023. In the last few weeks GenAI has intervened. <a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Quamina + Claude, Case 1</a> describes a series of Claude-generated human-curated PRs, most of which I’ve now approved and merged. <a href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2">Quamina + Claude, Case 2</a> considers <a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>, a largely-Claude-driven port from Go to Rust. Both of these stories seem to have happy endings and negligible downsides. So empirically, I <em>can</em> apply LLM technology usefully to software development. But should I?</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I’ve been puttering away on my
<a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a>
project since 2023. In the last few weeks GenAI
has intervened.
<a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Quamina + Claude, Case 1</a>
describes a series of
Claude-generated human-curated PRs, most of which I’ve now approved and merged.
<a href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2">Quamina + Claude, Case 2</a>
considers
<a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>
, a largely-Claude-driven port from Go to Rust.
Both of these stories seem to have happy endings and negligible downsides. So empirically, I
<em>can</em>
apply LLM
technology usefully to software development. But should I?
</p>
<h2 id="p-3">Conclusions 1: Burn it with fire?</h2>
<p>
Let me be clear: In the big GenAI picture, I’m a contra. Why? I’ll pass the mike to Baldur Bjarnason, my
favorite among GenAI’s blood enemies.:
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">“AI” is a dick move</a>
.
His tl;dr is something like “GenAI is environmentally devastating and has the goal of throwing millions of
knowledge workers onto the street and is being sold by the worst people and is used for horrible applications and will increase
society’s already-intolerable level of inequality!” To which I reply “Yes, yes, yes, yes, and yes.”
</p>
<p>At the end of the day, the business goal of GenAI is to boost monopolist profits by eliminating decent jobs, and
damn the consequences. This is a horrifying prospect (although I’m somewhat comforted by my belief that it basically won’t
work and most of the investment capital is heading straight down the toilet).</p>
<p>But. All that granted, there’s a plausible case, specifically in software development, for exempting LLMs from this
loathing.</p>
<p>
First of all, size.
<a href="https://www.jetbrains.com/lp/devecosystem-data-playground/#global_population">JetBrains thinks</a>
that
the world has 21 million or so software developers, i.e. less than 1% of the earth’s working population.
Vanishingly small in the context of the lunatic tsumani of LLM overinvestment.
Training and operating the models required for a market this small is
rounding error measured on the Great GenAI Overbuild scale. There aren’t enough geeks to create a detectable bump in the global
carbon load.
</p>
<p>
Another odious aspect of LLMs is
<a href="https://en.wikipedia.org/wiki/Reinforcement_learning_from_human_feedback">RLHF</a>
, “Reinforcement Learning From Human
Feedback”, which relies on underpaying Third-Worlders to
polish the models’ outputs.
My guess is that much less is required for code-oriented LLMs.
The combination of the compiler and your unit tests provide good starter guardrails. Then skilled
professional intervention is required to deal with the remaining misfires, as with those Quamina PRs.
</p>
<p>Finally, it seems making billionaires into multibillionaires is intrinsic to GenAI dreams. But software-development tools won’t
do that. Once again, the market is just too small. But even if it weren’t, consider this from Steve Yegge:</p>
<blockquote>
<p>
For
<a href="https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163">this blog post</a>
, “Claude Code” means “Claude Code and
all its identical-looking competitors”, i.e. Codex,
Gemini CLI, Amp, Amazon Q-developer ClI, blah blah, because that’s what they are. Clones.
</p>
</blockquote>
<p>(GenAI, overbuilding wherever you look.) None of these products have moats and the chance that any of them become
extractive monopolies is about zilch. Nobody’s ever built a major cash-cow on developer tooling</p>
<p>One reason is (*gasp*) Open Source. Does anybody doubt that in the near future, there will
be entirely open-source versions of what Yegge means by “Claude”?</p>
<p>So, if you want to condemn the use of GenAI in software development, I think you need arguments other than the fact that
it’s also being promoted for societally-toxic business purposes.</p>
<p>I have a few. But stand by, let me push that on the stack and turn to
technology for a bit.</p>
<h2 id="p-4">Conclusions 2: Engineering sanity?</h2>
<p>Question: Can LLMs even participate in quality software engineering?
Baldur doesn’t think so: “The gigantic, impossible to review, pull requests. Commits that are
all over the place. Tests that don’t test anything. Dependencies that import literal malware. Undergraduate-level security
issues. Incredibly verbose documentation completely disconnected from reality.”</p>
<p>I’m not saying that these pathologies can’t or don’t happen. But in my personal experience with Quamina, they
didn’t. (Mind you, it’s a hobby project.)</p>
<p>And when they do happen, I would assume that mature open-source projects will use a network of
trust, as big operations like Linux already do. PRs that don’t have the imprimatur of someone known to be clueful will be ignored.
When I saw the first of those incoming Quamina PRs, I took the time for a serious look because I knew Rob and had seen evidence that he
was technically competent. If I see an incoming PR that’s nontrivial and from some rando and doesn’t pass a 120-second sanity
check, it’s unlikely to get any more attention.</p>
<p>In fact, some essentials don’t change. If you’re not requiring that PRs be clean and
test coverage be good and code reviews not be skipped and dependencies be curated, you’re going to get a lousy result whether
the upstream code is coming from a human or an LLM.</p>
<p>But it’d be naive to think that a big change in the
shape of that upstream isn’t going to affect the profession.</p>
<h2 id="p-9">Bottlenecks</h2>
<p>Speaking from personal experience, reviewing the PRs from Claude&Rob was neither faster nor slower, easier nor harder,
than what I’m used to pre-GenAI. The number of my disagreements with the diffs, and the amount of arguing it took to resolve
them, was also about as usual.
Which creates a big problem. Because if we can generate code a whole lot faster but review doesn’t
speed up, all we’ve done is moved the bottleneck in the system.</p>
<p>
Speaking of which, Armin Ronacher offers
<a href="https://lucumr.pocoo.org/2026/2/13/the-final-bottleneck/">The Final Bottleneck</a>
, from which: “When one part of the
pipeline becomes dramatically faster, you need to throttle input.” Think about that.
</p>
<h2 id="p-10">Burnout</h2>
<p>
Meanwhile, evidence is piling up that LLM-based software development is driving
developers to overwork and burnout. Here’s
<a href="https://hbr.org/2026/02/ai-doesnt-reduce-work-it-intensifies-it">a cool-eyed take</a>
from
<cite>Harvard Business
Review</cite>
. Then there’s Steve Yegge’s frantic, overly-long
<a href="https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163">The AI Vampire</a>
. But my favorite, and I think a
must-read, is Siddhant Khare’s
<a href="https://siddhantkhare.com/writing/ai-fatigue-is-real">AI fatigue is real and nobody talks about it</a>
.
From which: “AI reduces the cost of production but increases the cost of coordination, review, and decision-making. And those
costs fall entirely on the human.”
</p>
<p>
The argument we’re hearing is that GenAI makes development more efficient. And more efficient is better.
<a href="https://www.tbray.org/ongoing/When/202x/2020/07/05/Too-Efficient">Until it’s not</a>
.
</p>
<p>
I’m not sure the profession I joined last century would attract me today. And on Mastodon,
<a href="https://cosocial.ca/@gordwait/116082229876399512">@GordWait said</a>
“At our office, we are
noticing a huge drop in Comp Sci co-op applications. The next generation is convinced there’s no future in programming thanks to
AI hype.”
</p>
<h2 id="p-11">Can and should</h2>
<p>
Here’s another conundrum. Suppose we
<em>can</em>
build a whole lot more stuff, faster.
<em>Should</em>
we? I don’t know about you,
but I am regularly enraged at tools that work just fine popping up “wonderful new features” modals in front of what I’m
trying to get accomplished. Also at damaging UI churn, driven by product managers trying to get promoted. It’s
just not obvious
that speeding up software development is, in the big picture, a good thing.
</p>
<p>And I can’t help noting that every attempt to measure the productivity boost due to GenAI has shown zero (or worse)
improvement. Of course, Claude’s cheering section will point out that those studies date to 2024 which is the stone age. Maybe
they’re right.</p>
<h2 id="p-8">Vampires</h2>
<p>
(In which I once again go all
<a href="/ongoing/When/202x/2023/01/16/Class-Reductionism">class-reductionist</a>
.) The real problem here is late-stage
capitalism, and I think is best addressed in Yegge’s
<cite>AI Vampires</cite>
piece, from which I quote:
“…dollar-signs appear in their
<i>[employers’]</i>
eyeballs, like cartoon bosses. I know that look. There’s no reasoning with
the dollar-eyeball stare.” Yeah.
</p>
<p>
Thus the ancient question:
<i>cui bono?</i>
Assuming GenAI genuinely boosts productivity, who gets the
benefits? Because the ownership class sure doesn’t think they should go to their newly-more-efficient employees.
</p>
<h2 id="p-7">But, what do I know?</h2>
<p>
I know that you gotta have test coverage or your software is an unmaintainable tangle of festering tech debt. I know you gotta
have code review or your quality is on inexorable downhill drift. I
<em>don’t</em>
know how to build LLMs into a sane,
sustainable software engineering culture. Nor what to do
about capitalism’s AI Vampires.
</p>
<p>
And I absolutely do
<em>not</em>
believe the wild-eyed claims of 10× productivity gains, assuming we demand (as we should) that
they’re sustainable at scale.
</p>
<p>
So, would I advise executives to tell software engineering shops to discard their
culture in favor of vibe coding in the expectation of monstrous productivity wins? Nope.
<a href="https://simonwillison.net/2025/Oct/7/vibe-engineering/">Vibe engineering</a>
, maybe.
<a href="https://locusmag.com/feature/commentary-cory-doctorow-reverse-centaurs/">Centaurs, not reverse centaurs</a>
? Indeed.
</p>
<p>But would I say “Stay away, don’t even look”? Nope. I’d probably suggest pointing the LLM at well-delimited non-strategic
issues and
optimizations, and emphasize no shortcuts on reviewing or CI/CD standards.</p>
<p>
Also note that the GenAI apostles are at one in saying that this year’s tools are
<em>so</em>
much better than last year’s,
and next year’s are guaranteed to be qualitatively still better! So why would you rush in and risk getting locked into
soon-to-be-outmoded tooling?
</p>
<p>Rob Sayre wrote “I would never bother to type out these patches by hand. But I read them all.” I probably wouldn’t have
either and I read them too. And now Quamina is roughly twice as fast. Which is to say, I got good results on a hobby
project. That’s not nothing.</p>
<p>
But, also not conclusive.
Once the AI bubble pops and we’ve recovered from the systemic damage, I think there’ll
<em>probably</em>
be a place for
open-source LLM automation in developer toolkits.
</p>
<p>But maybe not. Wouldn’t surprise me much, either way.</p>
</div>
</content>
</entry>
<entry>
<title>Quamina + Claude, Case 2</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2</id>
<published>2026-02-14T12:00:00-08:00</published>
<updated>2026-02-14T12:00:00-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Quamina Diary"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Quamina Diary"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"><a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Last time out</a> I described a bunch of incremental-improvement <a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a> PRs from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s <a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>, a Claude-based port of Quamina from Go to Rust. The next post is about where I stand on GenAI and code</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
<a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Last time out</a>
I described a bunch of incremental-improvement
<a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a>
PRs
from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s
<a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>
, a Claude-based port of Quamina from Go to Rust.
The next post is about where I stand on GenAI and code.
</p>
<p>
Anybody who cares about this kind of thing will appreciate Rishi’s write-ups, starting with
<a href="https://rishi.baldawa.com/posts/the-agents-kept-going/">The Agents Kept Going</a>
(also see
<a href="https://rishi.baldawa.com/posts/scaffolding-for-agent-velocity/">Scaffolding for Agent Velocity</a>
).
He doesn’t just say what he did, he draws lessons; good ones, I think.
</p>
<h2 id="p-1">Background</h2>
<p>
Rishi and I worked together at AWS, can’t remember the details, but after I left he took over what we called Ruler, now known
as
<a href="https://github.com/aws/event-ruler">aws/event-ruler</a>
, Quamina’s ancestor. At the time I left it had been adopted
by quite a number of AWS and Amazon services and various instances were processing, in aggregate, a remarkable number of
millions of events per second. So he knows the territory.
</p>
<p>As for quamina-rs, go read his blogs. I’ve got little to add, but here are a couple of juicy quotes: “…at some point while I was
mindlessly kicking off these sessions, the agents started picking up open issues from the Go version and implementing them on
their own.“ Also, “And I think that’s the thing worth saying plainly. It’s human to care. Agents don’t care. Automation doesn’t
care. They need to be told what to care about, and even then they’ll misbehave the moment you look away…”</p>
<p>Both these stories ended with useful results.
So empirically, you can get useful results by applying GenAI to the process of code construction.</p>
<p>
Yay. I guess. But there are a lot of smart people who think this whole LLM-fueled coding direction is irremediably toxic.
<a href="/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion">I’m not sure they’re wrong</a>
.
</p>
</div>
</content>
</entry>
<entry>
<title>Quamina + Claude, Case 1</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1</id>
<published>2026-02-06T12:00:00-08:00</published>
<updated>2026-02-06T12:00:00-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Quamina Diary"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Quamina Diary"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any) GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current code playground, <a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a>. Here’s the first story. I’m going to go ahead and share it even though it will make people mad at me</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any)
GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and
try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current
code playground,
<a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a>
. Here’s the first story. I’m going to go
ahead and share it even though it will make people mad at me.
</p>
<h2 id="p-1">Why share?</h2>
<p>
Because our profession’s debate on this topic is simultaneously ridiculous and toxic. No meaningful dialogue seems possible
between the
<a href="https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04">Gas Town</a>
-and-
<a href="https://en.wikipedia.org/wiki/Moltbook">Moltbook</a>
faction and the
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">“AI” is a dick move</a>
camp.
So, I’m not going to join in today. This is pure anecdata: What happened when Rob applied Claude to Quamina. I’m going to
avoid rhetoric (in the linguistic sense, language designed to convince) and especially polemic (language designed to
attack). I promise to have conclusions before too long, just not today.
</p>
<h2 id="p-2">What happened was…</h2>
<p>
There’s this guy
<a href="https://github.com/sayrer">Rob Sayre</a>
, I’ve known him for many years, even been in the same room once or twice,
in the context of IETF work. I’ve never previously collaborated on code with him. Starting in
mid-January, he’s sent
<a href="https://github.com/timbray/quamina/issues?q=is%3Apr%20author%3Asayrer">a steady flow of PRs</a>
, most of which I
eventually accept and merge.
</p>
<p>The net result is that Quamina is now roughly twice as fast on several benchmarks designed to measure typical tasks.</p>
<h2 id="p-3">Technical details</h2>
<p>
The details of what Quamina is and does are in the
<a href="https://github.com/timbray/quamina?tab=readme-ov-file#quamina">README</a>
. For this discussion, let’s ignore everything
except to say that it’s a Go library and consider its two most important APIs.
<code>AddPattern()</code>
adds a Pattern (literal or
regexp) to an instance, and
<code>MatchesForEvent</code>
considers a JSON blob and reports back which Patterns it matched. It’s really fast and the
relationship is pleasingly weak between the number of Patterns that have been added and the matching speed.
</p>
<p>Quamina is based around finite automata (both deterministic and nondeterministic) and the rest of this technical-details
section will throw around NFA and DFA jargon, sorry about that.</p>
<p>
For code like this that is neither I/O-bound nor UI-centric, performance is really all about choosing the right
algorithms. Once you’ve done that, it’s mostly about memory management. Obviously in Quamina, the
<code>AddPattern</code>
call
needs to allocate memory to hold the finite automata. But I’d like it if the
<code>MatchesForEvent</code>
didn’t.
</p>
<p>Go’s only built-in data structures are “map” i.e. hash table, and “slice” i.e. appendable array. (For refugees from Java, with
its dozens of flavors of lists and hashes, this is initially shocking, but most Go fans come to the conclusion that Go is right
and Java is wrong.)
In really well-optimized
code, you’d like to see all the time spent either in your own logic or in appending to slices and updating maps.</p>
<p>
In less-well-optimized code, the profiler will show you spending horrifying amounts of time in runtime routines whose names
include “malloc”, and in the garbage collector.
Now, both maps and slices grow automatically as needed, which is nice, except when you’re trying to minimize allocation.
It turns out that slices have a
<b>capacity</b>
, and as long as the number of things you append is less than the capacity, you won’t
allocate, which is good. Thus, there are two standard tricks in the inventory of 100% of people who’ve optimized Go code:
</p>
<ol>
<li>
<p>When you make a new slice, give it enough capacity to hold everything you’re going to be adding to it. Yes, this can
be hard because you’re probably using it to store input data of unpredictable size, thus…</p>
</li>
<li>
<p>After you’ve made a new slice, keep it around, clear it after each input record, and its capacity will naturally grow
until it gets to be big enough that it fits all the rest of the records, then you’ll never allocate again.</p>
</li>
</ol>
<h2 id="p-4">Those PRs</h2>
<p>Background: Quamina is equipped with what I think is a pretty good unit-test suite, and multiple benchmarks.</p>
<p>I started getting Rob’s PRs and initially, 100% of them were finding ways along both of those well-trodden map-and-slice
paths, in places where I hadn’t noticed the opportunity. They were decent PRs, well-commented, sensible code, no loss of test
coverage. After I asked to see benchmark runs to prove the gains weren’t just theoretical, they started including benchmark runs. I’ve
found a few things to push back on but Rob and I had no problem sorting those out.</p>
<p>At the end of the day I had no qualms about merging them, but I did find myself wondering how they were built. So I
asked.</p>
<h2 id="p-6">Workflow</h2>
<p>Rob had told me right away on the first one that these were substantially Claude-generated. I asked him for his workflow and part
of what he said was “I might say
‘let's do some profiles of memory and CPU on this benchmark, on main and on this branch.’ It will come up with good and bad
ideas, then I pick them.”</p>
<p>Also: “What might be counter-intuitive is that I can context switch really quickly with it. So, you leave a comment, and I
just tell Claude to fix that, because you are correct. Sometimes I go in and hand edit, but usually it gets close or perfect
(what they call a "one-shot"). But I just have the conversation open, so I just pick up where we left off.”</p>
<p>Here’s a sample of Claude talking to Rob. You may have to enlarge it.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/06/claude-says.png" alt="Dialogue with Claude"/>
<h2 id="p-7">Not just the same-old</h2>
<p>Then I got a surprise, because Claude and Rob spotted two pretty big improvements that aren’t on the standard list.
First: To traverse an NFA, for each state you have to compute its “epsilon closure”, the set of other states you can get to
transitively following epsilon transitions. I had already built a cache so that as you computed them, they got remembered.
C&R pointed out “Epsilon closures are a property of the automaton structure, not the input data. Once a pattern is added and the
NFA is built, the epsilon closure for any given state is fixed and never changes.” So you might as well compute it and save it
when you build the NFA.</p>
<p>This is even better than it sounds, because (for good reasons following from Quamina’s concurrency model) my closure
caches were per-thread, while the new epsilon closures were global, stored just once for all the threads. Not bad, and not trivial.</p>
<p>
Second, when you’re computing those closures, you have to memo-ize the key functions to avoid getting caught in NFA loops.
I’d done this with a set, which in Go you implement as
<code>map[whatever]bool</code>
. R&C figured out that if you gave each
state a “closure generation” integer field and maintained a global closure-generation value, you could dodge the necessity for the
set at the cost of one integer per state. The benchmarks proved it worked.
</p>
<p>
As I wrote this piece,
<a href="https://github.com/timbray/quamina/pull/491">another PR arrived</a>
with a stimulating title: “kaizen: allocation-free
on the matching path”.
</p>
<h2 id="p-5">Kaizen?</h2>
<p>
It’s
<a href="https://en.wikipedia.org/wiki/Kaizen">the idea that</a>
you make things substantially better by successively introducing
small improvements. We try to
use the term to tag Quamina PRs that change no semantics but just make performance better or more reliable or whatever.
</p>
<h2 id="p-8">But GenAI is bad!?!</h2>
<p>
Yes, so they say. Go re-read that
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">dick-move</a>
polemic.
</p>
<p>
But, I’m going to leave this little case study conclusion-free for a bit because there are two follow-up pieces.
Next,
<a href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2">the story of quamina-rs</a>
, a Claude-drive port of Quamina to Rust.
Finally,
<a href="/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion">Open Source and GenAI?</a>
.
</p>
<!--
<p>You say “But GenAI is environmentally devastating and has the goal of throwing millions of knowledge workers onto the street
and is being sold by the worst people and used for horrible applications and will increase society’s already-intolerable level
of inequality!” And I
reply “Yes, yes, yes, yes, and yes.” But I’m talking about the software sector here.
<a href="https://www.jetbrains.com/lp/devecosystem-data-playground/#global_population">JetBrains thinks</a> that the world has
21 million or so software developers. The notion that this is a market that could justify the lunatic wave of investment thrown
at GenAI is laughable. Training and operating the models required to support things like Claude will be rounding error in the
scale of the Great GenAI Overbuild. The world can afford it.</p>
<h2 id='p-9'>A prediction</h2>
<p>Let me quote Yegge:</p>
<blockquote><p>For this blog post, “Claude Code” means “Claude Code and all its identical-looking competitors”, i.e. Codex,
Gemini CLI, Amp, Amazon Q-developer ClI, blah blah, because that’s what they are. Clones.</p></blockquote>
<p>GenAI, overbuilding wherever you look. But anyhow, none of these products have moats and the chance that any of them become
dominant enough to serve as the basis for an extractive monopoly rounds to zero. Nobody’s ever built a huge cash-cow company
bsaed on selling tools to developers. One reason is (*gasp*) Open Source. Does anybody doubt that in the near future, there will
be entirely open-source versions of what Yegge means by “Claude”?</p>
-->
</div>
</content>
</entry>
<entry>
<title>Long Links</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links"/>
<link rel="replies" thr:count="0" type="application/xhtml+xml" href="/ongoing/When/202x/2026/02/03/Long-Links#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links</id>
<published>2026-02-03T12:00:00-08:00</published>
<updated>2026-02-04T14:41:25-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="The World"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="The World"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Welcome to the first <cite>Long Links</cite> of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to take in all of these, but there’s a good chance one or two might brighten your day</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Welcome to the first
<cite>Long Links</cite>
of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to
take in all of these, but there’s a good chance one or two might brighten your day.
</p>
<h2 id="p-17">Unclassified</h2>
<p>
Thomas Piketty is always right. For example,
<a href="https://thomaspiketty.wordpress.com/2026/02/03/europe-a-social-democratic-power/">Europe, a social-democratic
power</a>
.
</p>
<p>
Lying is wrong. Conservatives
<a href="https://thetyee.ca/Opinion/2026/02/02/Today-Conservatives-Misinformation-Norm/">do it all the time</a>
. To be fair,
that piece is about the capital-C flavor, as in the Canadian Tories. But still.
</p>
<p>
Clothing is open-source: “If you slice the different parts off with a seamripper, lay them all down, trace them on new
fabric, cut them out, and stitch them back together, you can effectively clone and fork
garments.” From
<a href="https://wiki.xxiivv.com/site/devine_lu_linvega.html">Devine Lu Linvega</a>
.
</p>
<p>
The Universe is weird. The Webb telescope keeps showing astronomers things that shouldn’t be there. For example,
<a href="https://www.nature.com/articles/s41586-025-09973-1">An X-ray-emitting protocluster at z ≈ 5.7 reveals rapid structure
growth</a>
; ignore the title and read the Abstract and Main sections. With pretty pictures!
</p>
<h2 id="p-2">Music</h2>
<p>
One time in Vegas, I was giving a speech, something about cloud computing, and was surprised to find the venue an ornate
velvet-lined theater. I found out from the staff, and then relayed to the audience, that the last human before me to stand on this stage
in front of an audience had been Willie Nelson. I was tempted to fall to my knees and kiss the boards.
<a href="https://www.newyorker.com/magazine/2025/12/29/willie-nelson-profile">How Willie Nelson Sees America</a>
, from
<cite>The
New Yorker</cite>
, is subtitled “On the road with the musician, his band, and his family” but it ends up being the kernel of a
good biography of an interesting person. Bonus link; on YouTube,
<a href="https://www.youtube.com/watch?v=3WIR3Riq4wM">Willie Nelson - Teatro, featuring Daniel Lanois & Emmylou Harris,
Directed by Wim Wenders</a>
. Strong stuff.
</p>
<p>
Speaking of recorded music, check out
<a href="https://www.dazeddigital.com/music/article/69407/1/why-listening-parties-are-everywhere-right-now-rosalia-album-launch-artist">Why
listening parties are everywhere right now</a>
. Huh? They are? As a deranged audiophile, sounds like my kind of thing. I’d go.
</p>
<h2 id="p-4">Somewhere to put worker bees</h2>
<p>When I was working at AWS in downtown Vancouver back starting in 2015, a lot of our junior engineers lived in these
teeny-tiny little one-room-tbh apartments. It worked out pretty well for them, they were affordable and an easy walk from the
office and these people hadn’t built up enough of a life to need much more room.
For a while this trend of
so-called-“studio” flats was the new hotness in Vancouver and I guess around quite a bit of the developed world.
Us older types with families would look at the
condo market and tell each other “this is stupid”.</p>
<p>We were right. The
bottom is falling out and they’re sitting empty in their thousands. And not just the teeniest either, the whole
condo business is in the toilet. It didn’t help that for a few years all the prices went up every year (until they didn’t) and
you could make serious money flipping unbuilt condos, so lots of people did (until they didn’t).</p>
<p>
Anyhow, here’s a nice write-up on the subject:
<a href="https://www.bbc.com/news/articles/cqxq32zzq8eo">‘Somewhere to put worker bees’: Why Canada's micro-condos are losing
their appeal</a>
. (From the BBC, huh?)
</p>
<h2 id="p-5">AI AI AI</h2>
<p>
Sorry, I can’t not relay pro- and anti-GenAI posts, because that conversation is affecting all our lives just now. I am
actually getting ready to decloak my own conclusions, but for the moment I’m just sharing essays on the subject that strike me as
well-written and enjoyable for their own sake. Thus
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">‘AI' is a dick move, redux</a>
from Baldur
Bjarnason. Boy, is he mad.
</p>
<p>
Sam Ruby has been doing some
<a href="https://intertwingly.net/blog/2026/01/28/Twilight-Zone.html">extremely weird shit</a>
, running Rails in the browser, as
in without even a network connection or a Ruby runtime. Yes, AI was involved in the construction.
</p>
<h2 id="p-6">Software</h2>
<p>
There’s this programming language called Ivy that is in the APL lineage; that acronym will leave young’uns blank but a few greying
eyebrows will have been raised. Anyhow,
<a href="https://commandcenter.blogspot.com/2026/01/implementing-transcendental-functions.html?m=1">Implementing the
transcendental functions in Ivy</a>
is delightfully geeky, diving deep with no awkwardness. By no less than Rob Pike.
</p>
<p>
Check out Mike Swanson’s
<a href="https://blog.mikeswanson.com/backseat-software/">Backseat Software</a>
. That’s “backseat” as in “backseat driver”,
which today’s commercial software has now, annoyingly, become. This piece doesn’t make any points that I haven’t heard (or made
myself) elsewhere, but it pulls a lot of the important ones together in a well-written and compelling package. Recommended.
</p>
<p>
Old Googler Harry Glaser
<a href="https://www.linkedin.com/posts/harryglaser_i-worked-on-ads-at-google-15-years-ago-when-activity-7423057144402427905-nm3p/">reacts
with horror</a>
to the introduction of advertising by OpenAI, and makes gloomy predictions about how it will evolve. His predictions
are obviously correct.
</p>
<p>
The title says it:
<a href="https://petapixel.com/2026/01/17/discovering-a-digital-photo-editing-workflow-beyond-adobe/">Discovering a Digital
Photo Editing Workflow Beyond Adobe</a>
. It’d be a tough transition for me, but the relationship with Adobe gets harder and
harder to justify.
</p>
<h2 id="p-7">Indigenous reconciliation</h2>
<p>Khelsilem is one of the loudest and clearest voices coming out of the Squamish nation, one of the larger and better-organized
Indigenous communities around here.</p>
<p>There has been a steady drumbeat of Indigenous litigation going on for decades as a
consequence of the fact that the British colonialists who seized the territory in what we now call British Columbia didn’t
bother to sign treaties with the people who were already there, they just assumed ownership. The Indigenous people have been
winning a lot of court cases, which makes people nervous.</p>
<p>
Anyhow, Khelsilem’s
<a href="https://khelsilem.substack.com/p/the-source-of-the-reconciliation">The Real Source of Canada's Reconciliation Panic</a>
covers the ground. I’m pretty sure British Columbians should read this, and suspect that anyone in a jurisdiction undergoing similar
processes should too.
</p>
<h2 id="p-8">Resonant computing, Black and Blue sky</h2>
<p>
There’s this thing called the
<a href="https://resonantcomputing.org">Resonant Computing Manifesto</a>
, whose authors and signatories include names you’d
probably recognize. Not mine; the first of its Five Principles begins with “In the era of AI…” Also, it is entirely oblivious to
the force driving the enshittification of social-media platforms: Monopoly ownership and the pathologies of late-stage
capitalism.
</p>
<p>
Having said that, the vision it paints is attractive. And having said
<em>that</em>
, it’s now featured on the flags waved by
the proponents of ATProto, which is to say Bluesky. See Mike Masnick’s
<a href="https://www.techdirt.com/2026/01/27/atproto-the-enshittification-killswitch-that-enables-resonant-computing/">ATproto:
The Enshittification Killswitch That Enables Resonant Computing</a>
(Mike is on Bluesky Corp’s Board). That piece is OK but, in
the comments, Masnick quickly gets snotty about the Fediverse and Mastodon, in a way that I find really off-putting. And once
again, says nothing about the underlying economic realities that poison today’s platforms.
</p>
<p>I want to like Bluesky, but I’m just too paranoid and cynical about money. It is entirely unclear who is funding the people
and infrastructure behind Bluesky, which matters, because if Bluesky Corp goes belly-up, so does the allegedly-decentralized service.</p>
<p>
On the other hand,
<a href="https://blackskyweb.xyz">Blacksky</a>
is interesting. They are trying to prove that ATProto really can be made
decentralized in fact not just in theory.
<a href="https://blackskyweb.xyz/overview/">Their ideas and their people</a>
are stimulating, and their
<a href="https://opencollective.com/blacksky">finances are transparent</a>
. I’ll be
<a href="https://docs.blacksky.community/migrating-to-blacksky-pds-complete-guide">moving my ATProto presence to Blacksky</a>
when I get some cycles and the process has become a little more automated.
</p>
<h2 id="p-14">Good crypto</h2>
<p>The cryptography community is working hard on the problem of what happens should quantum computers ever become real products as
opposed to over-invested fever dreams. Because if they ever work, they can probably crack the algorithms that we’ve been using
to provide basic Web privacy.</p>
<p>
The problem is technically
hard
<span class="dashes"> —</span>
there are good solutions though
<span class="dashes"> —</span>
and also politically fraught,
because maybe the designers or standards orgs are corrupt or incompetent. It’s reasonable to worry about this stuff and people
do. They probably don’t need to: Sophie Schmieg dives deep in
<a href="https://keymaterial.net/2025/11/27/ml-kem-mythbusting/">ML-KEM Mythbusting</a>
.
</p>
<h2 id="p-16">Books</h2>
<p>
Here’s one of the most heartwarming things I’ve read in months:
<a href="https://blog.openlibrary.org/2026/01/30/a-community-curated-nancy-drew-collection/">A Community-Curated Nancy Drew
Collection</a>
. Reminder: The Internet can still be great.
</p>
<p>
John Lanchester’s
<a href="https://www.lrb.co.uk/the-paper/v46/n17/john-lanchester/for-every-winner-a-loser">For Every Winner a Loser</a>
,
ostensibly a review of two books about famous financiers, is in fact an extended howl of
(extremely instructive) rage against the
financialization of everything and the unrelenting increase in inequality. What we need to do is to take the ill-gotten gains
away from these people and put it to a use
<span class="dashes"> —</span>
any use
<span class="dashes"> —</span>
that improves
human lives.
</p>
<p>
I talk a lot about late-stage capitalism. But Sven Beckert published a
<a href="https://www.nytimes.com/2025/11/26/books/review/capitalism-sven-beckert.html?searchResultPosition=1">1,300-page monster entitled <cite>Capitalism</cite></a>
;
the link is to a
<cite>NYT</cite>
review and makes me want to read it..
</p>
<p>
Charlie Stross, the sci-fi author, likes webtoons and
<a href="https://www.antipope.org/charlie/blog-static/2025/12/webtoons-revisited.html">recommends a bunch</a>
. Be careful, do
not follow those links if you’re already short of time. Semi- or fully-retired? Go ahead!
</p>
<p>
I have history with dictionaries. For several years of my life in the late Eighties, I was the research project manager for
the
<a href="https://cs.uwaterloo.ca/~fwtompa/newoed-project.html">New Oxford English Dictionary</a>
project at the University of
Waterloo. Dictionaries are a fascinating topic and, for much of the history of the publishing industry, were big money-makers;
they dominate any short list of the biggest-selling books in history. Then came the Internet.
</p>
<p>
Anyhow, Louis Menand’s
<a href="https://www.newyorker.com/magazine/2025/12/29/unabridged-the-thrill-of-and-threat-to-the-modern-dictionary-stefan-fatsis-book-review">Is
the Dictionary Done For?</a>
starts with a review of a book by Stefan Fatsis entitled
<cite>Unabridged: The Thrill of (and
Threat to) the Modern Dictionary</cite>
which I haven’t read and probably won’t, but oh boy, Menand’s piece is big and rich and
polished and just a fantastic read. If, that is, you care about words and languages. I understand there are those who don’t, which is
weird. I’ll close with a quote from Menand:
</p>
<blockquote>
<p>“The dictionary projects permanence,” Fatsis concludes, “but the language is Jell-O, slippery and mutable and
forever collapsing on itself.” He’s right, of course. Language is our fishbowl. We created it and now we’re forever trapped
inside it.</p>
</blockquote>
</div>
</content>
</entry>
<entry>
<title>Quamina v2.0.0</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2026/01/20/Quamina-2.0#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0</id>
<published>2026-01-20T12:00:00-08:00</published>
<updated>2026-01-21T15:27:06-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Quamina Diary"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Quamina Diary"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">There’ve been a few bugfixes and optimizations since 1.5, but the headline is: <a href="https://github.com/timbray/quamina?tab=readme-ov-file#quamina">Quamina</a> now knows regular expressions. This is roughly the fourth anniversary of the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and other tech enthusiasms.) Open-source software, it’s a damn fine hobby</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
There’ve been a few bugfixes and optimizations since 1.5, but the headline is:
<a href="https://github.com/timbray/quamina?tab=readme-ov-file#quamina">Quamina</a>
now knows regular expressions. This is roughly the fourth anniversary of
the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and
other tech enthusiasms.)
Open-source software, it’s a damn fine
hobby.
</p>
<p>
Did I mention optimizations? There are
<i>(sob)</i>
also regressions; introducing REs had
measurable negative impacts on other parts of the system.
But it’s a good trade-off. When you ship software that’s designed for pattern-matching, it should
really do REs. The RE story, about a year long, can be read starting
<a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series">here</a>
.
</p>
<h2 id="p-4">Quamina facts</h2>
<ol>
<li>
<p>About 18K lines of code (excluding generated code), 12K of which are unit tests. The RE feature makes the tests run
slower, which is annoying.</p>
</li>
<li>
<p>Adding Quamina to your app will bulk your executable size up by about 100K, largely due
to Unicode tables.</p>
</li>
<li>
<p>There are a few shreds of AI-assisted code, none of much importance.</p>
</li>
<li>
<p>A Quamina instance can match incoming data records on my 2023 M2 Mac at millions per
second without much dependence on how many patterns are being matched at once. This assumes
not too many horrible regular expressions. That’s per-thread of course, and Quamina does
multithreading nicely.</p>
</li>
</ol>
<h2 id="p-1">Next?</h2>
<p>
The
<a href="https://github.com/timbray/quamina/issues">open issues</a>
are modest in number but
some of them will be hard.
</p>
<p>
I think I’m going to ignore that list for a while (PRs welcome, of course) and work on
optimization. The introduction
of epsilon transitions was required for regular expressions, but they really bog the matching
process down. At Quamina’s core is the
<a href="/ongoing/When/202x/2024/07/28/Union-of-Finite-Automata">finite-automaton merge</a>
logic,
which contains fairly elegant code but generally throws up its hands when confronted with
epsilons and does the simplest thing that could possibly work. Sometimes at an annoyingly slow pace.
</p>
<p>
Having said that, to optimize you need a good benchmark that pressures the
software-under-test.
Which is tricky, because Quamina is so fast that it’s hard to
to feed it enough data to stress it without the feed-the-data code dominating
the runtime and memory use. If anybody has a bright idea for how to pull together a good
benchmark I’d love to hear it. I’m looking at
<a href="https://go.dev/blog/testing-b-loop">b.Loop()</a>
in Go 1.24, any reason not to go there?
</p>
<h2 id="p-3">Book?</h2>
<p>It occurs to me that as I’ve wrestled with the hard parts of Quamina, I’ve done the obvious
thing and trawled the Web for narratives and advice. And, more or less, been disappointed. Yes,
there are many lectures and blogs and so on about this or that aspect of finite automata, but
they tend to be mathemagical and theoretical and say little about how, practically speaking,
you’d write code to do what they’re talking about.</p>
<p>
The Quamina-diary
<span class="o">ongoing</span>
posts now contain several tens of thousands
of words. Also I’ve previously written
<a href="/ongoing/When/200x/2006/04/18/XML-Grammar">quite a bit</a>
about Lark, the world’s
first XML parser, which I wrote and was automaton-based. So I think there’s a case for a slim
volume entitled something like
<cite>Finite-state Automata in the Code Trenches</cite>
. It’d be
a big money-maker, I betcha. I mean, when Apple TV brings it to the screen.
</p>
<h2 id="p-2">Why?</h2>
<p>
Let’s be honest. While
<a href="https://github.com/timbray/quamina">the repo</a>
has quite a few stars, I truly have no idea who’s
using Quamina in production. So I can’t honestly claim that this work is making the
world better along any measurable dimension.
</p>
<p>I don’t much care because I just can’t help it. I love executable abstractions for their own sake.</p>
</div>
</content>
</entry>
<entry>
<title>Losing 1½ Million Lines of Go</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2026/01/14/Unicode-Properties#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties</id>
<published>2026-01-14T12:00:00-08:00</published>
<updated>2026-01-14T15:52:47-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Quamina Diary"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Quamina Diary"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support character-property regexp features in <a href="https://github.com/timbray/quamina">Quamina</a>. Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this is about (among other things) <em>avoiding</em> those 1½M lines. And really only of interest to people whose pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I think I should maybe have used</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support
character-property regexp features in
<a href="https://github.com/timbray/quamina">Quamina</a>
.
Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this
is about (among other things)
<em>avoiding</em>
those 1½M lines. And really only of interest to people whose
pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I
think I should maybe have used.
</p>
<h2 id="p-1">Character property matching</h2>
<p>
I’m talking about regexp incantations like
<code>[\p{L}\p{Zs}\p{Nd}]</code>
, which matches anything that Unicode classifies
as a letter, a space, or a decimal number. (Of course, in Quamina “
<code>\</code>
” is “
<code>~</code>
”
<a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series#p-7">for excellent reasons</a>
, so that reads
<code>[~p{L}~p{Zs}~p{Nd}]</code>
.)
</p>
<p>
(I’m writing about this now because I just launched
<a href="https://github.com/timbray/quamina/pull/465">a PR</a>
to enable this feature. Just one more to go before I can
release a new version of Quamina with full regexp support, yay.)
</p>
<h2 id="p-3">Finding the properties</h2>
<p>
To build an automaton that matches something like that, you have to find out what the character properties are.
This information comes from the
<a href="https://www.unicode.org/ucd/">Unicode Character Database</a>
, helpfully provided online by the Unicode consortium.
Of course, most programming languages have libraries that will help you out, and
<a href="https://pkg.go.dev/unicode#pkg-variables">that includes Go</a>
, but I didn’t use it.
</p>
<p>
Unfortunately, Go’s library doesn’t get updated every time Unicode does. As of now, January 2026,
it’s still stuck at Unicode 15.0.0, which
<a href="https://www.unicode.org/history/publicationdates.html">dates to September 2023</a>
; the latest version is 17.0.0, last
September. Which means there are plenty of Unicode characters Go doesn’t know about, and I didn’t want Quamina to settle
for that.
</p>
<p>
So, I fetched and parsed the famous master file from
<a href="https://www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt">www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt</a>
.
Not exactly rocket science, it’s a flat file with
<code>;</code>
-delimited fields, of which I only cared about the first
and third. There are some funky bits, such as the pair of nonstandard lines indicating that the Han characters occur
between U+4E00 and U+9FFF inclusive; but still not really taxing.
</p>
<p>
The output is, for each Unicode category, and also for each category’s complement (
<code>~P{L}</code>
matches everything
that’s
<em>not</em>
a letter; note the capital
<code>P</code>
), a list of pairs of code points, each pair indicating a subset
of the code space where that category applies. For example, here’s the first line of character pairs with category
<code>C</code>
.
</p>
<pre>
<code> {0x0020, 0x007e}, {0x00a0, 0x00ac}, {0x00ae, 0x0377},</code>
</pre>
<p>How many pairs of characters, you might wonder? There are 37 categories
and it’s all over the place but adds up to a lot. The top three categories
are L with 1,945 pairs, Ll at 664, and M at 563. At the other end are Zl and Zp, both with just 1.
The total number of pairs is 14,811, and the generated Go code is a mere 5,122 lines.</p>
<h2 id="p-5">Character-property automata</h2>
<p>
Turning these creations into finite automata was straightforward: I already had the code to handle regexps like
<code>[a-zA-Z0-9]</code>
, logically speaking the same problem. But, um, it wasn’t fast. My favorite unit test, an exercise in
<a href="/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1">sample-driven development</a>
with 992 regexps,
suddenly started taking multiple seconds, and my whole unit-test suite expanded from around ten seconds to over twelve; since I
tend to run the unit tests every time I take a sip of coffee or scratch my head or whatever, this was painful. And it occurred to
me that it would be painful in practice to people who want for some good reason or another to load up a bunch of
Unicode-property patterns into a Quamina instance.
</p>
<p>So, I said to myself, I’ll just precompute all the automata and serialize them into code. And now we
get to the title of this essay; my data structure is a bit messy and ad-hoc and just for the categories, before I got to the
complement versions, I was generating 775K lines of code.</p>
<p>
Which worked! But, it was 12M in size and while Go’s runtime is fast, there was a painful pause while it absorbed those data
structures on startup. Also, opening the generated file regularly caused my IDE
(
<a href="https://www.jetbrains.com/go/">Goland</a>
) to crash. And I was only halfway there. The whole approach was painful to
work with so I went looking for Plan B.
</p>
<p>The code that generates the automaton from the code point pairs is pretty well the simplest thing that could possibly work
and it was easy to understand but burned memory like crazy. So I worked for a bit on making it faster and
cheaper, but so far have found no low-hanging fruit.</p>
<p>I haven’t given up on that yet. But in the meantime, I remembered
Computer Science’s general solution for all performance problems, by which I mean caching. So now, any Quamina instance will
compute the automaton for a Unicode property the first time it’s used, then remember it. So now Quamina’s speed at adding
Unicode-property regexps to an instance has increased from 135/second to 4,330, a factor of thirty and Good Enough For
Rock-n-Roll.</p>
<p>
It’s worth pointing out that while
<em>building</em>
these automata is a heavyweight process, Quamina can use them to match
input messages at its typical rates, hundreds of thousands to millions per second. Sure, these automata are “wide”, with lots of
branches, but they’re also shallow, since they run on UTF-8 encoded characters whose maximum length is four and average length
is much less. Most times you only have to take one or two of those many branches to match or fail.
</p>
<h2 id="p-2">Should I have used Claude?</h2>
<p>
This particular segment of the Quamina project included some
<em>extremely</em>
routine programming tasks, for example
fetching and parsing
UnicodeData.txt, computing the sets of pairs, generating Go code to serialize the automata, reorganizing source files that had
become bloated and misshapen, and writing unit tests to confirm the results were correct.
</p>
<p>
Based on my own
<a href="/ongoing/When/202x/2025/07/01/First-AI-Code">very limited experience</a>
with GenAI code, and in particular after
reading Marc Brooker’s
<a href="https://brooker.co.za/blog/2025/12/16/natural-language.html">On the success of ‘natural language programming’</a>
and
Salvatore (“antirez”) Sanfilippo’s
<a href="https://antirez.com/news/158">Don't fall into the anti-AI hype</a>
, I guess I’ve joined the camp that thinks
this stuff is going to have a place in most developers’ toolboxes.
</p>
<p>I think Claude could have done all that boring stuff, including acceptable unit tests, way faster than I did.
And furthermore got it right the first time, which I didn’t.</p>
<p>So why didn’t I use Claude? Because I don’t have the tooling set up and I was impatient and didn’t want to invest the time in
getting all that stuff going and improving my prompting skills. Which reminds me of all the times I’ve been trying to evangelize other
developers on a better way to do things and was greeted by something along the lines of “Fine, but I’m too busy right now, I’ll
just going on doing things the way I already know how to.”</p>
<p>
Does this mean I’m joining the “GenAI is the future and our investments will pay off!” mob? Not in the slightest. I still
think it’s overpriced, overhyped, and mostly ill-suited to the business applications that “thought leaders” claim for it.
That word “mostly” excludes the domain of code; as I said
<a href="/ongoing/When/202x/2025/09/26/GenAI-Predictions#p-5">here</a>
, “It’s pretty obvious that LLMs are better at predicting code
sequences than human language.”
</p>
<p>And, as it turns out, the domain of Developer Tools has never been a Big Business by the standards of GenAI’s promoters. Nor
will it ever be; there just aren’t enough of us. Also, I suspect it’ll be reasonably easy in the near future for open-source
models and agents to duplicate the capabilities of Claude and its ilk.</p>
<p>Speaking personally, I can’t wait for the bubble to pop.</p>
<h2 id="p-4">Quamina.next?</h2>
<p>
After I ship the numeric-quantifier feature, e.g.
<code>a{2-5}</code>
, Quamina’s regexp support will be complete and if no
horrid bugs pop up I’ll pretty quickly release Quamina 2.0. Regexps in pattern-matching software are a qualitative difference-maker.
After that I dunno, there are lots more interesting features to add.
</p>
<p>Unfortunately, a couple years into my Quamina work, I got distracted by life and by other projects, and ignored it. One
result is that so did the other people who’d made major contributions and provided PR reviews. I miss them and it’s less fun
now. We’ll see.</p>
</div>
</content>
</entry>
<entry>
<title>Regexp Lessons</title>
<link href="https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2026/01/01/Quamina-2026#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026</id>
<published>2026-01-01T12:00:00-08:00</published>
<updated>2026-01-06T10:19:29-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/Quamina Diary"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Quamina Diary"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">I’m just landing a <a href="https://github.com/timbray/quamina/pull/461">chonky PR</a> in <a href="https://github.com/timbray/quamina">Quamina</a> whose effect is to enable the <code>+</code> and <code>*</code> regexp features. As in my <a href="/ongoing/When/202x/2025/07/21/Automaton-merge-war">last chapter</a>, this is a disorderly war story not an essay, and probably not of general interest. But as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are <em>dozens</em> of us)</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
I’m just landing a
<a href="https://github.com/timbray/quamina/pull/461">chonky PR</a>
in
<a href="https://github.com/timbray/quamina">Quamina</a>
whose effect is to enable the
<code>+</code>
and
<code>*</code>
regexp
features. As in my
<a href="/ongoing/When/202x/2025/07/21/Automaton-merge-war">last chapter</a>
, this is a disorderly war story not an essay, and
probably not of general interest. But
as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are
<em>dozens</em>
of us).
</p>
<h2 id="p-5">2014-2026</h2>
<p>
As I write this, I’m sitting in the same couch in my Mom’s living room in Saskatchewan where, on my first Christmas after
joining AWS, I got the first-ever iteration of this software to work. That embryo’s mature form is available to the world as
<a href="https://github.com/aws/event-ruler">aws/event-ruler</a>
. (Thanks, AWS!) Quamina is its direct descendent, which means
this story is entering its twelfth year.
</p>
<p>Mom is now 95 and good company despite her failing memory. I’ve also arrived at a qualitatively later stage of life than in
2014, but would like to report back from this poorly-lit and often painful landscape: Executable abstractions are still fun,
even when you’re old.</p>
<p>Anyhow, the reason I’m writing all this stuff isn’t to expound on the nature of finite automata or regular expressions, it’s
to pass on lessons from implementing them.</p>
<h2 id="p-8">Lesson: Seek out samples</h2>
<p>
In a previous episode I used the phrase
<a href="/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1">Sample-driven development</a>
to describe my luck in
digging up 992 regexp test cases, which reduced task task from intimidating to approachable.
I’ve never previously had the luxury of wading into a big software task armed with loads of test cases written by other
people, and I can’t recommend it enough. Obviously you’re not always going to dig this sort of stuff up, but give it a sincere
effort.
</p>
<h2 id="p-9">Lesson: Break up deliverables</h2>
<p>I decomposed regular expressions into ten unique features, created an enumerated type to identify them, and implemented them
by ones and twos.
Several of the feature releases used
techniques that turned out to be inefficient or just wrong when it came to subsequent features. But they worked,
they were useful, and my errors nearly all taught me useful lessons.</p>
<p>Having said that, here’s some cool output that combines this lesson and the one above, from the unit test that runs
those test cases. Each case has a regexp then one
or more samples each of strings that should and shouldn’t match. I instrumented the test to report the usage of regexp features
in the match and non-match cases.</p>
<pre>Feature match test counts:
32 '*' zero-or-more matcher
27 () parenthetized group
48 []-enclosed character-class matcher
7 '.' single-character matcher
29 |-separated logical alternatives
16 '?' optional matcher
29 '+' one-or-more matcher
Feature non-match test counts:
45 '+' one-or-more matcher
24 '*' zero-or-more matcher
31 () parenthetized group
49 []-enclosed character-class matcher
6 '.' single-character matcher
32 |-separated logical alternatives
21 '?' optional matcher</pre>
<p>Of course, since most of the tests combine multiple features, the numbers for all the features
get bigger each time I implement a new one. Very confidence-building.</p>
<h2 id="p-2">Lesson: Thompson’s construction</h2>
<p>
This is the classic nineteen-sixties regular-expression implementation by Ken Thompson, described in Wikipedia
<a href="https://en.wikipedia.org/wiki/Thompson%27s_construction">here</a>
and (for me at least) more usefully, in a
storytelling style by Russ Cox,
<a href="https://swtch.com/%7Ersc/regexp/regexp1.html">here</a>
.
</p>
<p>On several occasions I rushed ahead and implemented a feature without checking those sources, because how hard could it be?
In nearly every case, I had problems with that first cut and then after I went and consulted the oracle, I could see where I’d
gone wrong and how to fix it.</p>
<p>So big thanks, Ken and Russ.</p>
<h2 id="p-3">Lesson: List crushing</h2>
<p>
In some particularly nasty regular expressions that
combine
<code>[]</code>
and
<code>?</code>
and
<code>+</code>
and
<code>*</code>
, you can
get multiple states connected in complicated ways with epsilon links.
</p>
<p>
In Thompson’s Construction, traversing an NFA transitions not just from one state to another but from a current set of states
to a next set, repeat until you match or fail. You also compute epsilon closures as you go along; I’m skipping over details
here. The problem was that traversing these pathologically complex regexps with a sufficiently long string was leading to an
exponential explosion in the current-states and next-states sizes
<span class="dashes"> —</span>
not a figure of speech, I mean
<code>O(2<sup>N</sup>)</code>
. And despite the usage of the word “set” above, these weren’t, they contained endless
duplicates.
</p>
<p>
The
<em>best</em>
solution would be to study the traversal algorithm and improve it so it didn’t emit fountains of dupes. That
would be hard. The next-best would to turn these things into actual de-duped sets, but that would require a hash table right in
the middle of the traversal hot spot, and be expensive.
</p>
<p>So what I did was to detect whenever the next-steps list got to be longer than N, sorted it, and crushed out all the dupes.
As I write, N is now 500 based on running benchmarks and finding a value that makes number go down.</p>
<p>
The reason this is good engineering is that the condition where you have to crush the list almost never happens, so in the
vast majority of cases the the only cost is an
<code>if len(nextSteps)>N</code>
comparison. Some may find this approach
impure, and they have a point. I would at some point like to go back and find a better upstream approach. But for now it’s still
really fast in practice, so I sleep soundly.
</p>
<h2 id="p-4">Lesson: Hell’s benchmark</h2>
<p>
I’ve
<a href="/ongoing/When/202x/2025/07/21/Automaton-merge-war#p-1">written before</a>
about my struggles with the benchmark where I
merge 12,959 wildcard patterns together. Back before I was doing epsilon processing correctly, I had a kludgey implementation
that could match patterns in the merged FA at typical Quamina speeds, hundreds of thousands per second. With correct epsilon
general-purpose epsilon handling, I have so far not been smart enough to find a way to preserve that performance. With the full
13K patterns, Quamina matches at less than 2K/second, and with a mere thousand, at 16K/second. I spent literally days
trying to get better results, but decided that it was more valuable to Quamina to handle a large subset of regular expressions
correctly than to run idiotically large merges at full speed.
</p>
<p>I’m pretty sure that given enough time and consideration, I’ll be able to make it better. Or maybe someone else who’s smarter
than me can manage it.</p>
<h2 id="p-11">Question: What next?</h2>
<p>The still-unimplemented regexp features are:</p>
<pre>{lo,hi} : occurrence-count matcher
~p{} : Unicode property matcher
~P{} : Unicode property-complement matcher
[^] : complementary character-class matcher</pre>
<p>
Now I’m wondering what to do next.
<code>[^]</code>
is pretty easy I think and is useful, also I get to invert a
state-transition table. The
<code>{lo,hi}</code>
idiom shouldn’t be hard but I’ve been using regexps for longer than most of you have been alive and have
never felt the need for it, thus I don’t feel much urgency. The Unicode properties I think have a good fun factor just because
processing the Unicode character database tables is cool. And, I’ve used them.
</p>
<p>
<i>[Update: the <code>[^]</code> thing took a grand total of a couple of hours to build and test. Hmm, what next?]</i>
</p>
<h2 id="p-10">Lesson: Coding while aging</h2>
<p>I tell people I keep working on code for the sake of preserving my mental fitness. But mostly I do it for fun. Same for
writing about it. So, thanks for reading.</p>
</div>
</content>
</entry>
<entry>
<title>Humanist Plumbing</title>
<link href="https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing"/>
<link rel="replies" thr:count="5" type="application/xhtml+xml" href="/ongoing/When/202x/2025/12/18/Humanist-Plumbing#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing</id>
<published>2025-12-18T12:00:00-08:00</published>
<updated>2025-12-20T10:40:20-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Business"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Business"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage capitalism. These days, that’s almost always a story worth telling</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage
capitalism. These days, that’s almost always a story worth telling.</p>
<p>
Normally, faced with a drip,
we’d pull out the old cartridge, take it to the hardware store, and buy another to swap in.
But the fixture in our
<a href="/ongoing/When/202x/2025/02/28/Moved">recently-acquired</a>
place was kind of exotic and abstract and neither of us
could figure it out. We were gloomy because we’ve had terrible luck over the years with the local plumbing storefronts.
So…
</p>
<h2 id="p-1">The neighbors</h2>
<p>Our neighborhood has an online chat; both sides of the streets in a square around a single city block. This is our first
experience with such a thing. I gather that these don’t always work out well, but this one has been mostly pretty great.</p>
<p>So at 9AM I posted “Hey folks, looking for a plumber recommendation” and by ten there were three.</p>
<p>
<i>[Late-stage capital: “You’re supposed to ask the AI in your browser. It’ll
provide a handy link to a vendor based on geography and reviews but mostly advertising spend.
Why would you want to talk to other people?”]</i>
</p>
<h2 id="p-2">Thomas</h2>
<p>I picked a neighbor’s suggestion, first name
Thomas, and called the number. “Thomas here” on the second ring. I explained and he said “What’s the brand name? If
it’s one of those Chinese no-names I probably have to replace the whole thing.” I said “No idea, but I’ll take a picture and send it to
you.”</p>
<p>
Turns out the brand was
<a href="https://riobel.design/en/">Riobel</a>
, never heard of them. I texted Thomas a picture and he got right back to me: “That’s
high-end, it’s got a lifetime warranty. I’ll come by a little after 5 and take it out. Their dealer is in PoCo (an outer suburb)
and I live out there, so I can swap it.”
</p>
<p>
<i>[Late-stage capital: “You’re supposed to engage with the chatbot on the site we sent you to, which will integrate with your
calendar and arrange for a diagnostic visit a week from Wednesday. You could call them but you’d be in voice-menu hell and
eventually end up at the same chatbot.”]</i>
</p>
<p>When Thomas showed up, with a sidekick, he was affable and obviously competent.
Within five minutes I was glad I’d called for help; that faucet’s construction was highly non-obvious. Thomas knew what he was
doing and it still took him the best part of a half-hour to get it all disassembled and the cartridge extracted.</p>
<h2 id="p-6">Nothing’s perfect</h2>
<p>The next morning, a text from Thomas: “Bad news. That part is back-ordered till May at Riobel’s dealer. We can maybe get it
online but you’d have to pay.” He attached a screenie of a Web search for the part number; there were several online
vendors.</p>
<p>It’s irritating that the “lifetime warranty” doesn’t seem to be helping me, but to be fair, the part was initially installed
in 2011.</p>
<p><i>[Late-stage capital: “Lifetime warranty? Huh? Oh, of course you mean our VIP-class
subscription offering, that’s monthly with a
discount for annual up-front payment.”</i> (And the part would still be back-ordered.)]</p>
<h2 id="p-3">Kolani</h2>
<p>
High-end plumbing parts are expensive. But one of Thomas’ recommendations,
<a href="https://kolani.ca">Kolani Kitchen and bath</a>
, was asking less.
</p>
<p>They had a phone number on their
Web site so I called it and the voice menu only had three options: Location, opening hours, and Operator.
The operator was an intelligent human and picked up right away.
“Hi, I’m looking at ordering a cartridge and wanted to see if you had it in stock.” “Gimme the part number?” I
did and she went away for a couple of minutes and came back “Yeah, it’s in stock.” So I ordered it and I have a tracking
number.</p>
<p>
<i>[Late-stage capital: “There aren’t supposed to be independent dealers; the manufacturer has taken PE money and eliminated
the middlemen to better capture all the value-add.
Or maybe there’ll be a wholesaler, but just one, because another PE rolled up all the distributors to maximize pricing power.
Either way, you won’t be able to get a human on the line.”]</i>
</p>
<h2 id="p-7">Payment</h2>
<p>Next morning, I got an email that my order had been canceled. So I called that intelligent operator and she said “I was going
to email you. Our system won’t take payment if the billing and delivery addresses are different. Sorry. If you’re in a hurry you
could do an e-transfer?” (In Canada, all the banks are in a payments federation that makes this dead easy.) So I
did and the part has shipped.</p>
<p>
<i>[Late-stage capital: “What? If you’d used our Integrated online payment offering, it would all just work. What if it
doesn’t, you ask? Yeah, sucks to be you in that situation, of course there’d be nobody you could talk to about that.”]</i>
</p>
<p>Thomas came by again to put the old cartridge back in for now and said “This thing, don’t worry about a drip, it’s not fast
and it probably won’t get worse. Text me when the new part gets in.”</p>
<h2 id="p-5">Late-stage capitalism</h2>
<p>It won’t be missed when it’s gone.</p>
</div>
</content>
</entry>
<entry>
<title>After the Bubble</title>
<link href="https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble"/>
<link rel="replies" thr:count="7" type="application/xhtml+xml" href="/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble</id>
<published>2025-12-07T12:00:00-08:00</published>
<updated>2025-12-09T15:29:05-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology/AI"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Technology"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="AI"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the damage will be and what the hangover will feel like. On that basis, I was going to post a link on Mastodon to Paul Krugman’s <a href="https://paulkrugman.substack.com/p/talking-with-paul-kedrosky">Talking With Paul Kedrosky</a>. It’s great, but while I was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.” So consider this a preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go read that</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the
damage will be and what the hangover will feel like.
On that basis, I was going to post a link on Mastodon to Paul Krugman’s
<a href="https://paulkrugman.substack.com/p/talking-with-paul-kedrosky">Talking With Paul Kedrosky</a>
. It’s great, but while I
was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.”
So consider this a
preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go
read that.
</p>
<h2 id="p-2">Depreciation</h2>
<p>When companies buy expensive stuff, for accounting purposes they pretend they haven’t spent the money; instead they
“depreciate” it over a few years. That is to say, if you spent a million bucks on a piece of gear and decided to depreciate it
over four years, your annual financials would show four annual charges of $250K.
Management gets to pick your depreciation period, which provides a major opening
for creative accounting when the boss wants to make things look better or worse than they are.</p>
<p>Even when you’re perfectly honest it can be hard to choose a fair figure. I can remember one of the big
cloud vendors announcing they were going to change their fleet depreciation from three to four years and that having an impact on
their share price.</p>
<p>Depreciation is orderly whether or not it matches reality: anyone who runs a data center can tell you about racks with 20
systems in them that have been running fine since 2012. Still, orderly is good.</p>
<p>
In the world of LLMs, depreciation is different. When you’re doing huge model-building tasks, you’re running
those expensive GPUs flat out and red hot for days on end. Apparently they don’t like that, and flame out way more often than
conventional computer equipment. Nobody who is doing this is willing to come clean with hard numbers but there are data points, for
example from
<a href="https://www.tomshardware.com/tech-industry/artificial-intelligence/faulty-nvidia-h100-gpus-and-hbm3-memory-caused-half-of-the-failures-during-llama-3-training-one-failure-every-three-hours-for-metas-16384-gpu-training-cluster">Meta</a>
and (very unofficially)
<a href="https://www.tomshardware.com/pc-components/gpus/datacenter-gpu-service-life-can-be-surprisingly-short-only-one-to-three-years-is-expected-according-to-unnamed-google-architect">Google</a>
.
</p>
<p>So GPUs are apparently fragile. And they are expensive to run because they require huge
amounts of electricity. More, in fact, than we currently have, which is why electrical bills are spiking here and there around
the world.</p>
<p>
Why does this matter? Because when the 19th-century railway bubble burst, we were left with railways. When the
early-electrification bubble burst, we were left with the grid. And when the
<a href="https://en.wikipedia.org/wiki/Dot-com_bubble">dot-com bubble</a>
burst, we were left with a lot of valuable
infrastructure whose cost was sunk, in particular dark fibre. The AI bubble? Not so much; What with GPU burnout and power charges,
the infrastructure is going to be expensive to keep running, not something that new classes of application can pick up and use on
the cheap.
</p>
<p>Which suggests that the post-bubble hangover will have few bright spots.</p>
<h2 id="p-1">SPVs</h2>
<p>This is a set of purely financial issues but I think they’re at the center of the story.</p>
<p>It’s like this. The Big-Tech giants are insanely profitable but they don’t have enough money lying around to build the
hundreds of billions of dollars worth of data centers the AI prophets say we’re going to need. Which shouldn’t be a problem;
investors would line up to lend them as much as they want, because they’re pretty sure
they’re going to get it back, plus interest.</p>
<p>But apparently they don’t want to borrow the money and have the debts on their balance sheet. So they’re
setting up “Special Purpose Vehicles”, synthetic companies that are going to build and own the data centers; the Big Techs
promise to pay to use them, whether or not genAI pans out and whether or not the data centers become operational. Somehow,
this doesn’t count as “debt”.</p>
<p>
The financial voodoo runs deep here. I recommend Matt Levine’s
<a href="https://newsletterhunt.com/emails/205961">Coffee pod financing</a>
and the
<cite>Financial Times’</cite>
<a href="https://www.ft.com/content/d0344253-b0a2-4c6d-8b97-520243678afd">A closer look at the record-smashing ‘Hyperion’
corporate bond sale</a>
. Levine’s explanation has less jargon and is hilarious; the
<cite>FT</cite>
is more technical but still likely to provoke horrified eye-rolls.
</p>
<p>If you think there’s a distinct odor of 2008 around all this, you’d be right.</p>
<p>If the genAI fanpholks are right, all the debt-only-don’t-call-it-that will be covered by profits and everyone can sleep
sound. Only it won’t. Thus, either the debts will apply a meat-axe to Big Tech profits, or (like 2008) somehow they won’t be
paid back. If whoever’s going to bite the dust is “too big to fail”,
the money has to come from… somewhere? Taxpayers? Pension funds? Insurance companies?</p>
<h2 id="p-3">Paul K and Paul K</h2>
<p>
I think I’ve set
<a href="https://paulkrugman.substack.com/p/talking-with-paul-kedrosky">that piece</a>
up enough now. It points out a few other
issues that I think people should care about. I have one criticism: They argue that genAI won’t produce sufficient revenue from
consumers to pay back the current investment frenzy. I mean, they’re right, it won’t, but that’s not what the investors are
buying. They’re buying the promise, not of
<em>more revenue</em>
, but of
<em>higher profits</em>
that happen when tens of
millions of knowledge workers are replaced by (presumably-cheaper) genAI.
</p>
<p>I wonder who, after the loss of those tens of millions of high-paid jobs, are going to be the
consumers who’ll buy the goods that’ll drive the profits that’ll pay back the investors. But that problem is kind of
intrinsic to Late-stage Capitalism.</p>
<p>Anyhow, there will be a crash and a hangover. I think the people telling us that genAI is the future and we
must pay it fealty richly deserve their impending financial wipe-out.
But still, I hope the hangover is less terrible than I think it will be.</p>
</div>
</content>
</entry>
<entry>
<title>Tracy Numbers</title>
<link href="https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics"/>
<link rel="replies" thr:count="2" type="application/xhtml+xml" href="/ongoing/When/202x/2025/12/02/Bell-Combinatorics#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics</id>
<published>2025-12-02T12:00:00-08:00</published>
<updated>2025-12-02T12:00:00-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts/Music"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Arts"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Music"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking a class in Afro-Cuban rhythms from <a href="https://drumming.ca">Russell Shumsky</a>, with whom I’ve studied West-African drumming for many years. Among the basics of Afro-Cuban are the <a href="https://en.wikipedia.org/wiki/Bell_pattern">Bell Patterns</a>, which come straight out of Africa. The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It feels like it’s in four, particularly when played fast</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking
a class in Afro-Cuban rhythms from
<a href="https://drumming.ca">Russell Shumsky</a>
, with whom I’ve studied West-African drumming for many years. Among the
basics of Afro-Cuban are the
<a href="https://en.wikipedia.org/wiki/Bell_pattern">Bell Patterns</a>
, which come straight out of Africa.
The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of
three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It
feels like it’s in four, particularly when played fast.
</p>
<p>Here’s the standard bell pattern in music notation. Instead of one 12/8 bar, I’ve broken it into four 3/8 chunks. Let’s call
those “mini-measures”; I’ll use that or just “minis” in the rest of this piece.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png" alt="standard 12/8 bell pattern"/>
<div class="caption">
<p>
<audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a"></audio>
</p>
</div>
<p>Bell patterns are never played in isolation, but circularly on fast repeat, so the first note immediately follows
the last.</p>
<p>
In the sound sample, I’m playing a background beat on a conga, emphasizing the beginning of the 12/8 measures.
The actual bell pattern is on the high “child” bell of a
<a href="https://en.wikipedia.org/wiki/Ewe_drumming#Gankogui">Gankoqui</a>
, an African dual-cowbell set.
</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/PXL_20251201_192632520.png" alt="Black cat considers a Gankoqui"/>
<div class="caption">
<p>
<a href="/ongoing/When/202x/2021/02/22/Meet-Thorn">“þ” the cat</a>
was trying bell patterns but
unfortunately
<br/>
cats can’t count as high as 12. Collar by
<a href="https://www.birdsbesafe.com">BirdsBeSafe.com</a>
.
</p>
</div>
<p>That’s my Gankoqui.
I bought it off someone on Etsy who imports them from Ghana.
It came with that little thin stick that sounds nice, but sometimes I use a regular drumstick when things get loud.</p>
<h2 id="p-1">The problem</h2>
<p>Russell’s a good teacher and the standard pattern isn’t that tricky, but I just couldn’t get a grip on it.
It’s a little harder than it looks what with cycling it really fast, and then
you’re playing it against complicated music with other instrumental voices.
I probably would have got there, but the lessons ran out of gas in the depths of Covid.</p>
<h2 id="p-2">Introducing Tracy</h2>
<p>
She was Russell’s long-time partner, a good person and good drummer too. When you were struggling
with a complex rhythm it was helpful to watch Tracy’s hands, because she was
<em>always</em>
on the beat.
</p>
<p>Tracy lived with stage four metastatic cancer for many years and braved endless awful rounds of therapy while remaining generally
cheerful. She could be morbidly funny; I bought her congas (you can hear one behind the beat in the samples) when she had a
storage-space problem. She told me she was carefully planning her finances so she’d run out of money just before the cancer got
her.</p>
<p>I always enjoyed any time I spent with her. Then, a dozen years into her cancer
journey, this last summer it got into her brain and it was pretty clear her end times were upon her.</p>
<h2 id="p-3">The hospice</h2>
<p>
Tracy’s last months were spent at
<a href="https://stjohnhospice.ca">St. John Hospice</a>
in Vancouver’s far west. I can’t say enough
good things about it. If you’re near Vancouver and your death becomes imminent, try to be there if you can’t be at home.
It’s comfortable and the staff are expert and infinitely kind. The rules that apply at hospices
are different from those at hospitals; for example, Tracy’s cat joined her in residency and had the run of the place.
</p>
<p>I (and other fans of Russell and Tracy) visited the hospice a few times. My last visit was just days before her death
and, while she was fatigued and spaced-out, it was still Tracy.
I wasn’t close enough to call her a friend, but I miss her.</p>
<p>
We got to talking about Afro-Cuban music and I laughed at myself, saying how I never could get that damn bell pattern
down. Said Russell: “Oh, you mean the standard 12/8 pattern? Tracy, let’s show him” and on the second try, they were doing it
together, just voices,
<i>ta ta ta-ta, ta ta ta</i>
.
</p>
<p>Driving home from the hospice, I told myself that if Tracy could manage the bell pattern in her condition, I could bloody
well learn it. So I studied the details and used a metronome app and after a while
I thought I had it down pretty well.</p>
<h2 id="p-4">Sounds cool</h2>
<p>I go to a weekly by-invitation African drum jam where I’m on the weaker end of the skill
spectrum. The first time a 12/8 came along after I thought I’d learned the pattern, I had to summon up courage
and then I fluffed the first few bars. But after a while I
was grooving along and smiling and thinking the bell sounded pretty cool against the thunder of all the djembés and dununs.</p>
<p>And, even played amateurishly, it does sound cool. Let’s have another look at the music.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png" alt="standard 12/8 bell pattern"/>
<div class="caption">
<p>
<audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a"></audio>
</p>
</div>
<p>West-African drumming often tries to achieve rhythmic tension, where a given note could fit in multiple ways and your
ear is not 100% sure what’s going on. The standard pattern does this, twice.</p>
<p>Remember, I said that 12/8 sounds like it’s
“in four”, especially if you hit the first beat of each of the four mini-measures. But two of
the four minis here go around the first note, weakening the 4/4 feel.
Especially on that third mini; you can feel the beat slide by the missing “one”.</p>
<p>Also, the last three notes are evenly spaced two beats
apart, so six of them would fill the 12-beat pattern, suggesting that this might be in triple time, not 12/8.</p>
<p>The effect, to my ears, is of the bell, higher-pitched than the drums, shifting against the rhythm, or even dancing
across it. At the drum jam, at almost any given moment it won’t be just drums, one or more people will have
clave sticks or rattles or tambourines or cowbells weaving through the beat.</p>
<h2 id="p-5">Mixing it up</h2>
<p>After I felt confident playing the standard pattern, it still sounded cool, but I wanted to branch out, not just
go around and around the same seven notes. So the first thing I did was start mixing in a few of these.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-1.png" alt="bell pattern variation"/>
<div class="caption">
<p>
<audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/5333.m4a"></audio>
</p>
</div>
<p>This repeats the second bar through the end of the phrase. In the sound sample I mix it up with the standard pattern.
It’s got less rhythmic tension but on the other hand
flows along smoothly with the drum thunder. Also you don’t have to think at all, so you can enjoy listening to what the other
people are playing.</p>
<p>Then I got a little more ambitious and reshuffled:</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-2.png" alt="bell pattern variation"/>
<div class="caption">
<p>
<audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/5253.m4a"></audio>
</p>
</div>
<p>The mini-measures are the same as in the standard pattern, just in a different order. Anyhow, this kind of thing is fun.</p>
<h2 id="p-6">Combinatorics</h2>
<p>Then one evening I was lying in bed, thoughts wandering, and wondered “How many bell patterns are there?”
A little mental math showed that of course there are eight possible arrangements of tones
in a 3-note mini-measure. Here they are:</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/8-measures.png" alt="Possible arrangements of notes in 3/8 time"/>
<div class="caption">
<p>I’ll use the boxed numbers to identify the minis.</p>
</div>
<p>Why are the minis numbered in that order? Every computer programmer looking at this already knows, but for the rest of you: If the
notes are ones and the rests are zeroes, they are the eight binary numbers between zero and seven inclusive.
So each number’s binary bits show where the drumstrokes are.
By the way, numbers four through
seven have a note on the one beat, zero through three don’t.</p>
<p>Is it weird to have a zero i.e. silent mini? I don’t think so, sometimes spaces between the notes really matter.</p>
<h2 id="p-7">Patterns</h2>
<p>Anyhow, the original question was about the number of different bell patterns. Each has four
mini-measures with 8 possible values. So the answer is 8 ⨉ 8 ⨉ 8 ⨉ 8, which is 4,096.</p>
<p>And each of them can be identified by four little numbers, ranging from T0000 (I can hear the bandleader yelling “gimme zeroes
for the sax break”) to T7777, a flurry of eighth notes that you might use in the big encore-number finish designed to leave the
audience yelling as you walk off stage. The standard bell pattern is T5325; in binary “101 011 010 101” and the 1’s are drumstrokes.
The first variation above is T5333 and the second is T5253.</p>
<p>The “T” in front of each bell pattern number is for Tracy.</p>
<p>
If you go look at the
<a href="https://en.wikipedia.org/wiki/Bell_pattern">Wikipedia Bell-pattern article</a>
, they emphasize that there are lots of
different patterns. Now they all have numbers! The article
<a href="https://en.wikipedia.org/wiki/Bell_pattern#128_bell_patterns">makes special mention of</a>
T5124, T5221, and T5244.
</p>
<h2 id="p-8">But why, Tim?!</h2>
<p>I’m a computer programmer with a Math degree, and an amateur musician.
Anyone who thinks that these are disjoint disciplines is wrong.
And, I think the notation is (on a very small scale) kind of pleasing.</p>
<p>But the work has actually helped me.
Now that I’ve considered each mini-measure and its personality. I find all of them sneaking into
my Gankoqui excursions, which have gotten noticeably weirder, for example T5635.
Nobody’s threatened to kick me out of the jam, so far.</p>
<p>Also, this has given me a real appreciation of whoever it was that, probably thousands of years ago and certainly in Africa,
picked the “standard” pattern as, well, standard. Because it’s great.</p>
<h2 id="p-9">What’s missing?</h2>
<p>
You may have noticed that Gankoquis have two bells and I’ve been ignoring that fact. Normally you’d play these patterns
on the smaller “child” bell, but sometimes bringing the big parent bell in for a couple of strokes works
well.
<a href="https://www.youtube.com/watch?v=X2K0i8e6Ftc">Here’s an example</a>
(h/t Russell).
</p>
<p>
Also, this discussion has been limited to 3/8 minis in 12/8 measures. There’s another whole universe of 4/4 rhythms that
also have bell patterns (but everything exists in the shadow of the
<a href="https://en.wikipedia.org/wiki/Clave_(rhythm)">clave rhythm</a>
).
In that world a pattern has four measures, each of which can have sixteen possible values, so there are 65,536 different ones.
</p>
<p>
And I could repeat the numbers construction above for 4/4. But I’m not going to, because the rewards feel smaller. In my
experience, 4/4 rhythms lope smoothly along and everyone knows where the one is even when there’s no note on it, so there’s less
ambiguity to work with.
Anyhow, any neophyte (like for example me) can play a pretty smooth bell line against 4/4; just start with
<a href="https://en.wikipedia.org/wiki/Clave_(rhythm)">clave</a>
and add
variations (or don’t) and you’ll be fine.
</p>
<h2 id="p-10">Useful?</h2>
<p>These numbers are just elementary mathemusical fun. If anyone else wanted to use them that’d be a pleasant surprise.
If “anyone else” is you, go ahead, but they have a name and you have to use it. These are called Tracy Numbers.</p>
<h2 id="p-11">Colophon</h2>
<p>
Music fragments by
<a href="https://www.mu.se/musescore-studio">MuseScore Studio</a>
. Sound samples facilitated by GarageBand, a Shure MV51, and PSB
Alphas.
</p>
</div>
</content>
</entry>
<entry>
<title>Fútbol Joy</title>
<link href="https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football"/>
<link rel="replies" thr:count="1" type="application/xhtml+xml" href="/ongoing/When/202x/2025/11/23/Soccer-vs-Football#comments"/>
<id>https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football</id>
<published>2025-11-23T12:00:00-08:00</published>
<updated>2025-11-27T20:38:07-08:00</updated>
<category scheme="https://www.tbray.org/ongoing/What/" term="Sports/Football"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Sports"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Football"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Sports/Soccer"/>
<category scheme="https://www.tbray.org/ongoing/What/" term="Soccer"/>
<summary type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">Last Saturday I had one of my peak 2025 experiences, at the <a href="https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs">MLS semifinal</a> between the <a href="https://www.whitecapsfc.com/">Vancouver Whitecaps FC</a> (hereinafter “Caps”) and <a href="https://en.wikipedia.org/wiki/Los_Angeles_FC">Los Angeles FC</a> (“LAFC”). Both those FC’s stand for “Fútbol Club”. 53,095 other fans were there with my son and I; we came home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports</div>
</summary>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>
Last Saturday I had one of my peak 2025 experiences, at the
<a href="https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs">MLS semifinal</a>
between the
<a href="https://www.whitecapsfc.com/">Vancouver Whitecaps FC</a>
(hereinafter “Caps”) and
<a href="https://en.wikipedia.org/wiki/Los_Angeles_FC">Los Angeles FC</a>
(“LAFC”). Both those FC’s stand for “Fútbol Club”.
53,095 other fans were there with my son and I; we came
home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports.
</p>
<p>
Earlier this year
<a href="/ongoing/When/202x/2025/05/04/Southsiders">I wrote about becoming a Caps fan</a>
. Anyone who enjoys this will probably
like that piece too.
</p>
<p>Let’s set the scene with pictures.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_004124670.png" alt="Before the fútbol at the pub"/>
<div class="caption">
<p>Supporters gather pre-game at a nearby Irish-flavored pub.</p>
</div>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_011735082.png" alt="Parading from the pub to the match"/>
<div class="caption">
<p>
Supporters march to the game.
<br/>
When you’re in a frivolous parade, everyone smiles
<br/>
at
you, even the drivers hemmed in by paraders.
</p>
</div>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_024033770.png" alt="Whitecaps tifo banner: fire that burns / blue melts gold"/>
<div class="caption">
<p>
The banner is what’s called a
<a href="https://en.wikipedia.org/wiki/Tifo">tifo</a>
.
<br/>
I have to admit I failed to parse it.
</p>
</div>
<h2 id="p-5">The game</h2>
<p>
It was 120 minutes of ridiculously over-the-top psychodrama. I was exhausted at the end.
If you want a full retrospective, type “whitecaps lafc” into any Web search to get the particulars. Or
<a href="https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs">hit
this</a>
. But here’s the short version:
</p>
<ol>
<li>
<p>
The Caps came out sharp and fast and had LAFC pretty well flummoxed through most of the first half, scoring two goals,
<a href="https://www.youtube.com/watch?v=9nEOw8ckWMA">one of which was a jaw-dropper</a>
.
They also managed to contain LAFC’s superstar
<a href="https://en.wikipedia.org/wiki/Son_Heung-min">Son Heung-min</a>
.
</p>
</li>
<li>
<p>
In the second half, the visitors reconfigured and were much better. Son did the superstar thing and scored two goals,
<a href="https://www.youtube.com/watch?v=-L9N8pkrkSM">one another jaw-dropper</a>
, just as the game was ending, to tie things
up.
</p>
</li>
<li>
<p>The Caps lost two players, one for fouls, one to injury, and were down two men through most of overtime. LAFC’s assault
was relentless but the Caps held on, getting more than a little lucky.</p>
</li>
<li>
<p>So it went to a penalty-kick competition. Son, shockingly, missed; he was exhausted and limping. At the end of the
day the Caps scored four out of five to LAFC’s three and got the win.</p>
</li>
</ol>
<p>Suffice it to say that the dramatic peak wasn’t
any of the flashes of brilliance, but rather the errors that happen when people are at the limit of their endurance. Vancouver
made one fewer, that’s all there was to it.</p>
<h2 id="p-3">That sound</h2>
<p>There’s not another like it on this planet. I mean tens of thousands of voices in a big stadium greeting a home goal.
Fútbol specifically because its goals, compared to North American sports where points come in dozens, are
such huge markers. The sound-pressure wavefront, coming from every direction, of all those inarticulate howls of joy,
all in the same tiny fraction of a second, is a whole-body experience.</p>
<h2 id="p-6">The side effect</h2>
<p>I’ve long been a televised-sports fan; the only TV show that isn’t scripted and thus has real drama. But
since getting mixed up in fútbol, I’ve sort of gone off the other sports I used to watch. I had to think a bit to figure
out why.</p>
<p>
It’s the ads. The football, basketball and hockey broadcasts screech to a halt
<a href="https://qz.com/150577/an-average-nfl-game-more-than-100-commercials-and-just-11-minutes-of-play">every ten or fewer
minutes</a>
for a couple of minutes of advertising. Most of the ads are dumb, many are offensive, and the relentless
addiction-promoting gambling pitches are both. On top of which there’s the bone-headed repetition; someone somewhere thinks
I’m gonna lean toward this generic SUV as opposed to that one because of the 138th time they’ve run that commercial where hip young
people with fulfilling lives are going to have sex because of its dashboard geometry and motorized hatchback.
I mean, the other SUVs have that stuff too, but this one’s actors are more convincingly likely to be headed for bed?
</p>
<p>Being in the room with this shit makes me angry even though my mute-button skillz are sharp.
The world being what it is, I really don’t need to be around something that angers me several times per hour.
So, while when young I loved playing both football and basketball, and while the pro games are good entertainment,
my patience seems to be running out.</p>
<p>Fútbol, on the other hand, has two fiftyish-minute chunks of continuous action, so you can sink into the flow of the
game. The contrast, switching back and forth between that and the other North American sports, is stark.</p>
<p>(Except for I’m mostly forgiving baseball because its natural rhythm is full of stops suitable for hot dogs and beer and
admiring cute babies and T-shirts and discussions of etymology and epidemiology. I mean, the ads are still mindless repetitive
shit, we’re just more accustomed to switching attention away when nothing’s happening.)</p>
<p>
And I’m not claiming that fútbol is more virtuous or less dirty than any other sport; after all, its global
organizing body FIFA has repeatedly been exposed as
<a href="https://en.wikipedia.org/wiki/FIFA#Corruption">galactically corrupt</a>
. I’m just saying it offers a better
experience.
</p>
<h2 id="p-9">Soccer?</h2>
<p>That word is an awkward invention by nineteenth-century British toffs based on abbreviating “association”. I accept that on my
continent “football” means gridiron, but people who enjoy “soccer” still say it so in print I offer “fútbol”, which is a
typographically nice little cluster; please humor me.</p>
<p>Anyhow, you might want to check out your local team; in North America, the prices are lower than the other sports, who could
be against cheap happiness with fewer gambling ads?</p>
</div>
</content>
</entry>
</feed>
<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns='http://www.w3.org/2005/Atom'
xmlns:thr='http://purl.org/syndication/thread/1.0'
xml:lang='en-us'>
<title>ongoing by Tim Bray</title>
<link rel='hub' href='http://pubsubhubbub.appspot.com/' />
<id>https://www.tbray.org/ongoing/</id>
<link href='https://www.tbray.org/ongoing/' />
<link rel='self' href='https://www.tbray.org/ongoing/ongoing.atom' />
<link rel='replies' thr:count='101' href='https://www.tbray.org/ongoing/comments.atom' />
<logo>rsslogo.jpg</logo>
<icon>/favicon.ico</icon>
<updated>2026-04-27T12:05:18-07:00</updated>
<author><name>Tim Bray</name></author>
<subtitle>ongoing fragmented essay by Tim Bray</subtitle>
<rights>All content written by Tim Bray and photos by Tim Bray Copyright Tim Bray, some rights reserved, see /ongoing/misc/Copyright</rights>
<generator uri='/misc/Colophon'>Generated from XML source code using Perl, Expat, Emacs, Mysql, Ruby, and ImageMagick. Industrial-strength technology, baby.</generator>
<entry>
<title>Corey’s Captives</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/04/26/Coreys-Captives#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives</id>
<published>2026-04-26T12:00:00-07:00</published>
<updated>2026-04-27T12:05:14-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Books' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Books' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>That’s <a href='https://en.wikipedia.org/wiki/James_S._A._Corey'>James S.A. Corey</a>, which is to say Daniel Abraham and Ty Franck, and their new series <a href='https://en.wikipedia.org/wiki/The_Captive%27s_War'>The Captive’s War</a>, an in-progress work comprising 2¼ or so novels. The Coreys are of course best-known for their deservedly wildly popular <cite>The Expanse</cite> series and the subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should wade in, the following is for you</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>That’s
<a href="https://en.wikipedia.org/wiki/James_S._A._Corey">James S.A. Corey</a>, which is to say Daniel Abraham and Ty Franck,
and their new series
<a href="https://en.wikipedia.org/wiki/The_Captive%27s_War">The Captive’s War</a>, an in-progress work comprising 2¼
or so novels. The Coreys are of course best-known for their deservedly wildly popular <cite>The Expanse</cite> series and the
subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should
wade in, the following is for you.</p>
<h2 id='p-1'>Minor and meta spoilers</h2>
<p>Don’t worry, you can go on reading this even if you plan to read the books. Here’s a spoiler that has appeared in every public
mention of the book, which I’ll give away with a quote from page 102: “I think some important scientific questions have finally
been answered. Alien life exists, and they are assholes.” Which is to say, it doesn’t go well for the humans.</p>
<p>Now for the meta-spoilers. The novels are <cite>The Mercy of Gods</cite> and <cite>The Faith of Beasts</cite>, then there’s a
novella, <cite>Livesuit</cite>. I found <cite>The Mercy of Gods</cite> a bit of a grind, and if that’s all I’d read I would have
been pretty negative about this project. There is a major, <em>major</em> reveal partway into <cite>The Faith of Beasts</cite>
that changed my whole outlook on the series; it makes the storytelling velocity really pick up. It’s a little annoying that
<cite>Livesuit</cite> was published between the two full novels because it only really makes sense if you’ve finished both of
them. So do like I did, and read the novella last.</p>
<p>I have to ask why the Coreys couldn’t have pulled the curtain aside a little earlier on. And while I’m griping, let me add
that the sped-up storytelling runs into a big honking cliffhanger ending at high velocity. Harumph.</p>
<h2 id='p-2'>My take-away</h2>
<p>It could go off the rails but if they can maintain their <cite>Expanse</cite> form, I suspect this series is going to be
pretty great. The characters are fun to know and the narrative revolves around the great mother of all trolley-problem ethical
challenges, which was not nearly resolved at cliffhanger-ending time.</p>
<p>Those of us who are fussy about the plausibility of future technologies (hey, Charlie Stross) should avert their eyes from
the Coreys’ fairly low-effort attempts to explain how the aliens and humans in this story accomplish the things they do. Doesn’t
bother me much, though.</p>
<p>Having said all that, this series is not cheerful stuff; I do <em>not</em> recommend it to those who, like many in these
troubled times, are having trouble seeing the bright side of, well, anything.</p>
<h2 id='p-3'>Will I read the next volume?</h2>
<p>Yep, no hesitation. And they’ve already started working on a streaming version. Unfortunately it’s going to be on Amazon
Prime, which I haven’t missed since unsubscribing a couple years ago. Getting this thing on the screen is
going to be an extended, difficult, task. There are multiple species of aliens that the show is going to have to absolutely nail, with
emotional credibility, for the story to work. Don’t hold your breath.</p>
</div></content></entry>
<entry>
<title>Spring Evening</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/04/13/Modern-Cameras#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras</id>
<published>2026-04-13T12:00:00-07:00</published>
<updated>2026-04-15T22:23:17-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>On impulse, Lauren and I went out for a short walk<span class="dashes"> —</span> around just a few blocks<span class="dashes"> —</span> as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera on the way out the door</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>On impulse, Lauren and I went out for a short walk<span class='dashes'> —</span> around just a few
blocks<span class='dashes'> —</span> as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera
on the way out the door.</p>
<p>In our local community garden, here’s (I think) a
<a href="https://en.wikipedia.org/wiki/Chard">chard</a>.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56259.png" alt="Looking down on a vegetable plant with glossy green leaves and orange-yellow stalks" />
<p>That was in Vancouver’s Mount Pleasant park, small but nice and apparently never not used. Also this old blackened
fruit tree, we’re a bit past the fruit-blossom peak for this year. Nice to see I’m not the only old citizen trying to brighten
things up.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56264.png" alt="Fruit-tree blossoms on a blackened branch" />
<p>Now we’re walking up a locally-main street called Main Street or “The Main” if you’re trying to sound
hip. Someone put work into that window! I’ve bought my daughter a couple of cool birthday presents from the store behind it. My
thanks to the building across the street for providing a dark background reflection.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56265.png" alt="Used-fashion store window " />
<p>Back to the next block over from ours. A while ago a bunch of people were building little fairy/elf/hobbit villages at the
bottoms of the big old trees. This isn’t that. What is it?</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56270.png" alt="Dolls and related tree artifacts at the base of a tree in dim light" />
<p>The colors of the natural surfaces are real.</p>
<h2 id='p-1'>Cameras</h2>
<p>When I shot these, it
was getting dark but I didn’t think much, mostly just pointed and shot. (Fiddled with the aperture dial a bit.) Then I came
home and pulled them into Lightroom and didn’t need to do really anything about colors. A bit of contrast and highlights here
and there. Oh, and fairly brutal cropping, especially on that fruit-tree-flowers pic. Because like I said, I didn’t think very
much when I was shooting and I didn’t have to because on a Twenties camera you don’t.</p>
<p>I could take that heavily-cropped fruit-tree
picture and print it big enough to occupy any domestic wall in your place and yeah, there’d be grain but it wouldn’t
bother your eyes.</p>
<p>Anyhow, modern cameras are pretty great. The lowest ISO in today’s set is 2500 and the highest is 6400; the apertures range
from 2.8 to 5.6.
Bet you can’t tell the differences. My camera is a reasonably modern Fujifilm but not remotely
bleeding-edge in camera tech. (Note: 35mm F1.4, now all the Fuji fanfolk are smiling and nodding.)</p>
<p>Anyhow, there are very <em>very</em> few photographers for whom the camera they carry is the limiting factor in the
goodness of their pictures. Certainly not me.</p>
<p>Consider getting a camera. Used is fine, anything built in the last five years, maybe more, will effortlessly take brilliant
pictures in almost any conditions. Sure, your phone can take great shots too, but the feeling of walking along with something
that fits your hand and you only have to press one physical button once, that feeling, it helps you see the good pictures when they happen.</p>
<p>Then go out after and take a walk in the Spring dusk.</p>
</div></content></entry>
<entry>
<title>Password Manager Angst</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst' />
<link rel='replies' thr:count='13' type='application/xhtml+xml' href='/ongoing/When/202x/2026/04/09/Password-Manager-Angst#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst</id>
<published>2026-04-09T12:00:00-07:00</published>
<updated>2026-04-10T10:42:16-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Identity' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Identity' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Security' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Security' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Our family has used <a href='https://1password.com'>1Password</a> for many years. Most recently 1Password 7, now at least three years out of date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring <a href='https://bitwarden.com'>Bitwarden</a>. The best choice isn’t obvious; here’s the story thus far</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Our family has used
<a href="https://1password.com">1Password</a> for many years. Most recently 1Password 7, now at least three years out of
date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring
<a href="https://bitwarden.com">Bitwarden</a>. The best choice isn’t obvious; here’s the story thus far.</p>
<p>Important note: I suspect that most-to-all of the people reading this already are using a password manager. If you’re not,
please, <i><b>PLEASE</b></i> start now. Your browser probably has an OK one built-in, which is much better than
nothing.
<a href="https://www.cyber.gc.ca/en/guidance/password-managers-security-itsap30025">Here</a> is a good write-up on the basics.</p>
<h2 id='p-6'>Our needs</h2>
<p>They’re not fancy. The house contains Macs and Androids and Windows and an iPad.
We have hundreds of accounts (some require an authenticator) and a basketfull of secure notes: Government-ID numbers, recovery
codes, and so on.</p>
<h2 id='p-5'>1Password7 and 8</h2>
<p>1Password had this nice feature where you could sync between devices without involving any 1Password servers, in a variety
of ways. We used one of those and liked it.
1Password8 insists on storing your data (encrypted, more on that later). That always bothered me because, obviously, that
repository is a top-priority juicy target for all the bad guys, who range from employees of the Chinese government to geeky
narcos.</p>
<p>So we’ve been ignoring 1Password’s increasingly plaintive reminders that we were using years-out-of-date software
and chugging along with version 7. But, early this year, they broke our sync mode on the Android app and were pretty blunt that the only
way to get it back was to go to 1P8.</p>
<h2 id='p-7'>Alternatives</h2>
<p>There are plenty of password managers (Let’s just say “PMs”) out there, but as a regular scanner of the landscape,
it seems to me that 1Password
(hereinafter “1P”) and Bitwarden (“Bw”) stand out as leaders. The rest of this piece will focus on those two.
If you think I’m wrong, say so below but also please say why.</p>
<p>Note that Bw comes in two flavors: That offered as a subscription service by the company of the same name, or as an open-source
software suite you can build and run yourself.</p>
<p>This is not to say that the PMs that are starting to appear built-in to browsers and OSes are worthless or unimportant,
just that some of us need a little more.</p>
<h2 id='p-8'>The threat models</h2>
<p>Two are obvious. The first is incompetence, like for example
<a href="https://en.wikipedia.org/wiki/LastPass#Security_incidents">LastPass</a>, who apparently left the doors more or less
wide open to those bad guys I mentioned a few paragraphs ago. Complete horror-show.</p>
<p>The second is legal compulsion, where a government applies pressure to a PM provider to cough up our
secrets. Anybody who thinks governments won’t try is fooling themselves, because they’ve repeatedly said they want to, and are
eager to pass ill-considered legislation such as the
<a href="https://en.wikipedia.org/wiki/CLOUD_Act">CLOUD Act</a>. So we care about that aspect a lot.</p>
<h2 id='p-9'>1P vs Bw: Security</h2>
<p>I think they both have acceptably-good security postures; check out
<a href="https://bitwarden.com/help/bitwarden-security-white-paper/">Bitwarden Security Whitepaper</a> and
<a href="https://support.1password.com/1password-security/">About the 1Password security model</a>.</p>
<p>Both of them offer to host your data outside of the US, specifically in Canada or the EU.</p>
<p>But it doesn’t matter <em>that</em> much if a bad guy or bad government gets their hands on your password store; what
matters is whether or not they can decrypt it. I’m not an infosec professional but I know some and listen to them, and both
those security postures give me a good feeling. It’s not an accident that they’re pretty similar.</p>
<p>The actual threat isn’t so much that an adversary cracks the crypto; that’s very unlikely. It’s that they find a way to force
a PM vendor to build a back door into their software to get access to keys and passwords. For that reason, it would warm
my heart if either or both of Bw and 1P were to post a
<a href="https://en.wikipedia.org/wiki/Warrant_canary">Warrant Canary</a>.</p>
<p>But I’m going to give Bw a very slight edge. First, because of the fact that you can build and run it yourself, if you’re
willing to take responsibility for operating a server with strong security requirements. (I’m not.)</p>
<p>The source being open potentially offers a second, and more important I think, advantage: If they were able to get a
<a href="https://en.wikipedia.org/wiki/Reproducible_builds">Reproducible build</a> working, you’d have assurance that the code
you can download is the one their service is running. Which reduces the attack surface. (Mind you,
<a href="https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf">not to zero</a>.) Reproducible
builds are hard, but if they did that, it would make a difference to me.</p>
<p>On the other hand, Bw’s software development process
<a href="https://contributing.bitwarden.com/contributing/ai/">embraces GenAI</a> generally and Claude specifically.
At this stage in the growth of those technologies, this sends a chill up my spine. To be fair, 1P’s website
shouts that it’s just the thing for agentic security, whatever that means. And we don’t know anything about 1P’s internal
software-dev process.</p>
<h2 id='p-10'>1P vs Bw: Fit and finish</h2>
<p>1P wins this one. The problem is, do they always pop up when needed and never when they’re not? Can they fill every login
field that needs filling? Does the popup show you just what you need and nothing extraneous? I’ve used both and 1P is just
better.</p>
<h2 id='p-11'>Business issues</h2>
<p>This one is also pretty well a saw-off. Both of them have taken substantial chunks of VC money and thus are going to
come under relentless pressure to enshittify. I worry a little less about this because from what I read,
there’s not much lock-in.</p>
<p>Personal experience too: I recently did an export of everything out of 1P and into Bw and it all Just Worked, albeit putting all
my stuff into a folder named "No Folder" that I can’t figure out how to rename.</p>
<p>Both Bw and 1P are subscription-only, at prices that seem fair to me.</p>
<h2 id='p-12'>Death and recovery and pen and paper</h2>
<p>As I was reading up on this stuff, the issue of recovering access to your PM after it had been lost came up a couple of times.
Here’s a scenario where that could be really important: I die. And then my wife needs to get access to bank accounts and
business emails and so on.</p>
<p>Somebody (I’ve lost the link) was horrified that one of the PMs suggested writing the password down on a piece of paper as a
last-resort measure, but I’m here to tell you that they’re wrong. My wife has an envelope containing a piece of paper on which
appear the passwords for my PM and Mac, my mobile-phone PIN, and a very small number of other secret things she might really
need if I’m suddenly gone. I have no idea where she put it, but she’s really smart so I don’t worry.</p>
<p>You should probably do something like this too.</p>
<h2 id='p-13'>What will we do?</h2>
<p>We’ve paid for a year’s worth of both Bw and 1P. At the moment, we’re leaning to 1P because it’s a little more polished.
Which matters because my PM is something I use many times every day. Also they’re somewhat Canadian.</p>
<p>If you think we’ve missed something, please do let us know.</p>
</div></content></entry>
<entry>
<title>Long Links</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links' />
<link rel='replies' thr:count='2' type='application/xhtml+xml' href='/ongoing/When/202x/2026/03/24/Long-Links#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links</id>
<published>2026-03-24T12:00:00-07:00</published>
<updated>2026-03-26T16:36:32-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
<category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>This will be the 30<sup>th</sup> Long-Links outing. I’m 100% sure that there does not live a human being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to open one occasionally. All aboard!</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>This will be the 30<sup>th</sup> Long-Links outing. I’m 100% sure that there does not live a human
being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to
open one occasionally. All aboard!</p>
<p>Sadly, more than half the Long Links, this time out, are about AI. I almost decided to bury the piece but, whatever you or I
think, the subject matters. And the ones I posted are a tiny fraction of those I read (or tried to) and I think are
useful and not immoral.</p>
<p>But, let’s put all the non-AI stuff at the front so you can stop reading partway through if you’ve just had enough of
that stuff.</p>
<h2 id='p-1'>Not about GenAI</h2>
<p>Paul Ford has, after a lengthy gap, started writing again at
<a href="https://ftrain.com">ftrain.com</a>. Excellent!
Go there any day and there’ll almost certainly be something good at the top of the
page. He’s a technologist and, yeah, writes about AI sometimes, but
<a href="https://ftrain.com/warp-and-woof">Warp and Woof</a> is about dogs and their people. Charming.</p>
<p>I think most people who aren’t ultra-wealthy now agree that inequality is currently a central problem of our society. But it
would be nice to put some numbers behind that assertion.
<a href="https://paulkrugman.substack.com/p/talking-with-gabriel-zucman">Here</a> is a conversation between Paul Krugman,
Nobel-prizewinning economist, and Gabriel Zucman, a French specialist in the subject and frequent Piketty collaborator.
Now, there are quite a few paragraphs up front of talk about general macroeconomic issues and comparisons between the US and Europe,
which I enjoyed reading. And then inequality; here’s Zucman: “And so everybody now understands what was long understood for
centuries, very much including in the West, which is that extreme wealth is never virtual, it is always extreme power.”</p>
<p>CO<sub>2</sub> densities in Parts Per Million are a good measure of how full your inhalations are of others’ exhalations. And
thus of how likely you are to catch something by breathing. Especially, Covid, which everyone with a half a brain knows is not
nearly over. Anyhow, A. Grieve-Smith offers
<a href="https://grieve-smith.com/ftn/2026/03/nine-observations-from-carbon-dioxide-monitoring/">Nine observations from carbon
dioxide monitoring</a>: “I’ve been checking carbon dioxide levels for over three years now, and I’ve started to see patterns.”
This piece could save your life, and that’s not a metaphor.</p>
<p>Patrick McKenzie, who writes <cite>Bits About Money</cite>, has an icy-cool style and this Link could be a Little Less Long,
but I learn interesting things every time I read one of his pieces.
<a href="https://www.bitsaboutmoney.com/archive/fraud-investigation/">Fraud Investigation is Believing Your Lying
Eyes</a> launches from the Minnesota child-care fraud story, but is mostly, as the title suggests, relates the conventional wisdom
(which I didn’t know) about how to go sniffing around for in-progress fraud.
From which “As a fraud investigator, you are allowed and encouraged to read Facebook at work.”</p>
<p>Hari Kunzru has written good books and is a former London native. <cite>Harpers</cite> gave him an assignment:
Walk around and write about the city, thus
<a href="https://harpers.org/archive/2026/02/another-london-situationists-hari-kunzru/">Another London: Excavating the
disenchanted city</a>. It’s a tour through time as much as space<span class='dashes'> —</span> London, obviously, is
history-drenched<span class='dashes'> —</span> and not just politics and power either, but arts and ideas. The writing is
beautiful. It’ll take a chunk out of your day but the trade-off is good.</p>
<p>Here’s something beautiful:
<a href="https://thehtml.review/05/">The HTML Review</a>. Now I want to publish there, but I’d have to up my
writing game.</p>
<h2 id='p-5'>Lankum</h2>
<p>They’re an Irish band I just discovered, courtesy of Qobuz. The music grows out of traditional Irish acoustic folk. They play
old and new songs and throw in a heavy dose of snarl and drone. Some of the chords are like rotated model augmented 11ths or some
such, scratchy around the edges but helped with an itch I hadn’t known I had. Terrific musicians. Here’s
<a href="https://www.youtube.com/watch?v=lUReQ9GhT8s">Hunting the Wren</a>. I might get over-excited and fly to Ireland to see them.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/24/Lankum.png" alt="Lankum in concert" />
<h2 id='p-2'>Tech, but not GenAI</h2>
<p>Sebastian Pipping is, among other things, an Open-Source software developer, with whom
<a href="/ongoing/When/202x/2021/03/24/XMLWF-dash-k">I’ve collaborated</a>. His recent
<a href="https://blog.hartwork.org/posts/learn-from-me/">Learn from me!</a> begins “Not too long ago, someone literally asked me
what they "could learn from me", and that question has stuck with me since.” So he offers a few candidate lessons. What a nice
idea! What could people learn from <em>you</em>?</p>
<p>Filippo Valsorda, another OSS dev, is particularly interesting because he and a few partners have apparently figured out
<a href="https://geomys.org">how to make a living from their work</a>.
He recently published
<a href="https://words.filippo.io/dependabot/">Turn Dependabot Off</a> and I’m not going to offer a word of explanation because
if you understand the title I guarantee you’ll be interested in the piece. (I’m terrified of Dependabot.)</p>
<p>It seems like every day I hear from another person who’s trying to get their personal lives off Big Tech. Me too. So…
In <cite>The Verge</cite>,
<a href="https://www.theverge.com/tech/879114/best-big-tech-app-alternatives-installer">How to un-Big Tech your online life</a>.
And from Paris Marx,
<a href="https://disconnect.blog/getting-off-us-tech-a-guide/">Getting off US tech: a guide</a>. We are in the early stages of
de-Googling our family life, so this stuff is super useful. I expect to see more of it.</p>
<h2 id='p-4'>Amazon polemics, maybe a little AI</h2>
<p>I don’t loathe Amazon any more nor less than the rest of the Big Techs, but boy are there are a lot of people
publishing diatribes against the company. Not sure I understand why. But, worth reading.</p>
<p>In
<a href="https://markatwood.substack.com/p/how-amazon-dies-a-possible-maybe?">How Amazon Dies: A Possible, Maybe Likely
Future</a> Mark Atwood predicts that the infestation of amazon.com with highly-profitable advertising is a perhaps-fatal
blunder. What’s maybe more interesting is that he points out several potential Amazon alternatives that don’t suffer from
that same infestation; they hadn’t occurred to me.</p>
<p>And from a year ago, Cory Doctorow’s
<a href="https://pluralistic.net/2025/03/13/electronic-whipping/#youre-next">The future of Amazon coders is the present of
Amazon warehouse workers</a> introduces the “shitty technology adoption curve”. I missed this piece at the time but boy, is it
easy to believe.</p>
<p>Finally, reading
<a href="https://www.bigtechnology.com/p/writing-crystalized-thinking-at-amazon?">Writing Crystalized Thinking At Amazon. Is AI
Muddying It?</a> angered me. While I have no remaining respect or affection for any of the Big Techs, I enjoyed my time at AWS
and part of it was the writing culture. I think the Way Of The Six-pager is the best business-process innovation I witnessed in
my working life. If Amazon really is slopifying it, I predict disastrous outcomes. </p>
<h2 id='p-3'>OK, here’s the AI stuff</h2>
<p>My own position, just to be clear: There are going to be LLM applications in a few domains here and there, and one of them is
software development, but they won’t be nearly big enough to damage earth’s climate any further, nor to prevent the bubble from
popping. That said…</p>
<p>Let’s do the worst first:
<a href="https://www.heavybit.com/library/article/write-only-code">Write-Only Code</a> lays out a genuinely frightening future.
Quote: “I was maniacally insistent that any proposed change to our SDLC (software development life cycle) be evaluated first
through the lens of developer velocity.”
I think I’d rather not go there.</p>
<p>Most of us who watch the space, and have no idea where it’s going or what the future holds, are I think particularly
interested in Anthropic’s Claude. If you’re one, you’ll probably enjoy
<a href="https://www.newyorker.com/magazine/2026/02/16/what-is-claude-anthropic-doesnt-know-either">What Is Claude? Anthropic
Doesn’t Know, Either</a>.</p>
<p>It’s probably not that GenAI is intrinsically immoral. As Karl Bode writes,
<a href="https://karlbode.com/the-problem-with-ai-is-shitty-human-beings/">The Problem With AI Is Shitty Human Beings</a>. I
covered some of the same territory last year in
<a href="/ongoing/When/202x/2025/07/06/AI-Manifesto">The Real GenAI Issue</a>, but Bode is excellent:
“…the grand vision of modern automation's benefits can never materialize if its stewards are <i>foundationally fucking terrible
human beings disinterested in the contours of empathy.</i> If we're not talking prominently about that, we aren't really talking at
all.” (Emphasis his.)</p>
<p>One of the things that shitty people do is lie. Like for example charismatic leaders of AI “startups” valued in the tens of
billions. But then so do the less-visible, which provoked Kyle Kingsbury A.K.A. Aphyr to write
<a href="https://aphyr.com/posts/405-trudging-through-nonsense">Trudging Through Nonsense</a>. It’s sad and angry but I think
usefully so.</p>
<p>Armin Ronacher is not bursting with rage, but he is skeptical about all the right things in
<a href="https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/">Some Things Just Take Time</a>. Quote:
“There’s a feeling that all the things that create friction in your life should be automated away. That human involvement should
be replaced by AI-based decision-making. Because it is the friction of the process that is the problem. When in fact many times
the friction, or that things just take time, is precisely the point.”</p>
<p>For another cool-voiced critique, here’s Rishi Baldawa:
<a href="https://rishi.baldawa.com/posts/ai-mandates-manufacture-noise/">AI Mandates Manufacture Noise</a>. While I’m not
entirely a burn-it-all-with-fire GenAI foe, the “boss mandate” always struck me as dumb, and Rishi spells it out clearly
and simply. It’s really good, so here are a couple of quotes: “But those not in the weeds had no way to know any of this
because… well they aren’t in the weeds. So they feel compelled to solve their information gap with a policy hammer.” and
“As said before, none of this is revolutionary and that’s sort of the point. AI is a ’mirror and multiplier‘. It intensifies
whatever was already happening.”</p>
<h2 id='p-6'>That’s all</h2>
<p>Let’s really hope the bubble bursts soonest. Because when the money goes away, so will a lot of the shitty people.</p>
</div></content></entry>
<entry>
<title>Nash Burns Saves the Day</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2026/03/20/Nash-Burns#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns</id>
<published>2026-03-20T12:00:00-07:00</published>
<updated>2026-03-20T13:53:25-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Web' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Web' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their emails to us were bouncing. Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on. Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly price, and has been trouble-free</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their
emails to us were bouncing.
Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on.
Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly
price, and has been trouble-free.</p>
<p>So, what could be wrong? We investigated and discovered that Google was offering a new-and-improved MX-record option,
although they emphasized that the old setup should still work. Anyhow, we installed the New Thing and it didn’t help.</p>
<p>So, we filed a ticket with CWH tech support and somebody got back to us pretty quick, saying they’d changed a firewall
setting that was blocking connections to Germany. I detect the scent of GDPR, but whatever. <br/>
Euro-email: Bounce, bounce.</p>
<p>CWH: Probably an MX-record issue, and we should wait for DNS propagation. Several days passed and
bounce, bounce, bounce. <br/>Us: “Not DNS propagation.” <br/>CWH: “Still could be.”</p>
<p>So we VPN’ed to Germany and discovered we couldn’t ping
Textuality’s IP address. Smells like a firewall to me. We told CWH that.</p>
<p>CWH: We have made some changes to firewall settings.
<br/>EMail: bounce, bounce, bounce.
<br/>VPN+Ping: Request timeout, request timeout, request timeout.</p>
<p>CWH: Try traceroute?
<br/>VPN+Traceroute: 14 hops, no joy.</p>
<p>CWH: Your VPN settings must be wrong. Here are instructions to use Windows PC VPN correctly.<br/>
Us: Thanks but no.</p>
<p>CWH: Your MX records are configured incorrectly. <br/>Us: No, they are correct per Google guidance. We sent an email beginning
“Please believe us.”</p>
<p>CWH: It must be DNSSEC. Check to see if your registrar implements DNSSEC. <br/>Us: We are using your DNS servers.</p>
<p>CWH: Perhaps your registrar is broadcasting an old record? <br/>Us: Our registrar doesn’t do DNSSEC.</p>
<p>At this point we consulted a friend who’s an expert on DNS and Email and even DNSSEC. He verified that not only could
you not ping
Textuality from Germany, you also couldn’t ping CWH or its name servers. Firewall firewall firewall!</p>
<p>CWH: “I did test the site access using a 3rd party application, and it seems to be accessible on all parts.” <br/>Us: Look at the
output, it shows we can’t be reached from anywhere in Germany.</p>
<p>Also, for all the remaining messages in the email trail, we prefixed our input with bold face extra-large text reading:
<b>Systems located in Germany cannot ping Textuality.com’s IP address, nor can they ping the IP addresses of textuality.com’s
designated name servers. This is the problem.</b></p>
<p>CWH: Let’s try migrating you to a different server; try pinging these hostnames. <br/>VPN+Ping: Nope.</p>
<p>CWH: Are you sure it’s not your VPN settings? <br/>Us: Are you sure it’s not your GDPR settings?<br/>
CWH: Raising your issue to Tier 3.</p>
<p>20 hours pass, then we get email from:</p>
<h2 id='p-1'>Nash Burns!</h2>
<p>…who said “This has been fixed.” It was.
Nash’s email signature was “Nash(Rajaneesh) B”. What a great name, though. Thanks, Nash.</p>
<h2 id='p-2'>Am we mad?</h2>
<p>Not really. Consumer-facing tech support is hard. None of their suggestions were unreasonable.
Doing GDPR correctly is hard.
They’ve been just fine for years and were having a bad week.
Could we expect better from any of CWH’s local competitors? Probably not.</p>
<p>It wasn’t funny at the time, but looking back, it kind
of is.</p>
</div></content></entry>
<entry>
<title>Pure Sound Please</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2026/03/16/Pure-Sound-Please#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please</id>
<published>2026-03-16T12:00:00-07:00</published>
<updated>2026-03-18T14:34:31-07:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Music' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Music' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>This last weekend we attended a concert entitled <cite>Lenten Reflection</cite> at Vancouver’s Catholic <a href='https://en.wikipedia.org/wiki/Holy_Rosary_Cathedral_(Vancouver)'>Holy Rosary Cathedral</a> featuring the <a href='https://bellevoci.ca'>Belle Voci</a> vocal group and the <a href='https://chilliwacksymphony.com/cantare-super-orchestram/'>Cantare Super Orchestram</a> early-music band. The music was fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below). And so I get to report on good music and yell at production people</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>This last weekend we attended a concert entitled <cite>Lenten Reflection</cite> at Vancouver’s Catholic
<a href="https://en.wikipedia.org/wiki/Holy_Rosary_Cathedral_(Vancouver)">Holy Rosary Cathedral</a> featuring the
<a href="https://bellevoci.ca">Belle Voci</a> vocal group and the
<a href="https://chilliwacksymphony.com/cantare-super-orchestram/">Cantare Super Orchestram</a> early-music band. The music was
fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below).
And so I get to report on good music and yell at production people.</p>
<p>A cathedral is a nice place for a concert!</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_215727574.png" alt="Interior of Vancouver’s Holy Rosary Cathedral" />
<p>The concert opened with just the singers, their voices drifting down from a high place behind us, a balcony or choir loft.
There was no incremental accompaniment and no amplification; the music flowed from vocal cords to
eardrums<span class='dashes'> —</span> not directly, of course, there was lots of reflection and reverberation introduced by the
Cathedral space. The singers were polished and expressive and the sound, drifting through the vast space, beyond exquisite.</p>
<p>They sang a lovely piece by Byrd (1539-1623). Then the instrumentalists played a number by von Biber (1644-1704) while the
singers snuck downstairs. Joined, they performed Bach’s BWV
<a href="https://en.wikipedia.org/wiki/Komm,_Jesu,_komm,_BWV_229">229</a> and
<a href="https://en.wikipedia.org/wiki/Nach_dir,_Herr,_verlanget_mich,_BWV_150">150</a>, then pieces by Pergolesi (1710-1736)
and Steffani (1654-1728).</p>
<p>The Bach pieces, as usual, had more music in the music, but the others were also fun. It was a small ensemble: In
the choir, five sopranos, five altos, a countertenor, four each tenors and basses. The band had five baroque
violins, a baroque viola, a baroque cello, a
<a href="https://en.wikipedia.org/wiki/Violone">violone</a> (think, string bass with frets), a baroque bassoon, and a player
doubling on harpsichord and organ. Thus, an ensemble quite likely not too much bigger or smaller than the ones playing this
music in the 1700s, when it was new.</p>
<h2 id='p-2'>That sound</h2>
<p>Once again, the sound was something special and yeah, the musicians were excellent, but for me, the key thing was the lack of
amplification: vocal cord to eardrum via cathedral. It’s always seemed obvious to me that you can’t run music through a bunch of
electronics and speaker mechanics without changing it; if only spatially, with the sounds coming from speaker diaphragms located
somewhere away from the human musician.
To my ears, there is a fragile magic in pure unamplified sound. I lack the words to describe the difference but it’s not
subtle. </p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_212418188.png" alt="“Lenten Reflections” concert singers and players" />
<p>Does this mean that everything was perfect? No; the choir was a little bit male-heavy; some of the soprano and especially
alto lines were part-hidden behind the massed male voices. Also, the bassoon was right at the front of the stage;
While the playing was fine, it felt as though it were musically, not just physically “in front of” the band and
singers.</p>
<p>Both of these could have been fixed, by telling the men to take it down a notch or having one or two fewer of them. And by
moving the bassoon back to the usual woodwinds spot behind the strings. Still, these were very minor imperfections.</p>
<p>Oh, and the performance and sound of the bass line on that violone was absolutely awesome; clearly audible as a thing on its
own while it wove all the other musical threads together.</p>
<p>I’ve discovered that few classical musicians share my passion for unamplification. I hear things like “I want a
<em>full</em> sound or “The soloists need to cut through the orchestra.” Which, well, OK, but somehow people managed to
accomplish those things for centuries, before amplifiers and speakers were invented.</p>
<h2 id='p-1'>22 months?</h2>
<p>That’s since May of 2024 when I took in the
<a href="/ongoing/When/202x/2024/05/26/TTB">Tedeschi-Trucks Band</a>, whose music couldn’t be more different from anything
called “Lenten Reflections”: electric not acoustic, profane not sacred. But crystal clear and perfectly balanced
sound; so much better than most electric bands achieve.</p>
<p>My sincere thanks to the musicians and their leaders for a lovely experience. And my message to everyone co-ordinating and
leading live music performances: Of course the first priority has to be the quality of the music, but think about the sound and
try to be better. Better than than most performances manage, these days.</p>
<p>We know it’s possible.</p>
</div></content></entry>
<entry>
<title>Because Algospeak</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak' />
<link rel='replies' thr:count='2' type='application/xhtml+xml' href='/ongoing/When/202x/2026/03/05/Because-Algospeak#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak</id>
<published>2026-03-05T12:00:00-08:00</published>
<updated>2026-03-07T10:29:41-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Language' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Language' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Life Online' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Life Online' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Recently I read <a href='https://en.wikipedia.org/wiki/Because_Internet'>Because Internet</a> by <a href='https://gretchenmcculloch.com'>Gretchen McCulloch</a> and <a href='https://en.wikipedia.org/wiki/Algospeak_(book)'>Algospeak</a> by <a href='https://en.wikipedia.org/wiki/Adam_Aleksic'>Adam Aleksic</a>. The language we speak (and text) to each other is at the core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth. So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Recently I read
<a href="https://en.wikipedia.org/wiki/Because_Internet">Because Internet</a> by
<a href="https://gretchenmcculloch.com">Gretchen McCulloch</a> and
<a href="https://en.wikipedia.org/wiki/Algospeak_(book)">Algospeak</a> by
<a href="https://en.wikipedia.org/wiki/Adam_Aleksic">Adam Aleksic</a>. The language we speak (and text) to each other is at the
core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth.
So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/covers.png" alt="The covers of “Because Internet” and “Algospeak”" />
<h2 id='p-1'>Because Internet (2019)</h2>
<p>Its approach is historical and its voice fairly uninflected. It smiles and
argues, but it doesn’t ROFL nor does it YELL AT YOU. The history is longer, perhaps, than most people reading this have
been online (or even alive). Ms McCulloch goes back to the days of BBSes (“bulletin-board systems”) and ListServs and IRC. Some of
the jargon and formulations of those days live on; you’d be surprised.</p>
<p>Here’s her table of contents.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/BI-toc.png" alt="Table of Contents from “Because Internet”" />
<p>The analysis is grounded in the formalisms of the author’s profession, academic linguistics. Nothing wrong with that.</p>
<p>Let’s look at a couple of her ideas, beginning with Chapter 1’s “Informal Writing”. A few of us, back in the late
Eighties, noticed that computers in general and the then-nascent Internet in particular were driving a writing
renaissance.</p>
<p>Before computers, a knowledge worker who had laboriously constructed essays in college quite likely wrote
almost nothing for the rest of their working life. People talked face-to-face or on the phone, and dictated to
secretaries. Written communication was seen as necessarily formal and disjoint from the way we spoke, or that we wrote in
personal correspondence. Then, suddenly, everyone was sitting at a keyboard only seconds away from everyone else’s screen.
McCulloch goes deep on this:</p>
<blockquote><p>In the future, the era of writing between the invention of the printing press and the internet may come to be
seen as an anomaly—an era when there arose a significant gap between how easy it was to be a writer versus a reader. An era when
we collectively stopped paying attention to the informal, unedited side of writing and let typography become static and
disembodied.</p>
<p>The internet didn’t create informal writing, but it did make it more common, changing some of our previously spoken
interactions into near-real-time text exchanges.</p></blockquote>
<p>From which all of this follows. It feels like a central insight. I suppose you could argue that centrality of informal text
is fading in the face of short-form video. Maybe,
it’s too soon to tell.</p>
<p>Then consider chapter 5, about emojis. Linguists obviously need to think about them because now they’re an
integral part of written language. McCulloch’s insight is that they correspond almost exactly to gestures, the way we use
our hands to add force to our speech. Obviously, for example, “👍”. Or when you’re talking about something completely
loopy and you twirl your index finger by your ear? You meant “🤪”.</p>
<p>I offer the emoji story for flavor, an example of a linguist’s approach to what we’re doing to our language with our
networks.</p> <p>McCulloch has lots more of this stuff.
I enjoyed <cite>Because Internet</cite> a lot, partly because I’m old and my memories stretch back to those BBS and
IRC days and I had a front-row seat for the decades of linguistic seething and heaving. And also because I’m a
<a href="https://www.rfc-editor.org/rfc/rfc9839.html">Unicode geek</a>.</p>
<h2 id='p-2'>Algospeak (2025)</h2>
<p>The subtitle is “How Social Media Is Transforming the Future of Language”. OK, but…
Social media is a fertile field for language evolution. Thing is, corporate social media discourse
lives in the dire grip of the proprietors’ algorithms. And that’s where Adam Aleksic focuses. He treats all of them
as a single opaque object, “The Algorithm”, which I think is fair because they all are designed with one goal: To
maximize the effectiveness of human conversation at generating advertising revenue.</p>
<p>First, the Table of Contents.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/03/05/AS-toc.png" alt="Table of Contents from “Algospeak" />
<p>Aleksic knows whereof he speaks: As “Etymology Nerd”, his aggregate following across TikTok, Instagram, and YouTube is
over three million. He’s all about cool bits and pieces of
linguistics, often Internet-specific usages.
If I had the patience for podcasts I suppose his would be near the top of my list.</p>
<p>He really enjoys his work and has fun talking about some of Social Media’s more colorful linguistic extrusions; check
that Table of Contents. I’m kind of old and I learned a lot about the words and emojis younger folk emit, and I think most folks,
even those just out of their teens, would too. I’m on a Discord for a
<a href="/ongoing/What/Sports/Soccer/">Major League Soccer</a> team’s fans, and while it’s totally all-ages, I can say I am regularly
less mystified than I was before I read <cite>Algospeak</cite>.
For example, now I know what it means when someone tosses “💀” into a chat. Do you?</p>
<p>Aleksic isn’t averse to a little history himself. Looking back over the successive online-jargon volcanoes, he argues
convincingly that two stand out as extra productive. First of all, the short-lived (but hot stuff at the time)
<a href="https://en.wikipedia.org/wiki/Vine_(service)">Vine</a> video platform. Second, the incel cesspool; sad but
(apparently) true.</p>
<h2 id='p-3'>The Algorithm</h2>
<p>Remember, it’s all about what advertisers want. And wow, do they ever want a lot of things. I’ll just touch on a few of
Aleksic’s points.</p>
<p>First of all, they don’t want to find themselves next to downers. So if you want to talk about death or suicide or rape or
racism or rage,
you need to fool The Algorithm. Thus “unalive” and many other dodges. Of course, The Algorithm learns about them so you
have to keep dodging. Neither side of this struggle can stay ahead for long.</p>
<p>Here’s another thing I didn’t know: Apparently written Chinese is particularly rich in techniques for euphemizing, making it
easier for users of that language to evade, for a time, The Algorithm.</p>
<h2 id='p-4'>Partitioning people</h2>
<p>Another big thing The Algorithm likes is grouping people into smaller and smaller baskets based on interests, generations,
and many other criteria. This is because advertisers can aim very specific campaigns at just exactly the right cohort of people who
are likely to buy what they’re selling. Here’s a quote; See how the language fills in behind advertisers’ pressure?</p>
<blockquote><p>It doesn’t matter how much I label myself. If I’m a demisexual goblincore Gen
Z Swiftie, I guarantee there are still others like me. The only thing these labels really change about me is that they make me
easier to classify and market to. Ironically, true individuality may come out of a <em>lack</em> of labels and stories, because
there’s greater freedom of expression with a blank slate. If everybody’s the “main character,” then nobody is.</p></blockquote>
<p><cite>Algospeak</cite>, unlike <cite>Because Internet</cite>, doesn’t limit itself to written language. One of its most
compelling studies concerns the vocal techniques of podcasters and YouTubers. The finding is simple: It’s hard to build and hold an
audience for your show unless you sound like MrBeast. No, really.</p>
<p>Anyhow, they’re both good books. <cite>Because Internet</cite> educated and entertained me. <cite>Algospeak</cite> is way
more intense, intentionally more like the subject it addresses. Also it made me angry. I am a lover of human language and of its
patterns of growth and mutation and simplification and complexification. Linguistics is one of the disciplines I regret not
having chosen.</p>
<p>Aleksic makes it clear that there’s an amusing narrative about how the people living and speaking in the shade of the Algorithm
can never defeat it, but they can still manage to get their messages across. But they shouldn’t have to struggle!</p>
<p>In fact, a few million of us have found a place to talk to each other that isn’t in The
Algorithm’s shadow: Decentralized social media. Specifically the Fediverse (what people mean when they say “Mastodon”) and maybe
the ATmosphere (same for “Bluesky”).</p>
<p>I want to see how language grows in a place where new forms arrive when they’re needed, to say new things that need to be
said. Not to either serve or resist The Algorithm.</p>
</div></content></entry>
<entry>
<title>Kansas and AI</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI' />
<link rel='replies' thr:count='2' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/27/Kansas-and-GenAI#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI</id>
<published>2026-02-27T12:00:00-08:00</published>
<updated>2026-02-27T16:06:19-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud. Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural changes.” Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud.
Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural
changes.”
Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010.</p>
<h2 id='p-1'>The Kansas Experiment</h2>
<p>As long as I can remember, a certain class of right-wing evangelists has preached that cutting taxes would stimulate business
growth and everyone would come out ahead. There are a couple of problems with this theory. First, mainstream economists
almost universally think it’s just wrong. Second, most of the people pushing it are rich and would
benefit from the cuts.</p>
<p>Anyhow, in 2010 US Senator Sam Brownback won the race for governor of Kansas on what was then called the “Tea Party” program:
Prosperity through tax cuts. Tea-party Republicans also won a large majority in the state legislature. Unsurprisingly they
immediately
<a href="https://en.wikipedia.org/wiki/Kansas_experiment">did what they said they were going to do</a>: Slashed a wide variety
of taxes, some to zero.</p>
<p>The predicted prosperity failed to happen. The state government’s revenue plunged and it had to dig deep into rainy-day
reserves just to keep the doors open. There were brutal cuts to policing, road repair, and schools. Also a nasty
feedback loop: As the state’s fiscal position worsened, its credit rating fell and interest rates rose, leading to yet more
brutal austerity measures.</p>
<p>Another result was that affluent Kansans made out like bandits; the cost of running the state was substantially
transferred to the less financially fortunate.</p>
<p>In 2017, the legislature threw in their cards and repealed the tax cuts, overriding Brownback’s veto.</p>
<p>While this was a terrible experience for most Kansans, it is historically useful, because whenever you encounter a
tax-cut nut (probably self-interestedly wealthy) you can say “But, Kansas!” Having said that, there are still plenty of
those nuts, and they’ll tell you that the Kansas experiment failed because of one fine-tuning effort or another. That’s a position
that’s hard to defend, though.</p>
<h2 id='p-3'>Sidebar: Trans oppression too</h2>
<blockquote><p>Before I move onto the AI angle, I gotta pause to acknowledge this week’s news story about the Kansas
government’s vicious, brutal, and ignorant
<a href="https://www.theguardian.com/us-news/2026/feb/26/kansas-trans-drivers-license-law-assault-on-rights">assault on trans
people</a>. To be clear, I think the shitty people who hate trans folk are aren’t necessarily the same shitty people as the shitty
people who don’t want to contribute to the public good. But, something about Kansas seems to attract both
flavors.</p></blockquote>
<h2 id='p-2'>The GenAI experiment</h2>
<p>The core value proposition of contemporary AI technology is exactly what Dorsey seems to think: Fire half your
employees and profits will soar! If that’s true, the trillion dollars or so invested so far will seem like small potatoes. Since
we don’t know if
this will actually work, anyone who actually does it is conducting an experiment. Just like Sam Brownback did.
Unsurprisingly, the investor class loves this experiment and is putting their money on it working.</p>
<p>To be fair, voices have been raised to argue that the tech sector is a special case: That following on
feverish over-hiring during the Covid lockdown, they need to slash headcount anyhow, and are using AI as an excuse.
For example
<a href="https://daringfireball.net/linked/2026/02/27/block-layoffs">John Gruber</a>.</p>
<p>I personally
am unconvinced, but even if they’re right, it’s irrelevant. The shareholding class won’t be able to see past that 24% payoff. So
as of today, they’ll be yelling at every CEO on the planet to start pulling the mass-firing trigger. Or else.</p>
<p>I think I know how the experiment will turn out. Just like in Kansas, it’s not going to be fun.</p>
</div></content></entry>
<entry>
<title>Crocuses of 2026</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/24/Crocuses-of-2026#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026</id>
<published>2026-02-24T12:00:00-08:00</published>
<updated>2026-02-26T13:46:17-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth in early 2003. Except for last year. Because <a href='/ongoing/When/202x/2025/02/28/Moved'>we moved</a> and the new place didn’t have any. Only now it does, and they’re (just barely) up. <i>[Update: Up and open, too.]</i></div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth
in early 2003. Except for last year. Because
<a href="/ongoing/When/202x/2025/02/28/Moved">we moved</a> and the new place didn’t have any. Only now it does, and they’re
(just barely) up. <i>[Update: Up and open, too.]</i></p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56234.png" alt="Crocuses of February 2026" />
<p>Long-time followers may note that they’re pale and fragile compared to the exuberant blossoms of previous
years. Not sure why, but our new place faces north and there’s this enormous
<a href="https://en.wikipedia.org/wiki/Fraxinus_americana">White Ash</a> tree right in front of it, so they’re not getting as
much sun as at the south-facing former joint.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56235.png" alt="Crocuses of February 2026" />
<p>And also this is their first spring. We bought the bulbs and hired a professional with the right tools to jam them
into the earth last autumn, between the big tree’s roots. So they really haven’t had a chance to get their own root systems going.</p>
<p>And finally, it really is the first day that’s bright and warm enough to get out the camera. Maybe they’ll
be better in another few days. And quite likely next Spring.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56244.png" alt="Crocuses of February 2026" />
<p>This would be the place to introduce whatever metaphor this year’s blossoms, fighting their way through the leaf cover in
chilly air toward the sun, fit into, but I’m not gonna.</p>
<p>I, like many, am
<a href="/ongoing/When/202x/2023/10/25/Wild-World">not dealing very well</a> with what I see when I look at the world in either
the big or the ultra-local landscapes.
The world in tough shape and its worst people are making it worse.
People I love are in ugly corners and not finding help.</p>
<p>But you know, the flowers, in their low-key way, look great and so does the tree, still in wintersleep. Today the
sun was shining on them. It’ll be warmer and nicer soon.</p>
<p>Metaphors can go to hell. It’s just late-winter light on pale violet petals. Enjoy the moments you have with it.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56249.png" alt="Spring crocus, now open for business" />
<div class='caption'><p>Update: Now open for business.</p></div>
</div></content></entry>
<entry>
<title>Open Source and GenAI?</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion' />
<link rel='replies' thr:count='2' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion</id>
<published>2026-02-16T12:00:00-08:00</published>
<updated>2026-02-18T13:41:14-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I’ve been puttering away on my <a href='/ongoing/What/Technology/Quamina%20Diary/'>Quamina</a> project since 2023. In the last few weeks GenAI has intervened. <a href='/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1'>Quamina + Claude, Case 1</a> describes a series of Claude-generated human-curated PRs, most of which I’ve now approved and merged. <a href='/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2'>Quamina + Claude, Case 2</a> considers <a href='https://github.com/baldawarishi/quamina-rs'>quamina-rs</a>, a largely-Claude-driven port from Go to Rust. Both of these stories seem to have happy endings and negligible downsides. So empirically, I <em>can</em> apply LLM technology usefully to software development. But should I?</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>I’ve been puttering away on my
<a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a> project since 2023. In the last few weeks GenAI
has intervened.
<a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Quamina + Claude, Case 1</a> describes a series of
Claude-generated human-curated PRs, most of which I’ve now approved and merged.
<a href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2">Quamina + Claude, Case 2</a> considers
<a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>, a largely-Claude-driven port from Go to Rust.
Both of these stories seem to have happy endings and negligible downsides. So empirically, I <em>can</em> apply LLM
technology usefully to software development. But should I?</p>
<h2 id='p-3'>Conclusions 1: Burn it with fire?</h2>
<p>Let me be clear: In the big GenAI picture, I’m a contra. Why? I’ll pass the mike to Baldur Bjarnason, my
favorite among GenAI’s blood enemies.:
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">“AI” is a dick move</a>.
His tl;dr is something like “GenAI is environmentally devastating and has the goal of throwing millions of
knowledge workers onto the street and is being sold by the worst people and is used for horrible applications and will increase
society’s already-intolerable level of inequality!” To which I reply “Yes, yes, yes, yes, and yes.”</p>
<p>At the end of the day, the business goal of GenAI is to boost monopolist profits by eliminating decent jobs, and
damn the consequences. This is a horrifying prospect (although I’m somewhat comforted by my belief that it basically won’t
work and most of the investment capital is heading straight down the toilet).</p>
<p>But. All that granted, there’s a plausible case, specifically in software development, for exempting LLMs from this
loathing.</p>
<p>First of all, size.
<a href="https://www.jetbrains.com/lp/devecosystem-data-playground/#global_population">JetBrains thinks</a> that
the world has 21 million or so software developers, i.e. less than 1% of the earth’s working population.
Vanishingly small in the context of the lunatic tsumani of LLM overinvestment.
Training and operating the models required for a market this small is
rounding error measured on the Great GenAI Overbuild scale. There aren’t enough geeks to create a detectable bump in the global
carbon load.</p>
<p>Another odious aspect of LLMs is
<a href="https://en.wikipedia.org/wiki/Reinforcement_learning_from_human_feedback">RLHF</a>, “Reinforcement Learning From Human
Feedback”, which relies on underpaying Third-Worlders to
polish the models’ outputs.
My guess is that much less is required for code-oriented LLMs.
The combination of the compiler and your unit tests provide good starter guardrails. Then skilled
professional intervention is required to deal with the remaining misfires, as with those Quamina PRs.</p>
<p>Finally, it seems making billionaires into multibillionaires is intrinsic to GenAI dreams. But software-development tools won’t
do that. Once again, the market is just too small. But even if it weren’t, consider this from Steve Yegge:</p>
<blockquote><p>For
<a href="https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163">this blog post</a>, “Claude Code” means “Claude Code and
all its identical-looking competitors”, i.e. Codex,
Gemini CLI, Amp, Amazon Q-developer ClI, blah blah, because that’s what they are. Clones.</p></blockquote>
<p>(GenAI, overbuilding wherever you look.) None of these products have moats and the chance that any of them become
extractive monopolies is about zilch. Nobody’s ever built a major cash-cow on developer tooling</p>
<p>One reason is (*gasp*) Open Source. Does anybody doubt that in the near future, there will
be entirely open-source versions of what Yegge means by “Claude”?</p>
<p>So, if you want to condemn the use of GenAI in software development, I think you need arguments other than the fact that
it’s also being promoted for societally-toxic business purposes.</p>
<p>I have a few. But stand by, let me push that on the stack and turn to
technology for a bit.</p>
<h2 id='p-4'>Conclusions 2: Engineering sanity?</h2>
<p>Question: Can LLMs even participate in quality software engineering?
Baldur doesn’t think so: “The gigantic, impossible to review, pull requests. Commits that are
all over the place. Tests that don’t test anything. Dependencies that import literal malware. Undergraduate-level security
issues. Incredibly verbose documentation completely disconnected from reality.”</p>
<p>I’m not saying that these pathologies can’t or don’t happen. But in my personal experience with Quamina, they
didn’t. (Mind you, it’s a hobby project.)</p>
<p>And when they do happen, I would assume that mature open-source projects will use a network of
trust, as big operations like Linux already do. PRs that don’t have the imprimatur of someone known to be clueful will be ignored.
When I saw the first of those incoming Quamina PRs, I took the time for a serious look because I knew Rob and had seen evidence that he
was technically competent. If I see an incoming PR that’s nontrivial and from some rando and doesn’t pass a 120-second sanity
check, it’s unlikely to get any more attention.</p>
<p>In fact, some essentials don’t change. If you’re not requiring that PRs be clean and
test coverage be good and code reviews not be skipped and dependencies be curated, you’re going to get a lousy result whether
the upstream code is coming from a human or an LLM.</p>
<p>But it’d be naive to think that a big change in the
shape of that upstream isn’t going to affect the profession.</p>
<h2 id='p-9'>Bottlenecks</h2>
<p>Speaking from personal experience, reviewing the PRs from Claude&Rob was neither faster nor slower, easier nor harder,
than what I’m used to pre-GenAI. The number of my disagreements with the diffs, and the amount of arguing it took to resolve
them, was also about as usual.
Which creates a big problem. Because if we can generate code a whole lot faster but review doesn’t
speed up, all we’ve done is moved the bottleneck in the system.</p>
<p>Speaking of which, Armin Ronacher offers
<a href="https://lucumr.pocoo.org/2026/2/13/the-final-bottleneck/">The Final Bottleneck</a>, from which: “When one part of the
pipeline becomes dramatically faster, you need to throttle input.” Think about that.</p>
<h2 id='p-10'>Burnout</h2>
<p>Meanwhile, evidence is piling up that LLM-based software development is driving
developers to overwork and burnout. Here’s
<a href="https://hbr.org/2026/02/ai-doesnt-reduce-work-it-intensifies-it">a cool-eyed take</a> from <cite>Harvard Business
Review</cite>. Then there’s Steve Yegge’s frantic, overly-long
<a href="https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163">The AI Vampire</a>. But my favorite, and I think a
must-read, is Siddhant Khare’s
<a href="https://siddhantkhare.com/writing/ai-fatigue-is-real">AI fatigue is real and nobody talks about it</a>.
From which: “AI reduces the cost of production but increases the cost of coordination, review, and decision-making. And those
costs fall entirely on the human.”</p>
<p>The argument we’re hearing is that GenAI makes development more efficient. And more efficient is better.
<a href="https://www.tbray.org/ongoing/When/202x/2020/07/05/Too-Efficient">Until it’s not</a>.</p>
<p>I’m not sure the profession I joined last century would attract me today. And on Mastodon,
<a href="https://cosocial.ca/@gordwait/116082229876399512">@GordWait said</a> “At our office, we are
noticing a huge drop in Comp Sci co-op applications. The next generation is convinced there’s no future in programming thanks to
AI hype.”</p>
<h2 id='p-11'>Can and should</h2>
<p>Here’s another conundrum. Suppose we <em>can</em> build a whole lot more stuff, faster. <em>Should</em> we? I don’t know about you,
but I am regularly enraged at tools that work just fine popping up “wonderful new features” modals in front of what I’m
trying to get accomplished. Also at damaging UI churn, driven by product managers trying to get promoted. It’s
just not obvious
that speeding up software development is, in the big picture, a good thing.</p>
<p>And I can’t help noting that every attempt to measure the productivity boost due to GenAI has shown zero (or worse)
improvement. Of course, Claude’s cheering section will point out that those studies date to 2024 which is the stone age. Maybe
they’re right.</p>
<h2 id='p-8'>Vampires</h2>
<p>(In which I once again go all
<a href="/ongoing/When/202x/2023/01/16/Class-Reductionism">class-reductionist</a>.) The real problem here is late-stage
capitalism, and I think is best addressed in Yegge’s <cite>AI Vampires</cite> piece, from which I quote:
“…dollar-signs appear in their <i>[employers’]</i> eyeballs, like cartoon bosses. I know that look. There’s no reasoning with
the dollar-eyeball stare.” Yeah.</p>
<p>Thus the ancient question: <i>cui bono?</i> Assuming GenAI genuinely boosts productivity, who gets the
benefits? Because the ownership class sure doesn’t think they should go to their newly-more-efficient employees.</p>
<h2 id='p-7'>But, what do I know?</h2>
<p>I know that you gotta have test coverage or your software is an unmaintainable tangle of festering tech debt. I know you gotta
have code review or your quality is on inexorable downhill drift. I <em>don’t</em> know how to build LLMs into a sane,
sustainable software engineering culture. Nor what to do
about capitalism’s AI Vampires.</p>
<p>And I absolutely do <em>not</em> believe the wild-eyed claims of 10× productivity gains, assuming we demand (as we should) that
they’re sustainable at scale.</p>
<p>So, would I advise executives to tell software engineering shops to discard their
culture in favor of vibe coding in the expectation of monstrous productivity wins? Nope.
<a href="https://simonwillison.net/2025/Oct/7/vibe-engineering/">Vibe engineering</a>, maybe.
<a href="https://locusmag.com/feature/commentary-cory-doctorow-reverse-centaurs/">Centaurs, not reverse centaurs</a>? Indeed.</p>
<p>But would I say “Stay away, don’t even look”? Nope. I’d probably suggest pointing the LLM at well-delimited non-strategic
issues and
optimizations, and emphasize no shortcuts on reviewing or CI/CD standards.</p>
<p>Also note that the GenAI apostles are at one in saying that this year’s tools are <em>so</em> much better than last year’s,
and next year’s are guaranteed to be qualitatively still better! So why would you rush in and risk getting locked into
soon-to-be-outmoded tooling?</p>
<p>Rob Sayre wrote “I would never bother to type out these patches by hand. But I read them all.” I probably wouldn’t have
either and I read them too. And now Quamina is roughly twice as fast. Which is to say, I got good results on a hobby
project. That’s not nothing.</p>
<p>But, also not conclusive.
Once the AI bubble pops and we’ve recovered from the systemic damage, I think there’ll <em>probably</em> be a place for
open-source LLM automation in developer toolkits.</p>
<p>But maybe not. Wouldn’t surprise me much, either way.</p>
</div></content></entry>
<entry>
<title>Quamina + Claude, Case 2</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2</id>
<published>2026-02-14T12:00:00-08:00</published>
<updated>2026-02-14T12:00:00-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'><a href='/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1'>Last time out</a> I described a bunch of incremental-improvement <a href='/ongoing/What/Technology/Quamina%20Diary/'>Quamina</a> PRs from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s <a href='https://github.com/baldawarishi/quamina-rs'>quamina-rs</a>, a Claude-based port of Quamina from Go to Rust. The next post is about where I stand on GenAI and code</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p><a href="/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1">Last time out</a> I described a bunch of incremental-improvement
<a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a> PRs
from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s
<a href="https://github.com/baldawarishi/quamina-rs">quamina-rs</a>, a Claude-based port of Quamina from Go to Rust.
The next post is about where I stand on GenAI and code.</p>
<p>Anybody who cares about this kind of thing will appreciate Rishi’s write-ups, starting with
<a href="https://rishi.baldawa.com/posts/the-agents-kept-going/">The Agents Kept Going</a> (also see
<a href="https://rishi.baldawa.com/posts/scaffolding-for-agent-velocity/">Scaffolding for Agent Velocity</a>).
He doesn’t just say what he did, he draws lessons; good ones, I think.</p>
<h2 id='p-1'>Background</h2>
<p>Rishi and I worked together at AWS, can’t remember the details, but after I left he took over what we called Ruler, now known
as <a href="https://github.com/aws/event-ruler">aws/event-ruler</a>, Quamina’s ancestor. At the time I left it had been adopted
by quite a number of AWS and Amazon services and various instances were processing, in aggregate, a remarkable number of
millions of events per second. So he knows the territory.</p>
<p>As for quamina-rs, go read his blogs. I’ve got little to add, but here are a couple of juicy quotes: “…at some point while I was
mindlessly kicking off these sessions, the agents started picking up open issues from the Go version and implementing them on
their own.“ Also, “And I think that’s the thing worth saying plainly. It’s human to care. Agents don’t care. Automation doesn’t
care. They need to be told what to care about, and even then they’ll misbehave the moment you look away…”</p>
<p>Both these stories ended with useful results.
So empirically, you can get useful results by applying GenAI to the process of code construction.</p>
<p>Yay. I guess. But there are a lot of smart people who think this whole LLM-fueled coding direction is irremediably toxic.
<a href="/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion">I’m not sure they’re wrong</a>.</p>
</div></content></entry>
<entry>
<title>Quamina + Claude, Case 1</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1</id>
<published>2026-02-06T12:00:00-08:00</published>
<updated>2026-02-06T12:00:00-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any) GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current code playground, <a href='/ongoing/What/Technology/Quamina%20Diary/'>Quamina</a>. Here’s the first story. I’m going to go ahead and share it even though it will make people mad at me</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any)
GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and
try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current
code playground, <a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a>. Here’s the first story. I’m going to go
ahead and share it even though it will make people mad at me.</p>
<h2 id='p-1'>Why share?</h2>
<p>Because our profession’s debate on this topic is simultaneously ridiculous and toxic. No meaningful dialogue seems possible
between the
<a href="https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04">Gas Town</a>-and-<a href="https://en.wikipedia.org/wiki/Moltbook">Moltbook</a>
faction and the
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">“AI” is a dick move</a> camp.
So, I’m not going to join in today. This is pure anecdata: What happened when Rob applied Claude to Quamina. I’m going to
avoid rhetoric (in the linguistic sense, language designed to convince) and especially polemic (language designed to
attack). I promise to have conclusions before too long, just not today.</p>
<h2 id='p-2'>What happened was…</h2>
<p>There’s this guy
<a href="https://github.com/sayrer">Rob Sayre</a>, I’ve known him for many years, even been in the same room once or twice,
in the context of IETF work. I’ve never previously collaborated on code with him. Starting in
mid-January, he’s sent
<a href="https://github.com/timbray/quamina/issues?q=is%3Apr%20author%3Asayrer">a steady flow of PRs</a>, most of which I
eventually accept and merge.</p>
<p>The net result is that Quamina is now roughly twice as fast on several benchmarks designed to measure typical tasks.</p>
<h2 id='p-3'>Technical details</h2>
<p>The details of what Quamina is and does are in the
<a href="https://github.com/timbray/quamina?tab=readme-ov-file#quamina">README</a>. For this discussion, let’s ignore everything
except to say that it’s a Go library and consider its two most important APIs. <code>AddPattern()</code> adds a Pattern (literal or
regexp) to an instance, and
<code>MatchesForEvent</code> considers a JSON blob and reports back which Patterns it matched. It’s really fast and the
relationship is pleasingly weak between the number of Patterns that have been added and the matching speed.</p>
<p>Quamina is based around finite automata (both deterministic and nondeterministic) and the rest of this technical-details
section will throw around NFA and DFA jargon, sorry about that.</p>
<p>For code like this that is neither I/O-bound nor UI-centric, performance is really all about choosing the right
algorithms. Once you’ve done that, it’s mostly about memory management. Obviously in Quamina, the <code>AddPattern</code> call
needs to allocate memory to hold the finite automata. But I’d like it if the <code>MatchesForEvent</code> didn’t.</p>
<p>Go’s only built-in data structures are “map” i.e. hash table, and “slice” i.e. appendable array. (For refugees from Java, with
its dozens of flavors of lists and hashes, this is initially shocking, but most Go fans come to the conclusion that Go is right
and Java is wrong.)
In really well-optimized
code, you’d like to see all the time spent either in your own logic or in appending to slices and updating maps.</p>
<p>In less-well-optimized code, the profiler will show you spending horrifying amounts of time in runtime routines whose names
include “malloc”, and in the garbage collector.
Now, both maps and slices grow automatically as needed, which is nice, except when you’re trying to minimize allocation.
It turns out that slices have a <b>capacity</b>, and as long as the number of things you append is less than the capacity, you won’t
allocate, which is good. Thus, there are two standard tricks in the inventory of 100% of people who’ve optimized Go code:</p>
<ol>
<li><p>When you make a new slice, give it enough capacity to hold everything you’re going to be adding to it. Yes, this can
be hard because you’re probably using it to store input data of unpredictable size, thus…</p></li>
<li><p>After you’ve made a new slice, keep it around, clear it after each input record, and its capacity will naturally grow
until it gets to be big enough that it fits all the rest of the records, then you’ll never allocate again.</p></li>
</ol>
<h2 id='p-4'>Those PRs</h2>
<p>Background: Quamina is equipped with what I think is a pretty good unit-test suite, and multiple benchmarks.</p>
<p>I started getting Rob’s PRs and initially, 100% of them were finding ways along both of those well-trodden map-and-slice
paths, in places where I hadn’t noticed the opportunity. They were decent PRs, well-commented, sensible code, no loss of test
coverage. After I asked to see benchmark runs to prove the gains weren’t just theoretical, they started including benchmark runs. I’ve
found a few things to push back on but Rob and I had no problem sorting those out.</p>
<p>At the end of the day I had no qualms about merging them, but I did find myself wondering how they were built. So I
asked.</p>
<h2 id='p-6'>Workflow</h2>
<p>Rob had told me right away on the first one that these were substantially Claude-generated. I asked him for his workflow and part
of what he said was “I might say
‘let's do some profiles of memory and CPU on this benchmark, on main and on this branch.’ It will come up with good and bad
ideas, then I pick them.”</p>
<p>Also: “What might be counter-intuitive is that I can context switch really quickly with it. So, you leave a comment, and I
just tell Claude to fix that, because you are correct. Sometimes I go in and hand edit, but usually it gets close or perfect
(what they call a "one-shot"). But I just have the conversation open, so I just pick up where we left off.”</p>
<p>Here’s a sample of Claude talking to Rob. You may have to enlarge it.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2026/02/06/claude-says.png" alt="Dialogue with Claude" />
<h2 id='p-7'>Not just the same-old</h2>
<p>Then I got a surprise, because Claude and Rob spotted two pretty big improvements that aren’t on the standard list.
First: To traverse an NFA, for each state you have to compute its “epsilon closure”, the set of other states you can get to
transitively following epsilon transitions. I had already built a cache so that as you computed them, they got remembered.
C&R pointed out “Epsilon closures are a property of the automaton structure, not the input data. Once a pattern is added and the
NFA is built, the epsilon closure for any given state is fixed and never changes.” So you might as well compute it and save it
when you build the NFA.</p>
<p>This is even better than it sounds, because (for good reasons following from Quamina’s concurrency model) my closure
caches were per-thread, while the new epsilon closures were global, stored just once for all the threads. Not bad, and not trivial.</p>
<p>Second, when you’re computing those closures, you have to memo-ize the key functions to avoid getting caught in NFA loops.
I’d done this with a set, which in Go you implement as <code>map[whatever]bool</code>. R&C figured out that if you gave each
state a “closure generation” integer field and maintained a global closure-generation value, you could dodge the necessity for the
set at the cost of one integer per state. The benchmarks proved it worked.</p>
<p>As I wrote this piece,
<a href="https://github.com/timbray/quamina/pull/491">another PR arrived</a> with a stimulating title: “kaizen: allocation-free
on the matching path”.</p>
<h2 id='p-5'>Kaizen?</h2>
<p>It’s
<a href="https://en.wikipedia.org/wiki/Kaizen">the idea that</a> you make things substantially better by successively introducing
small improvements. We try to
use the term to tag Quamina PRs that change no semantics but just make performance better or more reliable or whatever.</p>
<h2 id='p-8'>But GenAI is bad!?!</h2>
<p>Yes, so they say. Go re-read that
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">dick-move</a> polemic.</p>
<p>But, I’m going to leave this little case study conclusion-free for a bit because there are two follow-up pieces.
Next,
<a href="/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2">the story of quamina-rs</a>, a Claude-drive port of Quamina to Rust.
Finally, <a href="/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion">Open Source and GenAI?</a>.</p>
<!--
<p>You say “But GenAI is environmentally devastating and has the goal of throwing millions of knowledge workers onto the street
and is being sold by the worst people and used for horrible applications and will increase society’s already-intolerable level
of inequality!” And I
reply “Yes, yes, yes, yes, and yes.” But I’m talking about the software sector here.
<a href="https://www.jetbrains.com/lp/devecosystem-data-playground/#global_population">JetBrains thinks</a> that the world has
21 million or so software developers. The notion that this is a market that could justify the lunatic wave of investment thrown
at GenAI is laughable. Training and operating the models required to support things like Claude will be rounding error in the
scale of the Great GenAI Overbuild. The world can afford it.</p>
<h2 id='p-9'>A prediction</h2>
<p>Let me quote Yegge:</p>
<blockquote><p>For this blog post, “Claude Code” means “Claude Code and all its identical-looking competitors”, i.e. Codex,
Gemini CLI, Amp, Amazon Q-developer ClI, blah blah, because that’s what they are. Clones.</p></blockquote>
<p>GenAI, overbuilding wherever you look. But anyhow, none of these products have moats and the chance that any of them become
dominant enough to serve as the basis for an extractive monopoly rounds to zero. Nobody’s ever built a huge cash-cow company
bsaed on selling tools to developers. One reason is (*gasp*) Open Source. Does anybody doubt that in the near future, there will
be entirely open-source versions of what Yegge means by “Claude”?</p>
-->
</div></content></entry>
<entry>
<title>Long Links</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links' />
<link rel='replies' thr:count='0' type='application/xhtml+xml' href='/ongoing/When/202x/2026/02/03/Long-Links#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links</id>
<published>2026-02-03T12:00:00-08:00</published>
<updated>2026-02-04T14:41:25-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
<category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Welcome to the first <cite>Long Links</cite> of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to take in all of these, but there’s a good chance one or two might brighten your day</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Welcome to the first <cite>Long Links</cite> of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to
take in all of these, but there’s a good chance one or two might brighten your day.</p>
<h2 id='p-17'>Unclassified</h2>
<p>Thomas Piketty is always right. For example,
<a href="https://thomaspiketty.wordpress.com/2026/02/03/europe-a-social-democratic-power/">Europe, a social-democratic
power</a>.</p>
<p>Lying is wrong. Conservatives
<a href="https://thetyee.ca/Opinion/2026/02/02/Today-Conservatives-Misinformation-Norm/">do it all the time</a>. To be fair,
that piece is about the capital-C flavor, as in the Canadian Tories. But still.</p>
<p>Clothing is open-source: “If you slice the different parts off with a seamripper, lay them all down, trace them on new
fabric, cut them out, and stitch them back together, you can effectively clone and fork
garments.” From
<a href="https://wiki.xxiivv.com/site/devine_lu_linvega.html">Devine Lu Linvega</a>.</p>
<p>The Universe is weird. The Webb telescope keeps showing astronomers things that shouldn’t be there. For example,
<a href="https://www.nature.com/articles/s41586-025-09973-1">An X-ray-emitting protocluster at z ≈ 5.7 reveals rapid structure
growth</a>; ignore the title and read the Abstract and Main sections. With pretty pictures!</p>
<h2 id='p-2'>Music</h2>
<p>One time in Vegas, I was giving a speech, something about cloud computing, and was surprised to find the venue an ornate
velvet-lined theater. I found out from the staff, and then relayed to the audience, that the last human before me to stand on this stage
in front of an audience had been Willie Nelson. I was tempted to fall to my knees and kiss the boards.
<a href="https://www.newyorker.com/magazine/2025/12/29/willie-nelson-profile">How Willie Nelson Sees America</a>, from <cite>The
New Yorker</cite>, is subtitled “On the road with the musician, his band, and his family” but it ends up being the kernel of a
good biography of an interesting person. Bonus link; on YouTube,
<a href="https://www.youtube.com/watch?v=3WIR3Riq4wM">Willie Nelson - Teatro, featuring Daniel Lanois & Emmylou Harris,
Directed by Wim Wenders</a>. Strong stuff.</p>
<p>Speaking of recorded music, check out
<a href="https://www.dazeddigital.com/music/article/69407/1/why-listening-parties-are-everywhere-right-now-rosalia-album-launch-artist">Why
listening parties are everywhere right now</a>. Huh? They are? As a deranged audiophile, sounds like my kind of thing. I’d go.</p>
<h2 id='p-4'>Somewhere to put worker bees</h2>
<p>When I was working at AWS in downtown Vancouver back starting in 2015, a lot of our junior engineers lived in these
teeny-tiny little one-room-tbh apartments. It worked out pretty well for them, they were affordable and an easy walk from the
office and these people hadn’t built up enough of a life to need much more room.
For a while this trend of
so-called-“studio” flats was the new hotness in Vancouver and I guess around quite a bit of the developed world.
Us older types with families would look at the
condo market and tell each other “this is stupid”.</p>
<p>We were right. The
bottom is falling out and they’re sitting empty in their thousands. And not just the teeniest either, the whole
condo business is in the toilet. It didn’t help that for a few years all the prices went up every year (until they didn’t) and
you could make serious money flipping unbuilt condos, so lots of people did (until they didn’t).</p>
<p>Anyhow, here’s a nice write-up on the subject:
<a href="https://www.bbc.com/news/articles/cqxq32zzq8eo">‘Somewhere to put worker bees’: Why Canada's micro-condos are losing
their appeal</a>. (From the BBC, huh?)</p>
<h2 id='p-5'>AI AI AI</h2>
<p>Sorry, I can’t not relay pro- and anti-GenAI posts, because that conversation is affecting all our lives just now. I am
actually getting ready to decloak my own conclusions, but for the moment I’m just sharing essays on the subject that strike me as
well-written and enjoyable for their own sake. Thus
<a href="https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/">‘AI' is a dick move, redux</a> from Baldur
Bjarnason. Boy, is he mad.</p>
<p>Sam Ruby has been doing some
<a href="https://intertwingly.net/blog/2026/01/28/Twilight-Zone.html">extremely weird shit</a>, running Rails in the browser, as
in without even a network connection or a Ruby runtime. Yes, AI was involved in the construction.</p>
<h2 id='p-6'>Software</h2>
<p>There’s this programming language called Ivy that is in the APL lineage; that acronym will leave young’uns blank but a few greying
eyebrows will have been raised. Anyhow,
<a href="https://commandcenter.blogspot.com/2026/01/implementing-transcendental-functions.html?m=1">Implementing the
transcendental functions in Ivy</a> is delightfully geeky, diving deep with no awkwardness. By no less than Rob Pike.</p>
<p>Check out Mike Swanson’s
<a href="https://blog.mikeswanson.com/backseat-software/">Backseat Software</a>. That’s “backseat” as in “backseat driver”,
which today’s commercial software has now, annoyingly, become. This piece doesn’t make any points that I haven’t heard (or made
myself) elsewhere, but it pulls a lot of the important ones together in a well-written and compelling package. Recommended.</p>
<p>Old Googler Harry Glaser
<a href="https://www.linkedin.com/posts/harryglaser_i-worked-on-ads-at-google-15-years-ago-when-activity-7423057144402427905-nm3p/">reacts
with horror</a> to the introduction of advertising by OpenAI, and makes gloomy predictions about how it will evolve. His predictions
are obviously correct.</p>
<p>The title says it:
<a href="https://petapixel.com/2026/01/17/discovering-a-digital-photo-editing-workflow-beyond-adobe/">Discovering a Digital
Photo Editing Workflow Beyond Adobe</a>. It’d be a tough transition for me, but the relationship with Adobe gets harder and
harder to justify.</p>
<h2 id='p-7'>Indigenous reconciliation</h2>
<p>Khelsilem is one of the loudest and clearest voices coming out of the Squamish nation, one of the larger and better-organized
Indigenous communities around here.</p>
<p>There has been a steady drumbeat of Indigenous litigation going on for decades as a
consequence of the fact that the British colonialists who seized the territory in what we now call British Columbia didn’t
bother to sign treaties with the people who were already there, they just assumed ownership. The Indigenous people have been
winning a lot of court cases, which makes people nervous.</p>
<p>Anyhow, Khelsilem’s
<a href="https://khelsilem.substack.com/p/the-source-of-the-reconciliation">The Real Source of Canada's Reconciliation Panic</a>
covers the ground. I’m pretty sure British Columbians should read this, and suspect that anyone in a jurisdiction undergoing similar
processes should too.</p>
<h2 id='p-8'>Resonant computing, Black and Blue sky</h2>
<p>There’s this thing called the
<a href="https://resonantcomputing.org">Resonant Computing Manifesto</a>, whose authors and signatories include names you’d
probably recognize. Not mine; the first of its Five Principles begins with “In the era of AI…” Also, it is entirely oblivious to
the force driving the enshittification of social-media platforms: Monopoly ownership and the pathologies of late-stage
capitalism.</p>
<p>Having said that, the vision it paints is attractive. And having said <em>that</em>, it’s now featured on the flags waved by
the proponents of ATProto, which is to say Bluesky. See Mike Masnick’s
<a href="https://www.techdirt.com/2026/01/27/atproto-the-enshittification-killswitch-that-enables-resonant-computing/">ATproto:
The Enshittification Killswitch That Enables Resonant Computing</a> (Mike is on Bluesky Corp’s Board). That piece is OK but, in
the comments, Masnick quickly gets snotty about the Fediverse and Mastodon, in a way that I find really off-putting. And once
again, says nothing about the underlying economic realities that poison today’s platforms.</p>
<p>I want to like Bluesky, but I’m just too paranoid and cynical about money. It is entirely unclear who is funding the people
and infrastructure behind Bluesky, which matters, because if Bluesky Corp goes belly-up, so does the allegedly-decentralized service.</p>
<p>On the other hand,
<a href="https://blackskyweb.xyz">Blacksky</a> is interesting. They are trying to prove that ATProto really can be made
decentralized in fact not just in theory.
<a href="https://blackskyweb.xyz/overview/">Their ideas and their people</a> are stimulating, and their
<a href="https://opencollective.com/blacksky">finances are transparent</a>. I’ll be
<a href="https://docs.blacksky.community/migrating-to-blacksky-pds-complete-guide">moving my ATProto presence to Blacksky</a>
when I get some cycles and the process has become a little more automated.</p>
<h2 id='p-14'>Good crypto</h2>
<p>The cryptography community is working hard on the problem of what happens should quantum computers ever become real products as
opposed to over-invested fever dreams. Because if they ever work, they can probably crack the algorithms that we’ve been using
to provide basic Web privacy.</p>
<p>The problem is technically
hard<span class='dashes'> —</span> there are good solutions though<span class='dashes'> —</span> and also politically fraught,
because maybe the designers or standards orgs are corrupt or incompetent. It’s reasonable to worry about this stuff and people
do. They probably don’t need to: Sophie Schmieg dives deep in
<a href="https://keymaterial.net/2025/11/27/ml-kem-mythbusting/">ML-KEM Mythbusting</a>.</p>
<h2 id='p-16'>Books</h2>
<p>Here’s one of the most heartwarming things I’ve read in months:
<a href="https://blog.openlibrary.org/2026/01/30/a-community-curated-nancy-drew-collection/">A Community-Curated Nancy Drew
Collection</a>. Reminder: The Internet can still be great.</p>
<p>John Lanchester’s
<a href="https://www.lrb.co.uk/the-paper/v46/n17/john-lanchester/for-every-winner-a-loser">For Every Winner a Loser</a>,
ostensibly a review of two books about famous financiers, is in fact an extended howl of
(extremely instructive) rage against the
financialization of everything and the unrelenting increase in inequality. What we need to do is to take the ill-gotten gains
away from these people and put it to a use<span class='dashes'> —</span> any use<span class='dashes'> —</span> that improves
human lives.</p>
<p>I talk a lot about late-stage capitalism. But Sven Beckert published a
<a href="https://www.nytimes.com/2025/11/26/books/review/capitalism-sven-beckert.html?searchResultPosition=1">1,300-page monster entitled <cite>Capitalism</cite></a>;
the link is to a <cite>NYT</cite> review and makes me want to read it..</p>
<p>Charlie Stross, the sci-fi author, likes webtoons and
<a href="https://www.antipope.org/charlie/blog-static/2025/12/webtoons-revisited.html">recommends a bunch</a>. Be careful, do
not follow those links if you’re already short of time. Semi- or fully-retired? Go ahead!</p>
<p>I have history with dictionaries. For several years of my life in the late Eighties, I was the research project manager for
the
<a href="https://cs.uwaterloo.ca/~fwtompa/newoed-project.html">New Oxford English Dictionary</a> project at the University of
Waterloo. Dictionaries are a fascinating topic and, for much of the history of the publishing industry, were big money-makers;
they dominate any short list of the biggest-selling books in history. Then came the Internet.</p>
<p>Anyhow, Louis Menand’s
<a href="https://www.newyorker.com/magazine/2025/12/29/unabridged-the-thrill-of-and-threat-to-the-modern-dictionary-stefan-fatsis-book-review">Is
the Dictionary Done For?</a> starts with a review of a book by Stefan Fatsis entitled <cite>Unabridged: The Thrill of (and
Threat to) the Modern Dictionary</cite> which I haven’t read and probably won’t, but oh boy, Menand’s piece is big and rich and
polished and just a fantastic read. If, that is, you care about words and languages. I understand there are those who don’t, which is
weird. I’ll close with a quote from Menand:</p>
<blockquote><p>“The dictionary projects permanence,” Fatsis concludes, “but the language is Jell-O, slippery and mutable and
forever collapsing on itself.” He’s right, of course. Language is our fishbowl. We created it and now we’re forever trapped
inside it.</p></blockquote>
</div></content></entry>
<entry>
<title>Quamina v2.0.0</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2026/01/20/Quamina-2.0#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0</id>
<published>2026-01-20T12:00:00-08:00</published>
<updated>2026-01-21T15:27:06-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>There’ve been a few bugfixes and optimizations since 1.5, but the headline is: <a href='https://github.com/timbray/quamina?tab=readme-ov-file#quamina'>Quamina</a> now knows regular expressions. This is roughly the fourth anniversary of the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and other tech enthusiasms.) Open-source software, it’s a damn fine hobby</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>There’ve been a few bugfixes and optimizations since 1.5, but the headline is:
<a href="https://github.com/timbray/quamina?tab=readme-ov-file#quamina">Quamina</a>
now knows regular expressions. This is roughly the fourth anniversary of
the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and
other tech enthusiasms.)
Open-source software, it’s a damn fine
hobby.</p>
<p>Did I mention optimizations? There are <i>(sob)</i> also regressions; introducing REs had
measurable negative impacts on other parts of the system.
But it’s a good trade-off. When you ship software that’s designed for pattern-matching, it should
really do REs. The RE story, about a year long, can be read starting
<a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series">here</a>.</p>
<h2 id='p-4'>Quamina facts</h2>
<ol>
<li><p>About 18K lines of code (excluding generated code), 12K of which are unit tests. The RE feature makes the tests run
slower, which is annoying.</p></li>
<li><p>Adding Quamina to your app will bulk your executable size up by about 100K, largely due
to Unicode tables.</p></li>
<li><p>There are a few shreds of AI-assisted code, none of much importance.</p></li>
<li><p>A Quamina instance can match incoming data records on my 2023 M2 Mac at millions per
second without much dependence on how many patterns are being matched at once. This assumes
not too many horrible regular expressions. That’s per-thread of course, and Quamina does
multithreading nicely.</p></li>
</ol>
<h2 id='p-1'>Next?</h2>
<p>The
<a href="https://github.com/timbray/quamina/issues">open issues</a> are modest in number but
some of them will be hard.</p>
<p>I think I’m going to ignore that list for a while (PRs welcome, of course) and work on
optimization. The introduction
of epsilon transitions was required for regular expressions, but they really bog the matching
process down. At Quamina’s core is the
<a href="/ongoing/When/202x/2024/07/28/Union-of-Finite-Automata">finite-automaton merge</a> logic,
which contains fairly elegant code but generally throws up its hands when confronted with
epsilons and does the simplest thing that could possibly work. Sometimes at an annoyingly slow pace.</p>
<p>Having said that, to optimize you need a good benchmark that pressures the
software-under-test.
Which is tricky, because Quamina is so fast that it’s hard to
to feed it enough data to stress it without the feed-the-data code dominating
the runtime and memory use. If anybody has a bright idea for how to pull together a good
benchmark I’d love to hear it. I’m looking at
<a href="https://go.dev/blog/testing-b-loop">b.Loop()</a> in Go 1.24, any reason not to go there?</p>
<h2 id='p-3'>Book?</h2>
<p>It occurs to me that as I’ve wrestled with the hard parts of Quamina, I’ve done the obvious
thing and trawled the Web for narratives and advice. And, more or less, been disappointed. Yes,
there are many lectures and blogs and so on about this or that aspect of finite automata, but
they tend to be mathemagical and theoretical and say little about how, practically speaking,
you’d write code to do what they’re talking about.</p>
<p>The Quamina-diary <span class='o'>ongoing</span> posts now contain several tens of thousands
of words. Also I’ve previously written
<a href="/ongoing/When/200x/2006/04/18/XML-Grammar">quite a bit</a> about Lark, the world’s
first XML parser, which I wrote and was automaton-based. So I think there’s a case for a slim
volume entitled something like <cite>Finite-state Automata in the Code Trenches</cite>. It’d be
a big money-maker, I betcha. I mean, when Apple TV brings it to the screen.</p>
<h2 id='p-2'>Why?</h2>
<p>Let’s be honest. While
<a href="https://github.com/timbray/quamina">the repo</a> has quite a few stars, I truly have no idea who’s
using Quamina in production. So I can’t honestly claim that this work is making the
world better along any measurable dimension.</p>
<p>I don’t much care because I just can’t help it. I love executable abstractions for their own sake.</p>
</div></content></entry>
<entry>
<title>Losing 1½ Million Lines of Go</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2026/01/14/Unicode-Properties#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties</id>
<published>2026-01-14T12:00:00-08:00</published>
<updated>2026-01-14T15:52:47-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support character-property regexp features in <a href='https://github.com/timbray/quamina'>Quamina</a>. Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this is about (among other things) <em>avoiding</em> those 1½M lines. And really only of interest to people whose pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I think I should maybe have used</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support
character-property regexp features in
<a href="https://github.com/timbray/quamina">Quamina</a>.
Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this
is about (among other things) <em>avoiding</em> those 1½M lines. And really only of interest to people whose
pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I
think I should maybe have used.</p>
<h2 id='p-1'>Character property matching</h2>
<p>I’m talking about regexp incantations like <code>[\p{L}\p{Zs}\p{Nd}]</code>, which matches anything that Unicode classifies
as a letter, a space, or a decimal number. (Of course, in Quamina “<code>\</code>” is “<code>~</code>”
<a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series#p-7">for excellent reasons</a>, so that reads
<code>[~p{L}~p{Zs}~p{Nd}]</code>.)</p>
<p>(I’m writing about this now because I just launched
<a href="https://github.com/timbray/quamina/pull/465">a PR</a> to enable this feature. Just one more to go before I can
release a new version of Quamina with full regexp support, yay.)</p>
<h2 id='p-3'>Finding the properties</h2>
<p>To build an automaton that matches something like that, you have to find out what the character properties are.
This information comes from the
<a href="https://www.unicode.org/ucd/">Unicode Character Database</a>, helpfully provided online by the Unicode consortium.
Of course, most programming languages have libraries that will help you out, and
<a href="https://pkg.go.dev/unicode#pkg-variables">that includes Go</a>, but I didn’t use it.</p>
<p>Unfortunately, Go’s library doesn’t get updated every time Unicode does. As of now, January 2026,
it’s still stuck at Unicode 15.0.0, which
<a href="https://www.unicode.org/history/publicationdates.html">dates to September 2023</a>; the latest version is 17.0.0, last
September. Which means there are plenty of Unicode characters Go doesn’t know about, and I didn’t want Quamina to settle
for that.</p>
<p>So, I fetched and parsed the famous master file from
<a href="https://www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt">www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt</a>.
Not exactly rocket science, it’s a flat file with <code>;</code>-delimited fields, of which I only cared about the first
and third. There are some funky bits, such as the pair of nonstandard lines indicating that the Han characters occur
between U+4E00 and U+9FFF inclusive; but still not really taxing.</p>
<p>The output is, for each Unicode category, and also for each category’s complement (<code>~P{L}</code> matches everything
that’s <em>not</em> a letter; note the capital <code>P</code>), a list of pairs of code points, each pair indicating a subset
of the code space where that category applies. For example, here’s the first line of character pairs with category <code>C</code>.</p>
<pre><code> {0x0020, 0x007e}, {0x00a0, 0x00ac}, {0x00ae, 0x0377},</code></pre>
<p>How many pairs of characters, you might wonder? There are 37 categories
and it’s all over the place but adds up to a lot. The top three categories
are L with 1,945 pairs, Ll at 664, and M at 563. At the other end are Zl and Zp, both with just 1.
The total number of pairs is 14,811, and the generated Go code is a mere 5,122 lines.</p>
<h2 id='p-5'>Character-property automata</h2>
<p>Turning these creations into finite automata was straightforward: I already had the code to handle regexps like
<code>[a-zA-Z0-9]</code>, logically speaking the same problem. But, um, it wasn’t fast. My favorite unit test, an exercise in
<a href="/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1">sample-driven development</a> with 992 regexps,
suddenly started taking multiple seconds, and my whole unit-test suite expanded from around ten seconds to over twelve; since I
tend to run the unit tests every time I take a sip of coffee or scratch my head or whatever, this was painful. And it occurred to
me that it would be painful in practice to people who want for some good reason or another to load up a bunch of
Unicode-property patterns into a Quamina instance.</p>
<p>So, I said to myself, I’ll just precompute all the automata and serialize them into code. And now we
get to the title of this essay; my data structure is a bit messy and ad-hoc and just for the categories, before I got to the
complement versions, I was generating 775K lines of code.</p>
<p>Which worked! But, it was 12M in size and while Go’s runtime is fast, there was a painful pause while it absorbed those data
structures on startup. Also, opening the generated file regularly caused my IDE
(<a href="https://www.jetbrains.com/go/">Goland</a>) to crash. And I was only halfway there. The whole approach was painful to
work with so I went looking for Plan B.</p>
<p>The code that generates the automaton from the code point pairs is pretty well the simplest thing that could possibly work
and it was easy to understand but burned memory like crazy. So I worked for a bit on making it faster and
cheaper, but so far have found no low-hanging fruit.</p>
<p>I haven’t given up on that yet. But in the meantime, I remembered
Computer Science’s general solution for all performance problems, by which I mean caching. So now, any Quamina instance will
compute the automaton for a Unicode property the first time it’s used, then remember it. So now Quamina’s speed at adding
Unicode-property regexps to an instance has increased from 135/second to 4,330, a factor of thirty and Good Enough For
Rock-n-Roll.</p>
<p>It’s worth pointing out that while <em>building</em> these automata is a heavyweight process, Quamina can use them to match
input messages at its typical rates, hundreds of thousands to millions per second. Sure, these automata are “wide”, with lots of
branches, but they’re also shallow, since they run on UTF-8 encoded characters whose maximum length is four and average length
is much less. Most times you only have to take one or two of those many branches to match or fail.</p>
<h2 id='p-2'>Should I have used Claude?</h2>
<p>This particular segment of the Quamina project included some <em>extremely</em> routine programming tasks, for example
fetching and parsing
UnicodeData.txt, computing the sets of pairs, generating Go code to serialize the automata, reorganizing source files that had
become bloated and misshapen, and writing unit tests to confirm the results were correct.</p>
<p>Based on my own
<a href="/ongoing/When/202x/2025/07/01/First-AI-Code">very limited experience</a> with GenAI code, and in particular after
reading Marc Brooker’s
<a href="https://brooker.co.za/blog/2025/12/16/natural-language.html">On the success of ‘natural language programming’</a> and
Salvatore (“antirez”) Sanfilippo’s
<a href="https://antirez.com/news/158">Don't fall into the anti-AI hype</a>, I guess I’ve joined the camp that thinks
this stuff is going to have a place in most developers’ toolboxes.</p>
<p>I think Claude could have done all that boring stuff, including acceptable unit tests, way faster than I did.
And furthermore got it right the first time, which I didn’t.</p>
<p>So why didn’t I use Claude? Because I don’t have the tooling set up and I was impatient and didn’t want to invest the time in
getting all that stuff going and improving my prompting skills. Which reminds me of all the times I’ve been trying to evangelize other
developers on a better way to do things and was greeted by something along the lines of “Fine, but I’m too busy right now, I’ll
just going on doing things the way I already know how to.”</p>
<p>Does this mean I’m joining the “GenAI is the future and our investments will pay off!” mob? Not in the slightest. I still
think it’s overpriced, overhyped, and mostly ill-suited to the business applications that “thought leaders” claim for it.
That word “mostly” excludes the domain of code; as I said
<a href="/ongoing/When/202x/2025/09/26/GenAI-Predictions#p-5">here</a>, “It’s pretty obvious that LLMs are better at predicting code
sequences than human language.”</p>
<p>And, as it turns out, the domain of Developer Tools has never been a Big Business by the standards of GenAI’s promoters. Nor
will it ever be; there just aren’t enough of us. Also, I suspect it’ll be reasonably easy in the near future for open-source
models and agents to duplicate the capabilities of Claude and its ilk.</p>
<p>Speaking personally, I can’t wait for the bubble to pop.</p>
<h2 id='p-4'>Quamina.next?</h2>
<p>After I ship the numeric-quantifier feature, e.g. <code>a{2-5}</code>, Quamina’s regexp support will be complete and if no
horrid bugs pop up I’ll pretty quickly release Quamina 2.0. Regexps in pattern-matching software are a qualitative difference-maker.
After that I dunno, there are lots more interesting features to add.</p>
<p>Unfortunately, a couple years into my Quamina work, I got distracted by life and by other projects, and ignored it. One
result is that so did the other people who’d made major contributions and provided PR reviews. I miss them and it’s less fun
now. We’ll see.</p>
</div></content></entry>
<entry>
<title>Regexp Lessons</title>
<link href='https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2026/01/01/Quamina-2026#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026</id>
<published>2026-01-01T12:00:00-08:00</published>
<updated>2026-01-06T10:19:29-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I’m just landing a <a href='https://github.com/timbray/quamina/pull/461'>chonky PR</a> in <a href='https://github.com/timbray/quamina'>Quamina</a> whose effect is to enable the <code>+</code> and <code>*</code> regexp features. As in my <a href='/ongoing/When/202x/2025/07/21/Automaton-merge-war'>last chapter</a>, this is a disorderly war story not an essay, and probably not of general interest. But as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are <em>dozens</em> of us)</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>I’m just landing a
<a href="https://github.com/timbray/quamina/pull/461">chonky PR</a> in
<a href="https://github.com/timbray/quamina">Quamina</a> whose effect is to enable the <code>+</code> and <code>*</code> regexp
features. As in my
<a href="/ongoing/When/202x/2025/07/21/Automaton-merge-war">last chapter</a>, this is a disorderly war story not an essay, and
probably not of general interest. But
as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are
<em>dozens</em> of us).</p>
<h2 id='p-5'>2014-2026</h2>
<p>As I write this, I’m sitting in the same couch in my Mom’s living room in Saskatchewan where, on my first Christmas after
joining AWS, I got the first-ever iteration of this software to work. That embryo’s mature form is available to the world as
<a href="https://github.com/aws/event-ruler">aws/event-ruler</a>. (Thanks, AWS!) Quamina is its direct descendent, which means
this story is entering its twelfth year.</p>
<p>Mom is now 95 and good company despite her failing memory. I’ve also arrived at a qualitatively later stage of life than in
2014, but would like to report back from this poorly-lit and often painful landscape: Executable abstractions are still fun,
even when you’re old.</p>
<p>Anyhow, the reason I’m writing all this stuff isn’t to expound on the nature of finite automata or regular expressions, it’s
to pass on lessons from implementing them.</p>
<h2 id='p-8'>Lesson: Seek out samples</h2>
<p>In a previous episode I used the phrase
<a href="/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1">Sample-driven development</a> to describe my luck in
digging up 992 regexp test cases, which reduced task task from intimidating to approachable.
I’ve never previously had the luxury of wading into a big software task armed with loads of test cases written by other
people, and I can’t recommend it enough. Obviously you’re not always going to dig this sort of stuff up, but give it a sincere
effort.</p>
<h2 id='p-9'>Lesson: Break up deliverables</h2>
<p>I decomposed regular expressions into ten unique features, created an enumerated type to identify them, and implemented them
by ones and twos.
Several of the feature releases used
techniques that turned out to be inefficient or just wrong when it came to subsequent features. But they worked,
they were useful, and my errors nearly all taught me useful lessons.</p>
<p>Having said that, here’s some cool output that combines this lesson and the one above, from the unit test that runs
those test cases. Each case has a regexp then one
or more samples each of strings that should and shouldn’t match. I instrumented the test to report the usage of regexp features
in the match and non-match cases.</p>
<pre>Feature match test counts:
32 '*' zero-or-more matcher
27 () parenthetized group
48 []-enclosed character-class matcher
7 '.' single-character matcher
29 |-separated logical alternatives
16 '?' optional matcher
29 '+' one-or-more matcher
Feature non-match test counts:
45 '+' one-or-more matcher
24 '*' zero-or-more matcher
31 () parenthetized group
49 []-enclosed character-class matcher
6 '.' single-character matcher
32 |-separated logical alternatives
21 '?' optional matcher</pre>
<p> Of course, since most of the tests combine multiple features, the numbers for all the features
get bigger each time I implement a new one. Very confidence-building.</p>
<h2 id='p-2'>Lesson: Thompson’s construction</h2>
<p>This is the classic nineteen-sixties regular-expression implementation by Ken Thompson, described in Wikipedia
<a href="https://en.wikipedia.org/wiki/Thompson%27s_construction">here</a> and (for me at least) more usefully, in a
storytelling style by Russ Cox,
<a href="https://swtch.com/%7Ersc/regexp/regexp1.html">here</a>.</p>
<p>On several occasions I rushed ahead and implemented a feature without checking those sources, because how hard could it be?
In nearly every case, I had problems with that first cut and then after I went and consulted the oracle, I could see where I’d
gone wrong and how to fix it.</p>
<p>So big thanks, Ken and Russ.</p>
<h2 id='p-3'>Lesson: List crushing</h2>
<p>In some particularly nasty regular expressions that
combine <code>[]</code> and <code>?</code> and <code>+</code> and <code>*</code>, you can
get multiple states connected in complicated ways with epsilon links.</p>
<p>In Thompson’s Construction, traversing an NFA transitions not just from one state to another but from a current set of states
to a next set, repeat until you match or fail. You also compute epsilon closures as you go along; I’m skipping over details
here. The problem was that traversing these pathologically complex regexps with a sufficiently long string was leading to an
exponential explosion in the current-states and next-states sizes<span class='dashes'> —</span> not a figure of speech, I mean
<code>O(2<sup>N</sup>)</code>. And despite the usage of the word “set” above, these weren’t, they contained endless
duplicates.</p>
<p>The <em>best</em> solution would be to study the traversal algorithm and improve it so it didn’t emit fountains of dupes. That
would be hard. The next-best would to turn these things into actual de-duped sets, but that would require a hash table right in
the middle of the traversal hot spot, and be expensive.</p>
<p>So what I did was to detect whenever the next-steps list got to be longer than N, sorted it, and crushed out all the dupes.
As I write, N is now 500 based on running benchmarks and finding a value that makes number go down.</p>
<p>The reason this is good engineering is that the condition where you have to crush the list almost never happens, so in the
vast majority of cases the the only cost is an <code>if len(nextSteps)>N</code> comparison. Some may find this approach
impure, and they have a point. I would at some point like to go back and find a better upstream approach. But for now it’s still
really fast in practice, so I sleep soundly.</p>
<h2 id='p-4'>Lesson: Hell’s benchmark</h2>
<p>I’ve
<a href="/ongoing/When/202x/2025/07/21/Automaton-merge-war#p-1">written before</a> about my struggles with the benchmark where I
merge 12,959 wildcard patterns together. Back before I was doing epsilon processing correctly, I had a kludgey implementation
that could match patterns in the merged FA at typical Quamina speeds, hundreds of thousands per second. With correct epsilon
general-purpose epsilon handling, I have so far not been smart enough to find a way to preserve that performance. With the full
13K patterns, Quamina matches at less than 2K/second, and with a mere thousand, at 16K/second. I spent literally days
trying to get better results, but decided that it was more valuable to Quamina to handle a large subset of regular expressions
correctly than to run idiotically large merges at full speed.</p>
<p>I’m pretty sure that given enough time and consideration, I’ll be able to make it better. Or maybe someone else who’s smarter
than me can manage it.</p>
<h2 id='p-11'>Question: What next?</h2>
<p>The still-unimplemented regexp features are:</p>
<pre>{lo,hi} : occurrence-count matcher
~p{} : Unicode property matcher
~P{} : Unicode property-complement matcher
[^] : complementary character-class matcher</pre>
<p>Now I’m wondering what to do next. <code>[^]</code> is pretty easy I think and is useful, also I get to invert a
state-transition table. The
<code>{lo,hi}</code> idiom shouldn’t be hard but I’ve been using regexps for longer than most of you have been alive and have
never felt the need for it, thus I don’t feel much urgency. The Unicode properties I think have a good fun factor just because
processing the Unicode character database tables is cool. And, I’ve used them.</p>
<p><i>[Update: the <code>[^]</code> thing took a grand total of a couple of hours to build and test. Hmm, what next?]</i></p>
<h2 id='p-10'>Lesson: Coding while aging</h2>
<p>I tell people I keep working on code for the sake of preserving my mental fitness. But mostly I do it for fun. Same for
writing about it. So, thanks for reading.</p>
</div></content></entry>
<entry>
<title>Humanist Plumbing</title>
<link href='https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing' />
<link rel='replies' thr:count='5' type='application/xhtml+xml' href='/ongoing/When/202x/2025/12/18/Humanist-Plumbing#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing</id>
<published>2025-12-18T12:00:00-08:00</published>
<updated>2025-12-20T10:40:20-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Business' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Business' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage capitalism. These days, that’s almost always a story worth telling</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage
capitalism. These days, that’s almost always a story worth telling.</p>
<p>Normally, faced with a drip,
we’d pull out the old cartridge, take it to the hardware store, and buy another to swap in.
But the fixture in our
<a href="/ongoing/When/202x/2025/02/28/Moved">recently-acquired</a> place was kind of exotic and abstract and neither of us
could figure it out. We were gloomy because we’ve had terrible luck over the years with the local plumbing storefronts.
So…</p>
<h2 id='p-1'>The neighbors</h2>
<p>Our neighborhood has an online chat; both sides of the streets in a square around a single city block. This is our first
experience with such a thing. I gather that these don’t always work out well, but this one has been mostly pretty great.</p>
<p>So at 9AM I posted “Hey folks, looking for a plumber recommendation” and by ten there were three.</p>
<p><i>[Late-stage capital: “You’re supposed to ask the AI in your browser. It’ll
provide a handy link to a vendor based on geography and reviews but mostly advertising spend.
Why would you want to talk to other people?”]</i></p>
<h2 id='p-2'>Thomas</h2>
<p>I picked a neighbor’s suggestion, first name
Thomas, and called the number. “Thomas here” on the second ring. I explained and he said “What’s the brand name? If
it’s one of those Chinese no-names I probably have to replace the whole thing.” I said “No idea, but I’ll take a picture and send it to
you.”</p>
<p>Turns out the brand was
<a href="https://riobel.design/en/">Riobel</a>, never heard of them. I texted Thomas a picture and he got right back to me: “That’s
high-end, it’s got a lifetime warranty. I’ll come by a little after 5 and take it out. Their dealer is in PoCo (an outer suburb)
and I live out there, so I can swap it.”</p>
<p><i>[Late-stage capital: “You’re supposed to engage with the chatbot on the site we sent you to, which will integrate with your
calendar and arrange for a diagnostic visit a week from Wednesday. You could call them but you’d be in voice-menu hell and
eventually end up at the same chatbot.”]</i></p>
<p>When Thomas showed up, with a sidekick, he was affable and obviously competent.
Within five minutes I was glad I’d called for help; that faucet’s construction was highly non-obvious. Thomas knew what he was
doing and it still took him the best part of a half-hour to get it all disassembled and the cartridge extracted.</p>
<h2 id='p-6'>Nothing’s perfect</h2>
<p>The next morning, a text from Thomas: “Bad news. That part is back-ordered till May at Riobel’s dealer. We can maybe get it
online but you’d have to pay.” He attached a screenie of a Web search for the part number; there were several online
vendors.</p>
<p>It’s irritating that the “lifetime warranty” doesn’t seem to be helping me, but to be fair, the part was initially installed
in 2011.</p>
<p><i>[Late-stage capital: “Lifetime warranty? Huh? Oh, of course you mean our VIP-class
subscription offering, that’s monthly with a
discount for annual up-front payment.”</i> (And the part would still be back-ordered.)]</p>
<h2 id='p-3'>Kolani</h2>
<p>High-end plumbing parts are expensive. But one of Thomas’ recommendations,
<a href="https://kolani.ca">Kolani Kitchen and bath</a>, was asking less.</p>
<p>They had a phone number on their
Web site so I called it and the voice menu only had three options: Location, opening hours, and Operator.
The operator was an intelligent human and picked up right away.
“Hi, I’m looking at ordering a cartridge and wanted to see if you had it in stock.” “Gimme the part number?” I
did and she went away for a couple of minutes and came back “Yeah, it’s in stock.” So I ordered it and I have a tracking
number.</p>
<p><i>[Late-stage capital: “There aren’t supposed to be independent dealers; the manufacturer has taken PE money and eliminated
the middlemen to better capture all the value-add.
Or maybe there’ll be a wholesaler, but just one, because another PE rolled up all the distributors to maximize pricing power.
Either way, you won’t be able to get a human on the line.”]</i></p>
<h2 id='p-7'>Payment</h2>
<p>Next morning, I got an email that my order had been canceled. So I called that intelligent operator and she said “I was going
to email you. Our system won’t take payment if the billing and delivery addresses are different. Sorry. If you’re in a hurry you
could do an e-transfer?” (In Canada, all the banks are in a payments federation that makes this dead easy.) So I
did and the part has shipped.</p>
<p><i>[Late-stage capital: “What? If you’d used our Integrated online payment offering, it would all just work. What if it
doesn’t, you ask? Yeah, sucks to be you in that situation, of course there’d be nobody you could talk to about that.”]</i></p>
<p>Thomas came by again to put the old cartridge back in for now and said “This thing, don’t worry about a drip, it’s not fast
and it probably won’t get worse. Text me when the new part gets in.”</p>
<h2 id='p-5'>Late-stage capitalism</h2>
<p>It won’t be missed when it’s gone.</p>
</div></content></entry>
<entry>
<title>After the Bubble</title>
<link href='https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble' />
<link rel='replies' thr:count='7' type='application/xhtml+xml' href='/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble</id>
<published>2025-12-07T12:00:00-08:00</published>
<updated>2025-12-09T15:29:05-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
<category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the damage will be and what the hangover will feel like. On that basis, I was going to post a link on Mastodon to Paul Krugman’s <a href='https://paulkrugman.substack.com/p/talking-with-paul-kedrosky'>Talking With Paul Kedrosky</a>. It’s great, but while I was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.” So consider this a preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go read that</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the
damage will be and what the hangover will feel like.
On that basis, I was going to post a link on Mastodon to Paul Krugman’s
<a href="https://paulkrugman.substack.com/p/talking-with-paul-kedrosky">Talking With Paul Kedrosky</a>. It’s great, but while I
was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.”
So consider this a
preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go
read that.</p>
<h2 id='p-2'>Depreciation</h2>
<p>When companies buy expensive stuff, for accounting purposes they pretend they haven’t spent the money; instead they
“depreciate” it over a few years. That is to say, if you spent a million bucks on a piece of gear and decided to depreciate it
over four years, your annual financials would show four annual charges of $250K.
Management gets to pick your depreciation period, which provides a major opening
for creative accounting when the boss wants to make things look better or worse than they are.</p>
<p>Even when you’re perfectly honest it can be hard to choose a fair figure. I can remember one of the big
cloud vendors announcing they were going to change their fleet depreciation from three to four years and that having an impact on
their share price.</p>
<p>Depreciation is orderly whether or not it matches reality: anyone who runs a data center can tell you about racks with 20
systems in them that have been running fine since 2012. Still, orderly is good.</p>
<p>In the world of LLMs, depreciation is different. When you’re doing huge model-building tasks, you’re running
those expensive GPUs flat out and red hot for days on end. Apparently they don’t like that, and flame out way more often than
conventional computer equipment. Nobody who is doing this is willing to come clean with hard numbers but there are data points, for
example from
<a href="https://www.tomshardware.com/tech-industry/artificial-intelligence/faulty-nvidia-h100-gpus-and-hbm3-memory-caused-half-of-the-failures-during-llama-3-training-one-failure-every-three-hours-for-metas-16384-gpu-training-cluster">Meta</a>
and (very unofficially)
<a href="https://www.tomshardware.com/pc-components/gpus/datacenter-gpu-service-life-can-be-surprisingly-short-only-one-to-three-years-is-expected-according-to-unnamed-google-architect">Google</a>.</p>
<p>So GPUs are apparently fragile. And they are expensive to run because they require huge
amounts of electricity. More, in fact, than we currently have, which is why electrical bills are spiking here and there around
the world.</p>
<p>Why does this matter? Because when the 19th-century railway bubble burst, we were left with railways. When the
early-electrification bubble burst, we were left with the grid. And when the
<a href="https://en.wikipedia.org/wiki/Dot-com_bubble">dot-com bubble</a> burst, we were left with a lot of valuable
infrastructure whose cost was sunk, in particular dark fibre. The AI bubble? Not so much; What with GPU burnout and power charges,
the infrastructure is going to be expensive to keep running, not something that new classes of application can pick up and use on
the cheap.</p>
<p>Which suggests that the post-bubble hangover will have few bright spots.</p>
<h2 id='p-1'>SPVs</h2>
<p>This is a set of purely financial issues but I think they’re at the center of the story.</p>
<p>It’s like this. The Big-Tech giants are insanely profitable but they don’t have enough money lying around to build the
hundreds of billions of dollars worth of data centers the AI prophets say we’re going to need. Which shouldn’t be a problem;
investors would line up to lend them as much as they want, because they’re pretty sure
they’re going to get it back, plus interest.</p>
<p>But apparently they don’t want to borrow the money and have the debts on their balance sheet. So they’re
setting up “Special Purpose Vehicles”, synthetic companies that are going to build and own the data centers; the Big Techs
promise to pay to use them, whether or not genAI pans out and whether or not the data centers become operational. Somehow,
this doesn’t count as “debt”.</p>
<p>The financial voodoo runs deep here. I recommend Matt Levine’s
<a href="https://newsletterhunt.com/emails/205961">Coffee pod financing</a> and the <cite>Financial Times’</cite>
<a href="https://www.ft.com/content/d0344253-b0a2-4c6d-8b97-520243678afd">A closer look at the record-smashing ‘Hyperion’
corporate bond sale</a>. Levine’s explanation has less jargon and is hilarious; the
<cite>FT</cite> is more technical but still likely to provoke horrified eye-rolls.</p>
<p>If you think there’s a distinct odor of 2008 around all this, you’d be right.</p>
<p>If the genAI fanpholks are right, all the debt-only-don’t-call-it-that will be covered by profits and everyone can sleep
sound. Only it won’t. Thus, either the debts will apply a meat-axe to Big Tech profits, or (like 2008) somehow they won’t be
paid back. If whoever’s going to bite the dust is “too big to fail”,
the money has to come from… somewhere? Taxpayers? Pension funds? Insurance companies?</p>
<h2 id='p-3'>Paul K and Paul K</h2>
<p>I think I’ve set
<a href="https://paulkrugman.substack.com/p/talking-with-paul-kedrosky">that piece</a> up enough now. It points out a few other
issues that I think people should care about. I have one criticism: They argue that genAI won’t produce sufficient revenue from
consumers to pay back the current investment frenzy. I mean, they’re right, it won’t, but that’s not what the investors are
buying. They’re buying the promise, not of <em>more revenue</em>, but of <em>higher profits</em> that happen when tens of
millions of knowledge workers are replaced by (presumably-cheaper) genAI.</p>
<p>I wonder who, after the loss of those tens of millions of high-paid jobs, are going to be the
consumers who’ll buy the goods that’ll drive the profits that’ll pay back the investors. But that problem is kind of
intrinsic to Late-stage Capitalism.</p>
<p>Anyhow, there will be a crash and a hangover. I think the people telling us that genAI is the future and we
must pay it fealty richly deserve their impending financial wipe-out.
But still, I hope the hangover is less terrible than I think it will be.</p>
</div></content></entry>
<entry>
<title>Tracy Numbers</title>
<link href='https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics' />
<link rel='replies' thr:count='2' type='application/xhtml+xml' href='/ongoing/When/202x/2025/12/02/Bell-Combinatorics#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics</id>
<published>2025-12-02T12:00:00-08:00</published>
<updated>2025-12-02T12:00:00-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Music' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Music' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking a class in Afro-Cuban rhythms from <a href='https://drumming.ca'>Russell Shumsky</a>, with whom I’ve studied West-African drumming for many years. Among the basics of Afro-Cuban are the <a href='https://en.wikipedia.org/wiki/Bell_pattern'>Bell Patterns</a>, which come straight out of Africa. The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It feels like it’s in four, particularly when played fast</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking
a class in Afro-Cuban rhythms from
<a href="https://drumming.ca">Russell Shumsky</a>, with whom I’ve studied West-African drumming for many years. Among the
basics of Afro-Cuban are the
<a href="https://en.wikipedia.org/wiki/Bell_pattern">Bell Patterns</a>, which come straight out of Africa.
The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of
three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It
feels like it’s in four, particularly when played fast.</p>
<p>Here’s the standard bell pattern in music notation. Instead of one 12/8 bar, I’ve broken it into four 3/8 chunks. Let’s call
those “mini-measures”; I’ll use that or just “minis” in the rest of this piece.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png" alt="standard 12/8 bell pattern" />
<div class='caption'><p><audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a"></audio></p></div>
<p>Bell patterns are never played in isolation, but circularly on fast repeat, so the first note immediately follows
the last.</p>
<p>In the sound sample, I’m playing a background beat on a conga, emphasizing the beginning of the 12/8 measures.
The actual bell pattern is on the high “child” bell of a
<a href="https://en.wikipedia.org/wiki/Ewe_drumming#Gankogui">Gankoqui</a>, an African dual-cowbell set.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/PXL_20251201_192632520.png" alt="Black cat considers a Gankoqui" />
<div class='caption'><p><a href="/ongoing/When/202x/2021/02/22/Meet-Thorn">“þ” the cat</a> was trying bell patterns but
unfortunately<br/>cats can’t count as high as 12. Collar by
<a href="https://www.birdsbesafe.com">BirdsBeSafe.com</a>.</p></div>
<p>That’s my Gankoqui.
I bought it off someone on Etsy who imports them from Ghana.
It came with that little thin stick that sounds nice, but sometimes I use a regular drumstick when things get loud.</p>
<h2 id='p-1'>The problem</h2>
<p>Russell’s a good teacher and the standard pattern isn’t that tricky, but I just couldn’t get a grip on it.
It’s a little harder than it looks what with cycling it really fast, and then
you’re playing it against complicated music with other instrumental voices.
I probably would have got there, but the lessons ran out of gas in the depths of Covid.</p>
<h2 id='p-2'>Introducing Tracy</h2>
<p>She was Russell’s long-time partner, a good person and good drummer too. When you were struggling
with a complex rhythm it was helpful to watch Tracy’s hands, because she was <em>always</em> on the beat.</p>
<p>Tracy lived with stage four metastatic cancer for many years and braved endless awful rounds of therapy while remaining generally
cheerful. She could be morbidly funny; I bought her congas (you can hear one behind the beat in the samples) when she had a
storage-space problem. She told me she was carefully planning her finances so she’d run out of money just before the cancer got
her.</p>
<p>I always enjoyed any time I spent with her. Then, a dozen years into her cancer
journey, this last summer it got into her brain and it was pretty clear her end times were upon her.</p>
<h2 id='p-3'>The hospice</h2>
<p>Tracy’s last months were spent at
<a href="https://stjohnhospice.ca">St. John Hospice</a> in Vancouver’s far west. I can’t say enough
good things about it. If you’re near Vancouver and your death becomes imminent, try to be there if you can’t be at home.
It’s comfortable and the staff are expert and infinitely kind. The rules that apply at hospices
are different from those at hospitals; for example, Tracy’s cat joined her in residency and had the run of the place.</p>
<p>I (and other fans of Russell and Tracy) visited the hospice a few times. My last visit was just days before her death
and, while she was fatigued and spaced-out, it was still Tracy.
I wasn’t close enough to call her a friend, but I miss her.</p>
<p>We got to talking about Afro-Cuban music and I laughed at myself, saying how I never could get that damn bell pattern
down. Said Russell: “Oh, you mean the standard 12/8 pattern? Tracy, let’s show him” and on the second try, they were doing it
together, just voices, <i>ta ta ta-ta, ta ta ta</i>. </p>
<p>Driving home from the hospice, I told myself that if Tracy could manage the bell pattern in her condition, I could bloody
well learn it. So I studied the details and used a metronome app and after a while
I thought I had it down pretty well.</p>
<h2 id='p-4'>Sounds cool</h2>
<p>I go to a weekly by-invitation African drum jam where I’m on the weaker end of the skill
spectrum. The first time a 12/8 came along after I thought I’d learned the pattern, I had to summon up courage
and then I fluffed the first few bars. But after a while I
was grooving along and smiling and thinking the bell sounded pretty cool against the thunder of all the djembés and dununs.</p>
<p>And, even played amateurishly, it does sound cool. Let’s have another look at the music.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png" alt="standard 12/8 bell pattern" />
<div class='caption'><p><audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a"></audio></p></div>
<p>West-African drumming often tries to achieve rhythmic tension, where a given note could fit in multiple ways and your
ear is not 100% sure what’s going on. The standard pattern does this, twice.</p>
<p>Remember, I said that 12/8 sounds like it’s
“in four”, especially if you hit the first beat of each of the four mini-measures. But two of
the four minis here go around the first note, weakening the 4/4 feel.
Especially on that third mini; you can feel the beat slide by the missing “one”.</p>
<p>Also, the last three notes are evenly spaced two beats
apart, so six of them would fill the 12-beat pattern, suggesting that this might be in triple time, not 12/8.</p>
<p>The effect, to my ears, is of the bell, higher-pitched than the drums, shifting against the rhythm, or even dancing
across it. At the drum jam, at almost any given moment it won’t be just drums, one or more people will have
clave sticks or rattles or tambourines or cowbells weaving through the beat.</p>
<h2 id='p-5'>Mixing it up</h2>
<p>After I felt confident playing the standard pattern, it still sounded cool, but I wanted to branch out, not just
go around and around the same seven notes. So the first thing I did was start mixing in a few of these.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-1.png" alt="bell pattern variation" />
<div class='caption'><p><audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/5333.m4a"></audio></p></div>
<p>This repeats the second bar through the end of the phrase. In the sound sample I mix it up with the standard pattern.
It’s got less rhythmic tension but on the other hand
flows along smoothly with the drum thunder. Also you don’t have to think at all, so you can enjoy listening to what the other
people are playing.</p>
<p>Then I got a little more ambitious and reshuffled:</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-2.png" alt="bell pattern variation" />
<div class='caption'><p><audio controls="controls" src="https://www.tbray.org/ongoing/When/202x/2025/12/02/5253.m4a"></audio></p></div>
<p>The mini-measures are the same as in the standard pattern, just in a different order. Anyhow, this kind of thing is fun.</p>
<h2 id='p-6'>Combinatorics</h2>
<p>Then one evening I was lying in bed, thoughts wandering, and wondered “How many bell patterns are there?”
A little mental math showed that of course there are eight possible arrangements of tones
in a 3-note mini-measure. Here they are:</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/12/02/8-measures.png" alt="Possible arrangements of notes in 3/8 time" />
<div class='caption'><p>I’ll use the boxed numbers to identify the minis.</p></div>
<p>Why are the minis numbered in that order? Every computer programmer looking at this already knows, but for the rest of you: If the
notes are ones and the rests are zeroes, they are the eight binary numbers between zero and seven inclusive.
So each number’s binary bits show where the drumstrokes are.
By the way, numbers four through
seven have a note on the one beat, zero through three don’t.</p>
<p>Is it weird to have a zero i.e. silent mini? I don’t think so, sometimes spaces between the notes really matter.</p>
<h2 id='p-7'>Patterns</h2>
<p>Anyhow, the original question was about the number of different bell patterns. Each has four
mini-measures with 8 possible values. So the answer is 8 ⨉ 8 ⨉ 8 ⨉ 8, which is 4,096.</p>
<p>And each of them can be identified by four little numbers, ranging from T0000 (I can hear the bandleader yelling “gimme zeroes
for the sax break”) to T7777, a flurry of eighth notes that you might use in the big encore-number finish designed to leave the
audience yelling as you walk off stage. The standard bell pattern is T5325; in binary “101 011 010 101” and the 1’s are drumstrokes.
The first variation above is T5333 and the second is T5253.</p>
<p>The “T” in front of each bell pattern number is for Tracy.</p>
<p>If you go look at the
<a href="https://en.wikipedia.org/wiki/Bell_pattern">Wikipedia Bell-pattern article</a>, they emphasize that there are lots of
different patterns. Now they all have numbers! The article
<a href="https://en.wikipedia.org/wiki/Bell_pattern#128_bell_patterns">makes special mention of</a> T5124, T5221, and T5244.</p>
<h2 id='p-8'>But why, Tim?!</h2>
<p>I’m a computer programmer with a Math degree, and an amateur musician.
Anyone who thinks that these are disjoint disciplines is wrong.
And, I think the notation is (on a very small scale) kind of pleasing.</p>
<p>But the work has actually helped me.
Now that I’ve considered each mini-measure and its personality. I find all of them sneaking into
my Gankoqui excursions, which have gotten noticeably weirder, for example T5635.
Nobody’s threatened to kick me out of the jam, so far.</p>
<p>Also, this has given me a real appreciation of whoever it was that, probably thousands of years ago and certainly in Africa,
picked the “standard” pattern as, well, standard. Because it’s great.</p>
<h2 id='p-9'>What’s missing?</h2>
<p>You may have noticed that Gankoquis have two bells and I’ve been ignoring that fact. Normally you’d play these patterns
on the smaller “child” bell, but sometimes bringing the big parent bell in for a couple of strokes works
well.
<a href="https://www.youtube.com/watch?v=X2K0i8e6Ftc">Here’s an example</a> (h/t Russell).</p>
<p>Also, this discussion has been limited to 3/8 minis in 12/8 measures. There’s another whole universe of 4/4 rhythms that
also have bell patterns (but everything exists in the shadow of the
<a href="https://en.wikipedia.org/wiki/Clave_(rhythm)">clave rhythm</a>).
In that world a pattern has four measures, each of which can have sixteen possible values, so there are 65,536 different ones.</p>
<p>And I could repeat the numbers construction above for 4/4. But I’m not going to, because the rewards feel smaller. In my
experience, 4/4 rhythms lope smoothly along and everyone knows where the one is even when there’s no note on it, so there’s less
ambiguity to work with.
Anyhow, any neophyte (like for example me) can play a pretty smooth bell line against 4/4; just start with
<a href="https://en.wikipedia.org/wiki/Clave_(rhythm)">clave</a> and add
variations (or don’t) and you’ll be fine.</p>
<h2 id='p-10'>Useful?</h2>
<p>These numbers are just elementary mathemusical fun. If anyone else wanted to use them that’d be a pleasant surprise.
If “anyone else” is you, go ahead, but they have a name and you have to use it. These are called Tracy Numbers.</p>
<h2 id='p-11'>Colophon</h2>
<p>Music fragments by
<a href="https://www.mu.se/musescore-studio">MuseScore Studio</a>. Sound samples facilitated by GarageBand, a Shure MV51, and PSB
Alphas.</p>
</div></content></entry>
<entry>
<title>Fútbol Joy</title>
<link href='https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football' />
<link rel='replies' thr:count='1' type='application/xhtml+xml' href='/ongoing/When/202x/2025/11/23/Soccer-vs-Football#comments' />
<id>https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football</id>
<published>2025-11-23T12:00:00-08:00</published>
<updated>2025-11-27T20:38:07-08:00</updated>
<category scheme='https://www.tbray.org/ongoing/What/' term='Sports/Football' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Sports' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Football' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Sports/Soccer' />
<category scheme='https://www.tbray.org/ongoing/What/' term='Soccer' />
<summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Last Saturday I had one of my peak 2025 experiences, at the <a href='https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs'>MLS semifinal</a> between the <a href='https://www.whitecapsfc.com/'>Vancouver Whitecaps FC</a> (hereinafter “Caps”) and <a href='https://en.wikipedia.org/wiki/Los_Angeles_FC'>Los Angeles FC</a> (“LAFC”). Both those FC’s stand for “Fútbol Club”. 53,095 other fans were there with my son and I; we came home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports</div></summary>
<content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
<p>Last Saturday I had one of my peak 2025 experiences, at the
<a href="https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs">MLS semifinal</a>
between the <a href="https://www.whitecapsfc.com/">Vancouver Whitecaps FC</a> (hereinafter “Caps”) and
<a href="https://en.wikipedia.org/wiki/Los_Angeles_FC">Los Angeles FC</a> (“LAFC”). Both those FC’s stand for “Fútbol Club”.
53,095 other fans were there with my son and I; we came
home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports.</p>
<p>Earlier this year
<a href="/ongoing/When/202x/2025/05/04/Southsiders">I wrote about becoming a Caps fan</a>. Anyone who enjoys this will probably
like that piece too.</p>
<p>Let’s set the scene with pictures.</p>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_004124670.png" alt="Before the fútbol at the pub" />
<div class='caption'><p>Supporters gather pre-game at a nearby Irish-flavored pub.</p></div>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_011735082.png" alt="Parading from the pub to the match" />
<div class='caption'><p>Supporters march to the game.<br/>When you’re in a frivolous parade, everyone smiles<br/>at
you, even the drivers hemmed in by paraders.</p></div>
<img src="https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_024033770.png" alt="Whitecaps tifo banner: fire that burns / blue melts gold" />
<div class='caption'><p>The banner is what’s called a
<a href="https://en.wikipedia.org/wiki/Tifo">tifo</a>.<br/>I have to admit I failed to parse it.</p></div>
<h2 id='p-5'>The game</h2>
<p>It was 120 minutes of ridiculously over-the-top psychodrama. I was exhausted at the end.
If you want a full retrospective, type “whitecaps lafc” into any Web search to get the particulars. Or
<a href="https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs">hit
this</a>. But here’s the short version:</p>
<ol>
<li><p>The Caps came out sharp and fast and had LAFC pretty well flummoxed through most of the first half, scoring two goals,
<a href="https://www.youtube.com/watch?v=9nEOw8ckWMA">one of which was a jaw-dropper</a>.
They also managed to contain LAFC’s superstar
<a href="https://en.wikipedia.org/wiki/Son_Heung-min">Son Heung-min</a>.</p></li>
<li><p>In the second half, the visitors reconfigured and were much better. Son did the superstar thing and scored two goals,
<a href="https://www.youtube.com/watch?v=-L9N8pkrkSM">one another jaw-dropper</a>, just as the game was ending, to tie things
up.</p></li>
<li><p>The Caps lost two players, one for fouls, one to injury, and were down two men through most of overtime. LAFC’s assault
was relentless but the Caps held on, getting more than a little lucky.</p></li>
<li><p>So it went to a penalty-kick competition. Son, shockingly, missed; he was exhausted and limping. At the end of the
day the Caps scored four out of five to LAFC’s three and got the win.</p></li>
</ol>
<p>Suffice it to say that the dramatic peak wasn’t
any of the flashes of brilliance, but rather the errors that happen when people are at the limit of their endurance. Vancouver
made one fewer, that’s all there was to it.</p>
<h2 id='p-3'>That sound</h2>
<p>There’s not another like it on this planet. I mean tens of thousands of voices in a big stadium greeting a home goal.
Fútbol specifically because its goals, compared to North American sports where points come in dozens, are
such huge markers. The sound-pressure wavefront, coming from every direction, of all those inarticulate howls of joy,
all in the same tiny fraction of a second, is a whole-body experience.</p>
<h2 id='p-6'>The side effect</h2>
<p>I’ve long been a televised-sports fan; the only TV show that isn’t scripted and thus has real drama. But
since getting mixed up in fútbol, I’ve sort of gone off the other sports I used to watch. I had to think a bit to figure
out why.</p>
<p>It’s the ads. The football, basketball and hockey broadcasts screech to a halt
<a href="https://qz.com/150577/an-average-nfl-game-more-than-100-commercials-and-just-11-minutes-of-play">every ten or fewer
minutes</a> for a couple of minutes of advertising. Most of the ads are dumb, many are offensive, and the relentless
addiction-promoting gambling pitches are both. On top of which there’s the bone-headed repetition; someone somewhere thinks
I’m gonna lean toward this generic SUV as opposed to that one because of the 138th time they’ve run that commercial where hip young
people with fulfilling lives are going to have sex because of its dashboard geometry and motorized hatchback.
I mean, the other SUVs have that stuff too, but this one’s actors are more convincingly likely to be headed for bed?</p>
<p>Being in the room with this shit makes me angry even though my mute-button skillz are sharp.
The world being what it is, I really don’t need to be around something that angers me several times per hour.
So, while when young I loved playing both football and basketball, and while the pro games are good entertainment,
my patience seems to be running out.</p>
<p>Fútbol, on the other hand, has two fiftyish-minute chunks of continuous action, so you can sink into the flow of the
game. The contrast, switching back and forth between that and the other North American sports, is stark.</p>
<p>(Except for I’m mostly forgiving baseball because its natural rhythm is full of stops suitable for hot dogs and beer and
admiring cute babies and T-shirts and discussions of etymology and epidemiology. I mean, the ads are still mindless repetitive
shit, we’re just more accustomed to switching attention away when nothing’s happening.)</p>
<p>And I’m not claiming that fútbol is more virtuous or less dirty than any other sport; after all, its global
organizing body FIFA has repeatedly been exposed as
<a href="https://en.wikipedia.org/wiki/FIFA#Corruption">galactically corrupt</a>. I’m just saying it offers a better
experience.</p>
<h2 id='p-9'>Soccer?</h2>
<p>That word is an awkward invention by nineteenth-century British toffs based on abbreviating “association”. I accept that on my
continent “football” means gridiron, but people who enjoy “soccer” still say it so in print I offer “fútbol”, which is a
typographically nice little cluster; please humor me.</p>
<p>Anyhow, you might want to check out your local team; in North America, the prices are lower than the other sports, who could
be against cheap happiness with fewer gambling ads?</p>
</div></content></entry>
</feed>
{
"accept-ranges": "bytes",
"cf-cache-status": "DYNAMIC",
"cf-ray": "9f45fbdd9e66c424-CMH",
"content-length": "173509",
"content-security-policy": "frame-ancestors 'self';",
"content-type": "application/atom+xml",
"date": "Thu, 30 Apr 2026 10:50:09 GMT",
"etag": "\"2a5c5-65075cbb07a36\"",
"last-modified": "Mon, 27 Apr 2026 19:05:19 GMT",
"server": "cloudflare",
"strict-transport-security": "max-age=31536000; includeSubdomains; preload",
"x-content-type-options": "nosniff"
}
{
"meta": {
"type": "atom",
"version": "1.0"
},
"language": "en-us",
"title": "ongoing by Tim Bray",
"description": "ongoing fragmented essay by Tim Bray",
"copyright": "All content written by Tim Bray and photos by Tim Bray Copyright Tim Bray, some rights reserved, see /ongoing/misc/Copyright",
"url": "https://www.tbray.org/ongoing/",
"self": "https://www.tbray.org/ongoing/ongoing.atom",
"published": null,
"updated": "2026-04-27T19:05:18.000Z",
"generator": {
"label": "Generated from XML source code using Perl, Expat, Emacs, Mysql, Ruby, and ImageMagick. Industrial-strength technology, baby.",
"version": null,
"url": "/misc/Colophon"
},
"image": {
"title": null,
"url": "rsslogo.jpg"
},
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [],
"items": [
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives",
"title": "Corey’s Captives",
"description": "That’s James S.A. Corey, which is to say Daniel Abraham and Ty Franck, and their new series The Captive’s War, an in-progress work comprising 2¼ or so novels. The Coreys are of course best-known for their deservedly wildly popular The Expanse series and the subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should wade in, the following is for you",
"url": "https://www.tbray.org/ongoing/When/202x/2026/04/26/Coreys-Captives",
"published": "2026-04-26T19:00:00.000Z",
"updated": "2026-04-27T19:05:14.000Z",
"content": "<p>That’s\n <a href=\"https://en.wikipedia.org/wiki/James_S._A._Corey\">James S.A. Corey</a>, which is to say Daniel Abraham and Ty Franck,\n and their new series\n <a href=\"https://en.wikipedia.org/wiki/The_Captive%27s_War\">The Captive’s War</a>, an in-progress work comprising 2¼\n or so novels. The Coreys are of course best-known for their deservedly wildly popular <cite>The Expanse</cite> series and the\n subsequent success of the streaming-video version. The new series is… different. If you’re wondering whether or not you should\n wade in, the following is for you.</p>\n <h2 id=\"p-1\">Minor and meta spoilers</h2>\n <p>Don’t worry, you can go on reading this even if you plan to read the books. Here’s a spoiler that has appeared in every public\n mention of the book, which I’ll give away with a quote from page 102: “I think some important scientific questions have finally\n been answered. Alien life exists, and they are assholes.” Which is to say, it doesn’t go well for the humans.</p>\n <p>Now for the meta-spoilers. The novels are <cite>The Mercy of Gods</cite> and <cite>The Faith of Beasts</cite>, then there’s a\n novella, <cite>Livesuit</cite>. I found <cite>The Mercy of Gods</cite> a bit of a grind, and if that’s all I’d read I would have\n been pretty negative about this project. There is a major, <em>major</em> reveal partway into <cite>The Faith of Beasts</cite>\n that changed my whole outlook on the series; it makes the storytelling velocity really pick up. It’s a little annoying that\n <cite>Livesuit</cite> was published between the two full novels because it only really makes sense if you’ve finished both of\n them. So do like I did, and read the novella last.</p>\n <p>I have to ask why the Coreys couldn’t have pulled the curtain aside a little earlier on. And while I’m griping, let me add\n that the sped-up storytelling runs into a big honking cliffhanger ending at high velocity. Harumph.</p>\n <h2 id=\"p-2\">My take-away</h2>\n <p>It could go off the rails but if they can maintain their <cite>Expanse</cite> form, I suspect this series is going to be\n pretty great. The characters are fun to know and the narrative revolves around the great mother of all trolley-problem ethical\n challenges, which was not nearly resolved at cliffhanger-ending time.</p>\n <p>Those of us who are fussy about the plausibility of future technologies (hey, Charlie Stross) should avert their eyes from\n the Coreys’ fairly low-effort attempts to explain how the aliens and humans in this story accomplish the things they do. Doesn’t\n bother me much, though.</p>\n <p>Having said all that, this series is not cheerful stuff; I do <em>not</em> recommend it to those who, like many in these\n troubled times, are having trouble seeing the bright side of, well, anything.</p>\n <h2 id=\"p-3\">Will I read the next volume?</h2>\n <p>Yep, no hesitation. And they’ve already started working on a streaming version. Unfortunately it’s going to be on Amazon\n Prime, which I haven’t missed since unsubscribing a couple years ago. Getting this thing on the screen is\n going to be an extended, difficult, task. There are multiple species of aliens that the show is going to have to absolutely nail, with\n emotional credibility, for the story to work. Don’t hold your breath.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Arts/Books",
"term": "Arts/Books",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Arts",
"term": "Arts",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Books",
"term": "Books",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras",
"title": "Spring Evening",
"description": "On impulse, Lauren and I went out for a short walk — around just a few blocks — as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera on the way out the door",
"url": "https://www.tbray.org/ongoing/When/202x/2026/04/13/Modern-Cameras",
"published": "2026-04-13T19:00:00.000Z",
"updated": "2026-04-16T05:23:17.000Z",
"content": "<p>On impulse, Lauren and I went out for a short walk<span class=\"dashes\"> —</span> around just a few\n blocks<span class=\"dashes\"> —</span> as the grey Spring afternoon shaded to dusk. On a second impulse, I grabbed the camera\n on the way out the door.</p>\n <p>In our local community garden, here’s (I think) a\n <a href=\"https://en.wikipedia.org/wiki/Chard\">chard</a>.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56259.png\" alt=\"Looking down on a vegetable plant with glossy green leaves and orange-yellow stalks\"></img>\n <p>That was in Vancouver’s Mount Pleasant park, small but nice and apparently never not used. Also this old blackened\n fruit tree, we’re a bit past the fruit-blossom peak for this year. Nice to see I’m not the only old citizen trying to brighten\n things up.</p> \n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56264.png\" alt=\"Fruit-tree blossoms on a blackened branch\"></img>\n <p>Now we’re walking up a locally-main street called Main Street or “The Main” if you’re trying to sound\n hip. Someone put work into that window! I’ve bought my daughter a couple of cool birthday presents from the store behind it. My\n thanks to the building across the street for providing a dark background reflection.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56265.png\" alt=\"Used-fashion store window \"></img>\n <p>Back to the next block over from ours. A while ago a bunch of people were building little fairy/elf/hobbit villages at the\n bottoms of the big old trees. This isn’t that. What is it?</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/04/13/TXT56270.png\" alt=\"Dolls and related tree artifacts at the base of a tree in dim light\"></img>\n <p>The colors of the natural surfaces are real.</p>\n <h2 id=\"p-1\">Cameras</h2>\n <p>When I shot these, it\n was getting dark but I didn’t think much, mostly just pointed and shot. (Fiddled with the aperture dial a bit.) Then I came\n home and pulled them into Lightroom and didn’t need to do really anything about colors. A bit of contrast and highlights here\n and there. Oh, and fairly brutal cropping, especially on that fruit-tree-flowers pic. Because like I said, I didn’t think very\n much when I was shooting and I didn’t have to because on a Twenties camera you don’t.</p>\n <p>I could take that heavily-cropped fruit-tree\n picture and print it big enough to occupy any domestic wall in your place and yeah, there’d be grain but it wouldn’t\n bother your eyes.</p>\n <p>Anyhow, modern cameras are pretty great. The lowest ISO in today’s set is 2500 and the highest is 6400; the apertures range\n from 2.8 to 5.6.\n Bet you can’t tell the differences. My camera is a reasonably modern Fujifilm but not remotely\n bleeding-edge in camera tech. (Note: 35mm F1.4, now all the Fuji fanfolk are smiling and nodding.)</p>\n <p>Anyhow, there are very <em>very</em> few photographers for whom the camera they carry is the limiting factor in the\n goodness of their pictures. Certainly not me.</p>\n <p>Consider getting a camera. Used is fine, anything built in the last five years, maybe more, will effortlessly take brilliant\n pictures in almost any conditions. Sure, your phone can take great shots too, but the feeling of walking along with something\n that fits your hand and you only have to press one physical button once, that feeling, it helps you see the good pictures when they happen.</p>\n <p>Then go out after and take a walk in the Spring dusk.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Arts/Photos",
"term": "Arts/Photos",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Arts",
"term": "Arts",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Photos",
"term": "Photos",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst",
"title": "Password Manager Angst",
"description": "Our family has used 1Password for many years. Most recently 1Password 7, now at least three years out of date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring Bitwarden. The best choice isn’t obvious; here’s the story thus far",
"url": "https://www.tbray.org/ongoing/When/202x/2026/04/09/Password-Manager-Angst",
"published": "2026-04-09T19:00:00.000Z",
"updated": "2026-04-10T17:42:16.000Z",
"content": "<p>Our family has used\n <a href=\"https://1password.com\">1Password</a> for many years. Most recently 1Password 7, now at least three years out of\n date. We didn’t want to upgrade to the latest version, went looking for alternatives, and have been exploring\n <a href=\"https://bitwarden.com\">Bitwarden</a>. The best choice isn’t obvious; here’s the story thus far.</p>\n <p>Important note: I suspect that most-to-all of the people reading this already are using a password manager. If you’re not,\n please, <i><b>PLEASE</b></i> start now. Your browser probably has an OK one built-in, which is much better than\n nothing.\n <a href=\"https://www.cyber.gc.ca/en/guidance/password-managers-security-itsap30025\">Here</a> is a good write-up on the basics.</p>\n <h2 id=\"p-6\">Our needs</h2>\n <p>They’re not fancy. The house contains Macs and Androids and Windows and an iPad. \n We have hundreds of accounts (some require an authenticator) and a basketfull of secure notes: Government-ID numbers, recovery\n codes, and so on.</p> \n <h2 id=\"p-5\">1Password7 and 8</h2>\n <p>1Password had this nice feature where you could sync between devices without involving any 1Password servers, in a variety\n of ways. We used one of those and liked it.\n 1Password8 insists on storing your data (encrypted, more on that later). That always bothered me because, obviously, that\n repository is a top-priority juicy target for all the bad guys, who range from employees of the Chinese government to geeky\n narcos.</p>\n <p>So we’ve been ignoring 1Password’s increasingly plaintive reminders that we were using years-out-of-date software\n and chugging along with version 7. But, early this year, they broke our sync mode on the Android app and were pretty blunt that the only\n way to get it back was to go to 1P8.</p>\n <h2 id=\"p-7\">Alternatives</h2>\n <p>There are plenty of password managers (Let’s just say “PMs”) out there, but as a regular scanner of the landscape,\n it seems to me that 1Password \n (hereinafter “1P”) and Bitwarden (“Bw”) stand out as leaders. The rest of this piece will focus on those two.\n If you think I’m wrong, say so below but also please say why.</p>\n <p>Note that Bw comes in two flavors: That offered as a subscription service by the company of the same name, or as an open-source\n software suite you can build and run yourself.</p>\n <p>This is not to say that the PMs that are starting to appear built-in to browsers and OSes are worthless or unimportant,\n just that some of us need a little more.</p>\n <h2 id=\"p-8\">The threat models</h2>\n <p>Two are obvious. The first is incompetence, like for example\n <a href=\"https://en.wikipedia.org/wiki/LastPass#Security_incidents\">LastPass</a>, who apparently left the doors more or less\n wide open to those bad guys I mentioned a few paragraphs ago. Complete horror-show.</p>\n <p>The second is legal compulsion, where a government applies pressure to a PM provider to cough up our\n secrets. Anybody who thinks governments won’t try is fooling themselves, because they’ve repeatedly said they want to, and are\n eager to pass ill-considered legislation such as the\n <a href=\"https://en.wikipedia.org/wiki/CLOUD_Act\">CLOUD Act</a>. So we care about that aspect a lot.</p>\n <h2 id=\"p-9\">1P vs Bw: Security</h2>\n <p>I think they both have acceptably-good security postures; check out \n <a href=\"https://bitwarden.com/help/bitwarden-security-white-paper/\">Bitwarden Security Whitepaper</a> and\n <a href=\"https://support.1password.com/1password-security/\">About the 1Password security model</a>.</p>\n <p>Both of them offer to host your data outside of the US, specifically in Canada or the EU.</p>\n <p>But it doesn’t matter <em>that</em> much if a bad guy or bad government gets their hands on your password store; what\n matters is whether or not they can decrypt it. I’m not an infosec professional but I know some and listen to them, and both\n those security postures give me a good feeling. It’s not an accident that they’re pretty similar.</p>\n <p>The actual threat isn’t so much that an adversary cracks the crypto; that’s very unlikely. It’s that they find a way to force\n a PM vendor to build a back door into their software to get access to keys and passwords. For that reason, it would warm\n my heart if either or both of Bw and 1P were to post a\n <a href=\"https://en.wikipedia.org/wiki/Warrant_canary\">Warrant Canary</a>.</p>\n <p>But I’m going to give Bw a very slight edge. First, because of the fact that you can build and run it yourself, if you’re\n willing to take responsibility for operating a server with strong security requirements. (I’m not.)</p>\n <p>The source being open potentially offers a second, and more important I think, advantage: If they were able to get a\n <a href=\"https://en.wikipedia.org/wiki/Reproducible_builds\">Reproducible build</a> working, you’d have assurance that the code\n you can download is the one their service is running. Which reduces the attack surface. (Mind you,\n <a href=\"https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf\">not to zero</a>.) Reproducible\n builds are hard, but if they did that, it would make a difference to me.</p>\n <p>On the other hand, Bw’s software development process\n <a href=\"https://contributing.bitwarden.com/contributing/ai/\">embraces GenAI</a> generally and Claude specifically.\n At this stage in the growth of those technologies, this sends a chill up my spine. To be fair, 1P’s website\n shouts that it’s just the thing for agentic security, whatever that means. And we don’t know anything about 1P’s internal\n software-dev process.</p>\n <h2 id=\"p-10\">1P vs Bw: Fit and finish</h2>\n <p>1P wins this one. The problem is, do they always pop up when needed and never when they’re not? Can they fill every login\n field that needs filling? Does the popup show you just what you need and nothing extraneous? I’ve used both and 1P is just\n better.</p>\n <h2 id=\"p-11\">Business issues</h2>\n <p>This one is also pretty well a saw-off. Both of them have taken substantial chunks of VC money and thus are going to\n come under relentless pressure to enshittify. I worry a little less about this because from what I read,\n there’s not much lock-in.</p>\n <p>Personal experience too: I recently did an export of everything out of 1P and into Bw and it all Just Worked, albeit putting all\n my stuff into a folder named \"No Folder\" that I can’t figure out how to rename.</p>\n <p>Both Bw and 1P are subscription-only, at prices that seem fair to me.</p>\n <h2 id=\"p-12\">Death and recovery and pen and paper</h2>\n <p>As I was reading up on this stuff, the issue of recovering access to your PM after it had been lost came up a couple of times.\n Here’s a scenario where that could be really important: I die. And then my wife needs to get access to bank accounts and\n business emails and so on.</p>\n <p>Somebody (I’ve lost the link) was horrified that one of the PMs suggested writing the password down on a piece of paper as a\n last-resort measure, but I’m here to tell you that they’re wrong. My wife has an envelope containing a piece of paper on which\n appear the passwords for my PM and Mac, my mobile-phone PIN, and a very small number of other secret things she might really\n need if I’m suddenly gone. I have no idea where she put it, but she’s really smart so I don’t worry.</p>\n <p>You should probably do something like this too.</p>\n <h2 id=\"p-13\">What will we do?</h2>\n <p>We’ve paid for a year’s worth of both Bw and 1P. At the moment, we’re leaning to 1P because it’s a little more polished.\n Which matters because my PM is something I use many times every day. Also they’re somewhat Canadian.</p>\n <p>If you think we’ve missed something, please do let us know.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/Identity",
"term": "Technology/Identity",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Identity",
"term": "Identity",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology/Security",
"term": "Technology/Security",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Security",
"term": "Security",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links",
"title": "Long Links",
"description": "This will be the 30th Long-Links outing. I’m 100% sure that there does not live a human being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to open one occasionally. All aboard!",
"url": "https://www.tbray.org/ongoing/When/202x/2026/03/24/Long-Links",
"published": "2026-03-24T19:00:00.000Z",
"updated": "2026-03-26T23:36:32.000Z",
"content": "<p>This will be the 30<sup>th</sup> Long-Links outing. I’m 100% sure that there does not live a human\n being who has looked at all those Links, but my logfiles say that quite a few of you, Dear Readers, at least take the time to\n open one occasionally. All aboard!</p>\n <p>Sadly, more than half the Long Links, this time out, are about AI. I almost decided to bury the piece but, whatever you or I\n think, the subject matters. And the ones I posted are a tiny fraction of those I read (or tried to) and I think are \n useful and not immoral.</p>\n <p>But, let’s put all the non-AI stuff at the front so you can stop reading partway through if you’ve just had enough of\n that stuff.</p>\n <h2 id=\"p-1\">Not about GenAI</h2>\n <p>Paul Ford has, after a lengthy gap, started writing again at\n <a href=\"https://ftrain.com\">ftrain.com</a>. Excellent!\n Go there any day and there’ll almost certainly be something good at the top of the\n page. He’s a technologist and, yeah, writes about AI sometimes, but\n <a href=\"https://ftrain.com/warp-and-woof\">Warp and Woof</a> is about dogs and their people. Charming.</p>\n <p>I think most people who aren’t ultra-wealthy now agree that inequality is currently a central problem of our society. But it\n would be nice to put some numbers behind that assertion.\n <a href=\"https://paulkrugman.substack.com/p/talking-with-gabriel-zucman\">Here</a> is a conversation between Paul Krugman,\n Nobel-prizewinning economist, and Gabriel Zucman, a French specialist in the subject and frequent Piketty collaborator.\n Now, there are quite a few paragraphs up front of talk about general macroeconomic issues and comparisons between the US and Europe,\n which I enjoyed reading. And then inequality; here’s Zucman: “And so everybody now understands what was long understood for\n centuries, very much including in the West, which is that extreme wealth is never virtual, it is always extreme power.”</p>\n <p>CO<sub>2</sub> densities in Parts Per Million are a good measure of how full your inhalations are of others’ exhalations. And\n thus of how likely you are to catch something by breathing. Especially, Covid, which everyone with a half a brain knows is not\n nearly over. Anyhow, A. Grieve-Smith offers\n <a href=\"https://grieve-smith.com/ftn/2026/03/nine-observations-from-carbon-dioxide-monitoring/\">Nine observations from carbon\n dioxide monitoring</a>: “I’ve been checking carbon dioxide levels for over three years now, and I’ve started to see patterns.”\n This piece could save your life, and that’s not a metaphor.</p>\n <p>Patrick McKenzie, who writes <cite>Bits About Money</cite>, has an icy-cool style and this Link could be a Little Less Long,\n but I learn interesting things every time I read one of his pieces. \n <a href=\"https://www.bitsaboutmoney.com/archive/fraud-investigation/\">Fraud Investigation is Believing Your Lying\n Eyes</a> launches from the Minnesota child-care fraud story, but is mostly, as the title suggests, relates the conventional wisdom\n (which I didn’t know) about how to go sniffing around for in-progress fraud. \n From which “As a fraud investigator, you are allowed and encouraged to read Facebook at work.”</p>\n <p>Hari Kunzru has written good books and is a former London native. <cite>Harpers</cite> gave him an assignment:\n Walk around and write about the city, thus\n <a href=\"https://harpers.org/archive/2026/02/another-london-situationists-hari-kunzru/\">Another London: Excavating the\n disenchanted city</a>. It’s a tour through time as much as space<span class=\"dashes\"> —</span> London, obviously, is\n history-drenched<span class=\"dashes\"> —</span> and not just politics and power either, but arts and ideas. The writing is\n beautiful. It’ll take a chunk out of your day but the trade-off is good.</p>\n <p>Here’s something beautiful:\n <a href=\"https://thehtml.review/05/\">The HTML Review</a>. Now I want to publish there, but I’d have to up my\n writing game.</p>\n <h2 id=\"p-5\">Lankum</h2>\n <p>They’re an Irish band I just discovered, courtesy of Qobuz. The music grows out of traditional Irish acoustic folk. They play\n old and new songs and throw in a heavy dose of snarl and drone. Some of the chords are like rotated model augmented 11ths or some\n such, scratchy around the edges but helped with an itch I hadn’t known I had. Terrific musicians. Here’s\n <a href=\"https://www.youtube.com/watch?v=lUReQ9GhT8s\">Hunting the Wren</a>. I might get over-excited and fly to Ireland to see them.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/24/Lankum.png\" alt=\"Lankum in concert\"></img>\n <h2 id=\"p-2\">Tech, but not GenAI</h2>\n <p>Sebastian Pipping is, among other things, an Open-Source software developer, with whom\n <a href=\"/ongoing/When/202x/2021/03/24/XMLWF-dash-k\">I’ve collaborated</a>. His recent\n <a href=\"https://blog.hartwork.org/posts/learn-from-me/\">Learn from me!</a> begins “Not too long ago, someone literally asked me\n what they \"could learn from me\", and that question has stuck with me since.” So he offers a few candidate lessons. What a nice\n idea! What could people learn from <em>you</em>?</p>\n <p>Filippo Valsorda, another OSS dev, is particularly interesting because he and a few partners have apparently figured out\n <a href=\"https://geomys.org\">how to make a living from their work</a>. \n He recently published\n <a href=\"https://words.filippo.io/dependabot/\">Turn Dependabot Off</a> and I’m not going to offer a word of explanation because\n if you understand the title I guarantee you’ll be interested in the piece. (I’m terrified of Dependabot.)</p>\n <p>It seems like every day I hear from another person who’s trying to get their personal lives off Big Tech. Me too. So…\n In <cite>The Verge</cite>,\n <a href=\"https://www.theverge.com/tech/879114/best-big-tech-app-alternatives-installer\">How to un-Big Tech your online life</a>.\n And from Paris Marx,\n <a href=\"https://disconnect.blog/getting-off-us-tech-a-guide/\">Getting off US tech: a guide</a>. We are in the early stages of\n de-Googling our family life, so this stuff is super useful. I expect to see more of it.</p>\n <h2 id=\"p-4\">Amazon polemics, maybe a little AI</h2>\n <p>I don’t loathe Amazon any more nor less than the rest of the Big Techs, but boy are there are a lot of people\n publishing diatribes against the company. Not sure I understand why. But, worth reading.</p>\n <p>In\n <a href=\"https://markatwood.substack.com/p/how-amazon-dies-a-possible-maybe?\">How Amazon Dies: A Possible, Maybe Likely\n Future</a> Mark Atwood predicts that the infestation of amazon.com with highly-profitable advertising is a perhaps-fatal\n blunder. What’s maybe more interesting is that he points out several potential Amazon alternatives that don’t suffer from\n that same infestation; they hadn’t occurred to me.</p>\n <p>And from a year ago, Cory Doctorow’s\n <a href=\"https://pluralistic.net/2025/03/13/electronic-whipping/#youre-next\">The future of Amazon coders is the present of\n Amazon warehouse workers</a> introduces the “shitty technology adoption curve”. I missed this piece at the time but boy, is it\n easy to believe.</p>\n <p>Finally, reading\n <a href=\"https://www.bigtechnology.com/p/writing-crystalized-thinking-at-amazon?\">Writing Crystalized Thinking At Amazon. Is AI\n Muddying It?</a> angered me. While I have no remaining respect or affection for any of the Big Techs, I enjoyed my time at AWS\n and part of it was the writing culture. I think the Way Of The Six-pager is the best business-process innovation I witnessed in\n my working life. If Amazon really is slopifying it, I predict disastrous outcomes. </p>\n <h2 id=\"p-3\">OK, here’s the AI stuff</h2>\n <p>My own position, just to be clear: There are going to be LLM applications in a few domains here and there, and one of them is\n software development, but they won’t be nearly big enough to damage earth’s climate any further, nor to prevent the bubble from\n popping. That said…</p>\n <p>Let’s do the worst first:\n <a href=\"https://www.heavybit.com/library/article/write-only-code\">Write-Only Code</a> lays out a genuinely frightening future.\n Quote: “I was maniacally insistent that any proposed change to our SDLC (software development life cycle) be evaluated first\n through the lens of developer velocity.”\n I think I’d rather not go there.</p> \n <p>Most of us who watch the space, and have no idea where it’s going or what the future holds, are I think particularly\n interested in Anthropic’s Claude. If you’re one, you’ll probably enjoy\n <a href=\"https://www.newyorker.com/magazine/2026/02/16/what-is-claude-anthropic-doesnt-know-either\">What Is Claude? Anthropic\n Doesn’t Know, Either</a>.</p>\n <p>It’s probably not that GenAI is intrinsically immoral. As Karl Bode writes,\n <a href=\"https://karlbode.com/the-problem-with-ai-is-shitty-human-beings/\">The Problem With AI Is Shitty Human Beings</a>. I\n covered some of the same territory last year in\n <a href=\"/ongoing/When/202x/2025/07/06/AI-Manifesto\">The Real GenAI Issue</a>, but Bode is excellent:\n “…the grand vision of modern automation's benefits can never materialize if its stewards are <i>foundationally fucking terrible\n human beings disinterested in the contours of empathy.</i> If we're not talking prominently about that, we aren't really talking at\n all.” (Emphasis his.)</p>\n <p>One of the things that shitty people do is lie. Like for example charismatic leaders of AI “startups” valued in the tens of\n billions. But then so do the less-visible, which provoked Kyle Kingsbury A.K.A. Aphyr to write\n <a href=\"https://aphyr.com/posts/405-trudging-through-nonsense\">Trudging Through Nonsense</a>. It’s sad and angry but I think\n usefully so.</p>\n <p>Armin Ronacher is not bursting with rage, but he is skeptical about all the right things in\n <a href=\"https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/\">Some Things Just Take Time</a>. Quote:\n “There’s a feeling that all the things that create friction in your life should be automated away. That human involvement should\n be replaced by AI-based decision-making. Because it is the friction of the process that is the problem. When in fact many times\n the friction, or that things just take time, is precisely the point.”</p>\n <p>For another cool-voiced critique, here’s Rishi Baldawa:\n <a href=\"https://rishi.baldawa.com/posts/ai-mandates-manufacture-noise/\">AI Mandates Manufacture Noise</a>. While I’m not\n entirely a burn-it-all-with-fire GenAI foe, the “boss mandate” always struck me as dumb, and Rishi spells it out clearly\n and simply. It’s really good, so here are a couple of quotes: “But those not in the weeds had no way to know any of this\n because… well they aren’t in the weeds. So they feel compelled to solve their information gap with a policy hammer.” and \n “As said before, none of this is revolutionary and that’s sort of the point. AI is a ’mirror and multiplier‘. It intensifies\n whatever was already happening.”</p>\n <h2 id=\"p-6\">That’s all</h2>\n <p>Let’s really hope the bubble bursts soonest. Because when the money goes away, so will a lot of the shitty people.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "The World",
"term": "The World",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "The World",
"term": "The World",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns",
"title": "Nash Burns Saves the Day",
"description": "What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their emails to us were bouncing. Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on. Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly price, and has been trouble-free",
"url": "https://www.tbray.org/ongoing/When/202x/2026/03/20/Nash-Burns",
"published": "2026-03-20T19:00:00.000Z",
"updated": "2026-03-20T20:53:25.000Z",
"content": "<p>What happened was, soon after New Year’s, friends and colleagues in the UK and Germany started letting us know that their\n emails to us were bouncing. \n Our “textuality.com” family domain is a Google Workspace (or whatever they call it this year) for email and docs and so on.\n Its Web presence, including DNS, has for many years been handled by a local outfit I’ll call “CWH” for some absurdly low monthly\n price, and has been trouble-free.</p>\n <p>So, what could be wrong? We investigated and discovered that Google was offering a new-and-improved MX-record option,\n although they emphasized that the old setup should still work. Anyhow, we installed the New Thing and it didn’t help.</p>\n <p>So, we filed a ticket with CWH tech support and somebody got back to us pretty quick, saying they’d changed a firewall\n setting that was blocking connections to Germany. I detect the scent of GDPR, but whatever. <br></br>\n Euro-email: Bounce, bounce.</p>\n <p>CWH: Probably an MX-record issue, and we should wait for DNS propagation. Several days passed and\n bounce, bounce, bounce. <br></br>Us: “Not DNS propagation.” <br></br>CWH: “Still could be.”</p>\n <p>So we VPN’ed to Germany and discovered we couldn’t ping\n Textuality’s IP address. Smells like a firewall to me. We told CWH that.</p>\n <p>CWH: We have made some changes to firewall settings.\n <br></br>EMail: bounce, bounce, bounce.\n <br></br>VPN+Ping: Request timeout, request timeout, request timeout.</p>\n <p>CWH: Try traceroute?\n <br></br>VPN+Traceroute: 14 hops, no joy.</p>\n <p>CWH: Your VPN settings must be wrong. Here are instructions to use Windows PC VPN correctly.<br></br>\n Us: Thanks but no.</p>\n <p>CWH: Your MX records are configured incorrectly. <br></br>Us: No, they are correct per Google guidance. We sent an email beginning\n “Please believe us.”</p>\n <p>CWH: It must be DNSSEC. Check to see if your registrar implements DNSSEC. <br></br>Us: We are using your DNS servers.</p>\n <p>CWH: Perhaps your registrar is broadcasting an old record? <br></br>Us: Our registrar doesn’t do DNSSEC.</p>\n <p>At this point we consulted a friend who’s an expert on DNS and Email and even DNSSEC. He verified that not only could\n you not ping \n Textuality from Germany, you also couldn’t ping CWH or its name servers. Firewall firewall firewall!</p>\n <p>CWH: “I did test the site access using a 3rd party application, and it seems to be accessible on all parts.” <br></br>Us: Look at the\n output, it shows we can’t be reached from anywhere in Germany.</p>\n <p>Also, for all the remaining messages in the email trail, we prefixed our input with bold face extra-large text reading:\n <b>Systems located in Germany cannot ping Textuality.com’s IP address, nor can they ping the IP addresses of textuality.com’s\n designated name servers. This is the problem.</b></p>\n <p>CWH: Let’s try migrating you to a different server; try pinging these hostnames. <br></br>VPN+Ping: Nope.</p>\n <p>CWH: Are you sure it’s not your VPN settings? <br></br>Us: Are you sure it’s not your GDPR settings?<br></br>\n CWH: Raising your issue to Tier 3.</p>\n <p>20 hours pass, then we get email from:</p>\n <h2 id=\"p-1\">Nash Burns!</h2>\n <p>…who said “This has been fixed.” It was.\n Nash’s email signature was “Nash(Rajaneesh) B”. What a great name, though. Thanks, Nash.</p>\n <h2 id=\"p-2\">Am we mad?</h2>\n <p>Not really. Consumer-facing tech support is hard. None of their suggestions were unreasonable.\n Doing GDPR correctly is hard. \n They’ve been just fine for years and were having a bad week.\n Could we expect better from any of CWH’s local competitors? Probably not.</p>\n <p>It wasn’t funny at the time, but looking back, it kind\n of is.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/Web",
"term": "Technology/Web",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Web",
"term": "Web",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please",
"title": "Pure Sound Please",
"description": "This last weekend we attended a concert entitled Lenten Reflection at Vancouver’s Catholic Holy Rosary Cathedral featuring the Belle Voci vocal group and the Cantare Super Orchestram early-music band. The music was fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below). And so I get to report on good music and yell at production people",
"url": "https://www.tbray.org/ongoing/When/202x/2026/03/16/Pure-Sound-Please",
"published": "2026-03-16T19:00:00.000Z",
"updated": "2026-03-18T21:34:31.000Z",
"content": "<p>This last weekend we attended a concert entitled <cite>Lenten Reflection</cite> at Vancouver’s Catholic\n <a href=\"https://en.wikipedia.org/wiki/Holy_Rosary_Cathedral_(Vancouver)\">Holy Rosary Cathedral</a> featuring the\n <a href=\"https://bellevoci.ca\">Belle Voci</a> vocal group and the\n <a href=\"https://chilliwacksymphony.com/cantare-super-orchestram/\">Cantare Super Orchestram</a> early-music band. The music was\n fine and it was the most beautiful sound I’ve heard in a long time. Twenty-two months, to be precise (see below).\n And so I get to report on good music and yell at production people.</p>\n <p>A cathedral is a nice place for a concert!</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_215727574.png\" alt=\"Interior of Vancouver’s Holy Rosary Cathedral\"></img>\n <p>The concert opened with just the singers, their voices drifting down from a high place behind us, a balcony or choir loft.\n There was no incremental accompaniment and no amplification; the music flowed from vocal cords to\n eardrums<span class=\"dashes\"> —</span> not directly, of course, there was lots of reflection and reverberation introduced by the\n Cathedral space. The singers were polished and expressive and the sound, drifting through the vast space, beyond exquisite.</p>\n <p>They sang a lovely piece by Byrd (1539-1623). Then the instrumentalists played a number by von Biber (1644-1704) while the\n singers snuck downstairs. Joined, they performed Bach’s BWV\n <a href=\"https://en.wikipedia.org/wiki/Komm,_Jesu,_komm,_BWV_229\">229</a> and\n <a href=\"https://en.wikipedia.org/wiki/Nach_dir,_Herr,_verlanget_mich,_BWV_150\">150</a>, then pieces by Pergolesi (1710-1736)\n and Steffani (1654-1728).</p>\n <p>The Bach pieces, as usual, had more music in the music, but the others were also fun. It was a small ensemble: In\n the choir, five sopranos, five altos, a countertenor, four each tenors and basses. The band had five baroque\n violins, a baroque viola, a baroque cello, a\n <a href=\"https://en.wikipedia.org/wiki/Violone\">violone</a> (think, string bass with frets), a baroque bassoon, and a player\n doubling on harpsichord and organ. Thus, an ensemble quite likely not too much bigger or smaller than the ones playing this\n music in the 1700s, when it was new.</p>\n <h2 id=\"p-2\">That sound</h2>\n <p>Once again, the sound was something special and yeah, the musicians were excellent, but for me, the key thing was the lack of\n amplification: vocal cord to eardrum via cathedral. It’s always seemed obvious to me that you can’t run music through a bunch of\n electronics and speaker mechanics without changing it; if only spatially, with the sounds coming from speaker diaphragms located\n somewhere away from the human musician.\n To my ears, there is a fragile magic in pure unamplified sound. I lack the words to describe the difference but it’s not\n subtle. </p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/16/PXL_20260314_212418188.png\" alt=\"“Lenten Reflections” concert singers and players\"></img>\n <p>Does this mean that everything was perfect? No; the choir was a little bit male-heavy; some of the soprano and especially\n alto lines were part-hidden behind the massed male voices. Also, the bassoon was right at the front of the stage;\n While the playing was fine, it felt as though it were musically, not just physically “in front of” the band and\n singers.</p>\n <p>Both of these could have been fixed, by telling the men to take it down a notch or having one or two fewer of them. And by\n moving the bassoon back to the usual woodwinds spot behind the strings. Still, these were very minor imperfections.</p>\n <p>Oh, and the performance and sound of the bass line on that violone was absolutely awesome; clearly audible as a thing on its\n own while it wove all the other musical threads together.</p>\n <p>I’ve discovered that few classical musicians share my passion for unamplification. I hear things like “I want a\n <em>full</em> sound or “The soloists need to cut through the orchestra.” Which, well, OK, but somehow people managed to\n accomplish those things for centuries, before amplifiers and speakers were invented.</p>\n <h2 id=\"p-1\">22 months?</h2>\n <p>That’s since May of 2024 when I took in the \n <a href=\"/ongoing/When/202x/2024/05/26/TTB\">Tedeschi-Trucks Band</a>, whose music couldn’t be more different from anything\n called “Lenten Reflections”: electric not acoustic, profane not sacred. But crystal clear and perfectly balanced\n sound; so much better than most electric bands achieve.</p>\n <p>My sincere thanks to the musicians and their leaders for a lovely experience. And my message to everyone co-ordinating and\n leading live music performances: Of course the first priority has to be the quality of the music, but think about the sound and\n try to be better. Better than than most performances manage, these days.</p>\n <p>We know it’s possible.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Arts/Music",
"term": "Arts/Music",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Arts",
"term": "Arts",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Music",
"term": "Music",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak",
"title": "Because Algospeak",
"description": "Recently I read Because Internet by Gretchen McCulloch and Algospeak by Adam Aleksic. The language we speak (and text) to each other is at the core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth. So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry",
"url": "https://www.tbray.org/ongoing/When/202x/2026/03/05/Because-Algospeak",
"published": "2026-03-05T20:00:00.000Z",
"updated": "2026-03-07T18:29:41.000Z",
"content": "<p>Recently I read\n <a href=\"https://en.wikipedia.org/wiki/Because_Internet\">Because Internet</a> by\n <a href=\"https://gretchenmcculloch.com\">Gretchen McCulloch</a> and\n <a href=\"https://en.wikipedia.org/wiki/Algospeak_(book)\">Algospeak</a> by\n <a href=\"https://en.wikipedia.org/wiki/Adam_Aleksic\">Adam Aleksic</a>. The language we speak (and text) to each other is at the\n core of who and what we are, and the Internet is the strongest among the forces that channel and fertilize its growth.\n So there’s scope for plenty of books on the subject. Both books educated and entertained, one made me angry.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/05/covers.png\" alt=\"The covers of “Because Internet” and “Algospeak”\"></img>\n <h2 id=\"p-1\">Because Internet (2019)</h2>\n <p>Its approach is historical and its voice fairly uninflected. It smiles and\n argues, but it doesn’t ROFL nor does it YELL AT YOU. The history is longer, perhaps, than most people reading this have\n been online (or even alive). Ms McCulloch goes back to the days of BBSes (“bulletin-board systems”) and ListServs and IRC. Some of\n the jargon and formulations of those days live on; you’d be surprised.</p>\n <p>Here’s her table of contents.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/05/BI-toc.png\" alt=\"Table of Contents from “Because Internet”\"></img>\n <p>The analysis is grounded in the formalisms of the author’s profession, academic linguistics. Nothing wrong with that.</p>\n <p>Let’s look at a couple of her ideas, beginning with Chapter 1’s “Informal Writing”. A few of us, back in the late\n Eighties, noticed that computers in general and the then-nascent Internet in particular were driving a writing\n renaissance.</p>\n <p>Before computers, a knowledge worker who had laboriously constructed essays in college quite likely wrote\n almost nothing for the rest of their working life. People talked face-to-face or on the phone, and dictated to\n secretaries. Written communication was seen as necessarily formal and disjoint from the way we spoke, or that we wrote in\n personal correspondence. Then, suddenly, everyone was sitting at a keyboard only seconds away from everyone else’s screen.\n McCulloch goes deep on this:</p>\n <blockquote><p>In the future, the era of writing between the invention of the printing press and the internet may come to be\n seen as an anomaly—an era when there arose a significant gap between how easy it was to be a writer versus a reader. An era when\n we collectively stopped paying attention to the informal, unedited side of writing and let typography become static and\n disembodied.</p>\n <p>The internet didn’t create informal writing, but it did make it more common, changing some of our previously spoken\n interactions into near-real-time text exchanges.</p></blockquote>\n <p>From which all of this follows. It feels like a central insight. I suppose you could argue that centrality of informal text\n is fading in the face of short-form video. Maybe,\n it’s too soon to tell.</p>\n <p>Then consider chapter 5, about emojis. Linguists obviously need to think about them because now they’re an\n integral part of written language. McCulloch’s insight is that they correspond almost exactly to gestures, the way we use\n our hands to add force to our speech. Obviously, for example, “👍”. Or when you’re talking about something completely\n loopy and you twirl your index finger by your ear? You meant “🤪”.</p>\n <p>I offer the emoji story for flavor, an example of a linguist’s approach to what we’re doing to our language with our\n networks.</p> <p>McCulloch has lots more of this stuff.\n I enjoyed <cite>Because Internet</cite> a lot, partly because I’m old and my memories stretch back to those BBS and\n IRC days and I had a front-row seat for the decades of linguistic seething and heaving. And also because I’m a\n <a href=\"https://www.rfc-editor.org/rfc/rfc9839.html\">Unicode geek</a>.</p>\n <h2 id=\"p-2\">Algospeak (2025)</h2>\n <p>The subtitle is “How Social Media Is Transforming the Future of Language”. OK, but… \n Social media is a fertile field for language evolution. Thing is, corporate social media discourse\n lives in the dire grip of the proprietors’ algorithms. And that’s where Adam Aleksic focuses. He treats all of them\n as a single opaque object, “The Algorithm”, which I think is fair because they all are designed with one goal: To\n maximize the effectiveness of human conversation at generating advertising revenue.</p>\n <p>First, the Table of Contents.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/03/05/AS-toc.png\" alt=\"Table of Contents from “Algospeak\"></img>\n <p>Aleksic knows whereof he speaks: As “Etymology Nerd”, his aggregate following across TikTok, Instagram, and YouTube is\n over three million. He’s all about cool bits and pieces of\n linguistics, often Internet-specific usages.\n If I had the patience for podcasts I suppose his would be near the top of my list.</p>\n <p>He really enjoys his work and has fun talking about some of Social Media’s more colorful linguistic extrusions; check\n that Table of Contents. I’m kind of old and I learned a lot about the words and emojis younger folk emit, and I think most folks,\n even those just out of their teens, would too. I’m on a Discord for a \n <a href=\"/ongoing/What/Sports/Soccer/\">Major League Soccer</a> team’s fans, and while it’s totally all-ages, I can say I am regularly\n less mystified than I was before I read <cite>Algospeak</cite>.\n For example, now I know what it means when someone tosses “💀” into a chat. Do you?</p>\n <p>Aleksic isn’t averse to a little history himself. Looking back over the successive online-jargon volcanoes, he argues\n convincingly that two stand out as extra productive. First of all, the short-lived (but hot stuff at the time)\n <a href=\"https://en.wikipedia.org/wiki/Vine_(service)\">Vine</a> video platform. Second, the incel cesspool; sad but\n (apparently) true.</p>\n <h2 id=\"p-3\">The Algorithm</h2>\n <p>Remember, it’s all about what advertisers want. And wow, do they ever want a lot of things. I’ll just touch on a few of\n Aleksic’s points.</p>\n <p>First of all, they don’t want to find themselves next to downers. So if you want to talk about death or suicide or rape or\n racism or rage, \n you need to fool The Algorithm. Thus “unalive” and many other dodges. Of course, The Algorithm learns about them so you\n have to keep dodging. Neither side of this struggle can stay ahead for long.</p>\n <p>Here’s another thing I didn’t know: Apparently written Chinese is particularly rich in techniques for euphemizing, making it\n easier for users of that language to evade, for a time, The Algorithm.</p>\n <h2 id=\"p-4\">Partitioning people</h2>\n <p>Another big thing The Algorithm likes is grouping people into smaller and smaller baskets based on interests, generations,\n and many other criteria. This is because advertisers can aim very specific campaigns at just exactly the right cohort of people who\n are likely to buy what they’re selling. Here’s a quote; See how the language fills in behind advertisers’ pressure?</p>\n <blockquote><p>It doesn’t matter how much I label myself. If I’m a demisexual goblincore Gen\n Z Swiftie, I guarantee there are still others like me. The only thing these labels really change about me is that they make me\n easier to classify and market to. Ironically, true individuality may come out of a <em>lack</em> of labels and stories, because\n there’s greater freedom of expression with a blank slate. If everybody’s the “main character,” then nobody is.</p></blockquote>\n <p><cite>Algospeak</cite>, unlike <cite>Because Internet</cite>, doesn’t limit itself to written language. One of its most\n compelling studies concerns the vocal techniques of podcasters and YouTubers. The finding is simple: It’s hard to build and hold an\n audience for your show unless you sound like MrBeast. No, really.</p>\n <p>Anyhow, they’re both good books. <cite>Because Internet</cite> educated and entertained me. <cite>Algospeak</cite> is way\n more intense, intentionally more like the subject it addresses. Also it made me angry. I am a lover of human language and of its\n patterns of growth and mutation and simplification and complexification. Linguistics is one of the disciplines I regret not\n having chosen.</p>\n <p>Aleksic makes it clear that there’s an amusing narrative about how the people living and speaking in the shade of the Algorithm\n can never defeat it, but they can still manage to get their messages across. But they shouldn’t have to struggle!</p>\n <p>In fact, a few million of us have found a place to talk to each other that isn’t in The\n Algorithm’s shadow: Decentralized social media. Specifically the Fediverse (what people mean when they say “Mastodon”) and maybe\n the ATmosphere (same for “Bluesky”).</p>\n <p>I want to see how language grows in a place where new forms arrive when they’re needed, to say new things that need to be\n said. Not to either serve or resist The Algorithm.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Language",
"term": "Language",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Language",
"term": "Language",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Life Online",
"term": "Life Online",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Life Online",
"term": "Life Online",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI",
"title": "Kansas and AI",
"description": "Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud. Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural changes.” Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/27/Kansas-and-GenAI",
"published": "2026-02-27T20:00:00.000Z",
"updated": "2026-02-28T00:06:19.000Z",
"content": "<p>Block announced that it’s cutting 40% of its workforce. It didn’t say it was replacing those people with GenAI. Not out loud.\n Jack Dorsey did say “I believe the majority of companies will reach the same conclusion and make similar structural\n changes.”\n Wall Street loved it, bidding up the share price by 24%. Which reminded me of Kansas in 2010.</p>\n <h2 id=\"p-1\">The Kansas Experiment</h2>\n <p>As long as I can remember, a certain class of right-wing evangelists has preached that cutting taxes would stimulate business\n growth and everyone would come out ahead. There are a couple of problems with this theory. First, mainstream economists\n almost universally think it’s just wrong. Second, most of the people pushing it are rich and would\n benefit from the cuts.</p>\n <p>Anyhow, in 2010 US Senator Sam Brownback won the race for governor of Kansas on what was then called the “Tea Party” program:\n Prosperity through tax cuts. Tea-party Republicans also won a large majority in the state legislature. Unsurprisingly they\n immediately\n <a href=\"https://en.wikipedia.org/wiki/Kansas_experiment\">did what they said they were going to do</a>: Slashed a wide variety\n of taxes, some to zero.</p>\n <p>The predicted prosperity failed to happen. The state government’s revenue plunged and it had to dig deep into rainy-day\n reserves just to keep the doors open. There were brutal cuts to policing, road repair, and schools. Also a nasty\n feedback loop: As the state’s fiscal position worsened, its credit rating fell and interest rates rose, leading to yet more\n brutal austerity measures.</p>\n <p>Another result was that affluent Kansans made out like bandits; the cost of running the state was substantially\n transferred to the less financially fortunate.</p>\n <p>In 2017, the legislature threw in their cards and repealed the tax cuts, overriding Brownback’s veto.</p>\n <p>While this was a terrible experience for most Kansans, it is historically useful, because whenever you encounter a\n tax-cut nut (probably self-interestedly wealthy) you can say “But, Kansas!” Having said that, there are still plenty of\n those nuts, and they’ll tell you that the Kansas experiment failed because of one fine-tuning effort or another. That’s a position\n that’s hard to defend, though.</p>\n <h2 id=\"p-3\">Sidebar: Trans oppression too</h2>\n <blockquote><p>Before I move onto the AI angle, I gotta pause to acknowledge this week’s news story about the Kansas\n government’s vicious, brutal, and ignorant\n <a href=\"https://www.theguardian.com/us-news/2026/feb/26/kansas-trans-drivers-license-law-assault-on-rights\">assault on trans\n people</a>. To be clear, I think the shitty people who hate trans folk are aren’t necessarily the same shitty people as the shitty\n people who don’t want to contribute to the public good. But, something about Kansas seems to attract both\n flavors.</p></blockquote>\n <h2 id=\"p-2\">The GenAI experiment</h2>\n <p>The core value proposition of contemporary AI technology is exactly what Dorsey seems to think: Fire half your\n employees and profits will soar! If that’s true, the trillion dollars or so invested so far will seem like small potatoes. Since\n we don’t know if \n this will actually work, anyone who actually does it is conducting an experiment. Just like Sam Brownback did.\n Unsurprisingly, the investor class loves this experiment and is putting their money on it working.</p>\n <p>To be fair, voices have been raised to argue that the tech sector is a special case: That following on\n feverish over-hiring during the Covid lockdown, they need to slash headcount anyhow, and are using AI as an excuse.\n For example\n <a href=\"https://daringfireball.net/linked/2026/02/27/block-layoffs\">John Gruber</a>.</p>\n <p>I personally\n am unconvinced, but even if they’re right, it’s irrelevant. The shareholding class won’t be able to see past that 24% payoff. So \n as of today, they’ll be yelling at every CEO on the planet to start pulling the mass-firing trigger. Or else.</p>\n <p>I think I know how the experiment will turn out. Just like in Kansas, it’s not going to be fun.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/AI",
"term": "Technology/AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "AI",
"term": "AI",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026",
"title": "Crocuses of 2026",
"description": "I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth in early 2003. Except for last year. Because we moved and the new place didn’t have any. Only now it does, and they’re (just barely) up. [Update: Up and open, too.]",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/24/Crocuses-of-2026",
"published": "2026-02-24T20:00:00.000Z",
"updated": "2026-02-26T21:46:17.000Z",
"content": "<p>I’ve run early-spring pictures of these little purple guys almost every year since this blog’s birth\n in early 2003. Except for last year. Because\n <a href=\"/ongoing/When/202x/2025/02/28/Moved\">we moved</a> and the new place didn’t have any. Only now it does, and they’re\n (just barely) up. <i>[Update: Up and open, too.]</i></p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56234.png\" alt=\"Crocuses of February 2026\"></img>\n <p>Long-time followers may note that they’re pale and fragile compared to the exuberant blossoms of previous\n years. Not sure why, but our new place faces north and there’s this enormous\n <a href=\"https://en.wikipedia.org/wiki/Fraxinus_americana\">White Ash</a> tree right in front of it, so they’re not getting as\n much sun as at the south-facing former joint.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56235.png\" alt=\"Crocuses of February 2026\"></img>\n <p>And also this is their first spring. We bought the bulbs and hired a professional with the right tools to jam them\n into the earth last autumn, between the big tree’s roots. So they really haven’t had a chance to get their own root systems going.</p>\n <p>And finally, it really is the first day that’s bright and warm enough to get out the camera. Maybe they’ll\n be better in another few days. And quite likely next Spring.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56244.png\" alt=\"Crocuses of February 2026\"></img>\n <p>This would be the place to introduce whatever metaphor this year’s blossoms, fighting their way through the leaf cover in\n chilly air toward the sun, fit into, but I’m not gonna.</p>\n <p>I, like many, am\n <a href=\"/ongoing/When/202x/2023/10/25/Wild-World\">not dealing very well</a> with what I see when I look at the world in either\n the big or the ultra-local landscapes.\n The world in tough shape and its worst people are making it worse.\n People I love are in ugly corners and not finding help.</p>\n <p>But you know, the flowers, in their low-key way, look great and so does the tree, still in wintersleep. Today the\n sun was shining on them. It’ll be warmer and nicer soon.</p>\n <p>Metaphors can go to hell. It’s just late-winter light on pale violet petals. Enjoy the moments you have with it.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/02/24/TXT56249.png\" alt=\"Spring crocus, now open for business\"></img>\n <div class=\"caption\"><p>Update: Now open for business.</p></div>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Arts/Photos",
"term": "Arts/Photos",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Arts",
"term": "Arts",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Photos",
"term": "Photos",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion",
"title": "Open Source and GenAI?",
"description": "I’ve been puttering away on my Quamina project since 2023. In the last few weeks GenAI has intervened. Quamina + Claude, Case 1 describes a series of Claude-generated human-curated PRs, most of which I’ve now approved and merged. Quamina + Claude, Case 2 considers quamina-rs, a largely-Claude-driven port from Go to Rust. Both of these stories seem to have happy endings and negligible downsides. So empirically, I can apply LLM technology usefully to software development. But should I?",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion",
"published": "2026-02-16T20:00:00.000Z",
"updated": "2026-02-18T21:41:14.000Z",
"content": "<p>I’ve been puttering away on my\n <a href=\"/ongoing/What/Technology/Quamina%20Diary/\">Quamina</a> project since 2023. In the last few weeks GenAI\n has intervened. \n <a href=\"/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1\">Quamina + Claude, Case 1</a> describes a series of\n Claude-generated human-curated PRs, most of which I’ve now approved and merged.\n <a href=\"/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2\">Quamina + Claude, Case 2</a> considers\n <a href=\"https://github.com/baldawarishi/quamina-rs\">quamina-rs</a>, a largely-Claude-driven port from Go to Rust.\n Both of these stories seem to have happy endings and negligible downsides. So empirically, I <em>can</em> apply LLM\n technology usefully to software development. But should I?</p>\n <h2 id=\"p-3\">Conclusions 1: Burn it with fire?</h2>\n <p>Let me be clear: In the big GenAI picture, I’m a contra. Why? I’ll pass the mike to Baldur Bjarnason, my\n favorite among GenAI’s blood enemies.: \n <a href=\"https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/\">“AI” is a dick move</a>.\n His tl;dr is something like “GenAI is environmentally devastating and has the goal of throwing millions of\n knowledge workers onto the street and is being sold by the worst people and is used for horrible applications and will increase\n society’s already-intolerable level of inequality!” To which I reply “Yes, yes, yes, yes, and yes.”</p>\n <p>At the end of the day, the business goal of GenAI is to boost monopolist profits by eliminating decent jobs, and\n damn the consequences. This is a horrifying prospect (although I’m somewhat comforted by my belief that it basically won’t\n work and most of the investment capital is heading straight down the toilet).</p>\n <p>But. All that granted, there’s a plausible case, specifically in software development, for exempting LLMs from this\n loathing.</p> \n <p>First of all, size.\n <a href=\"https://www.jetbrains.com/lp/devecosystem-data-playground/#global_population\">JetBrains thinks</a> that\n the world has 21 million or so software developers, i.e. less than 1% of the earth’s working population.\n Vanishingly small in the context of the lunatic tsumani of LLM overinvestment.\n Training and operating the models required for a market this small is\n rounding error measured on the Great GenAI Overbuild scale. There aren’t enough geeks to create a detectable bump in the global\n carbon load.</p>\n <p>Another odious aspect of LLMs is\n <a href=\"https://en.wikipedia.org/wiki/Reinforcement_learning_from_human_feedback\">RLHF</a>, “Reinforcement Learning From Human\n Feedback”, which relies on underpaying Third-Worlders to \n polish the models’ outputs. \n My guess is that much less is required for code-oriented LLMs. \n The combination of the compiler and your unit tests provide good starter guardrails. Then skilled\n professional intervention is required to deal with the remaining misfires, as with those Quamina PRs.</p>\n <p>Finally, it seems making billionaires into multibillionaires is intrinsic to GenAI dreams. But software-development tools won’t\n do that. Once again, the market is just too small. But even if it weren’t, consider this from Steve Yegge:</p>\n <blockquote><p>For\n <a href=\"https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163\">this blog post</a>, “Claude Code” means “Claude Code and\n all its identical-looking competitors”, i.e. Codex, \n Gemini CLI, Amp, Amazon Q-developer ClI, blah blah, because that’s what they are. Clones.</p></blockquote>\n <p>(GenAI, overbuilding wherever you look.) None of these products have moats and the chance that any of them become\n extractive monopolies is about zilch. Nobody’s ever built a major cash-cow on developer tooling</p>\n <p>One reason is (*gasp*) Open Source. Does anybody doubt that in the near future, there will\n be entirely open-source versions of what Yegge means by “Claude”?</p>\n <p>So, if you want to condemn the use of GenAI in software development, I think you need arguments other than the fact that\n it’s also being promoted for societally-toxic business purposes.</p>\n <p>I have a few. But stand by, let me push that on the stack and turn to\n technology for a bit.</p>\n <h2 id=\"p-4\">Conclusions 2: Engineering sanity?</h2>\n <p>Question: Can LLMs even participate in quality software engineering?\n Baldur doesn’t think so: “The gigantic, impossible to review, pull requests. Commits that are\n all over the place. Tests that don’t test anything. Dependencies that import literal malware. Undergraduate-level security\n issues. Incredibly verbose documentation completely disconnected from reality.”</p>\n <p>I’m not saying that these pathologies can’t or don’t happen. But in my personal experience with Quamina, they\n didn’t. (Mind you, it’s a hobby project.)</p>\n <p>And when they do happen, I would assume that mature open-source projects will use a network of\n trust, as big operations like Linux already do. PRs that don’t have the imprimatur of someone known to be clueful will be ignored.\n When I saw the first of those incoming Quamina PRs, I took the time for a serious look because I knew Rob and had seen evidence that he\n was technically competent. If I see an incoming PR that’s nontrivial and from some rando and doesn’t pass a 120-second sanity\n check, it’s unlikely to get any more attention.</p>\n <p>In fact, some essentials don’t change. If you’re not requiring that PRs be clean and\n test coverage be good and code reviews not be skipped and dependencies be curated, you’re going to get a lousy result whether\n the upstream code is coming from a human or an LLM.</p>\n <p>But it’d be naive to think that a big change in the\n shape of that upstream isn’t going to affect the profession.</p>\n <h2 id=\"p-9\">Bottlenecks</h2>\n <p>Speaking from personal experience, reviewing the PRs from Claude&Rob was neither faster nor slower, easier nor harder,\n than what I’m used to pre-GenAI. The number of my disagreements with the diffs, and the amount of arguing it took to resolve\n them, was also about as usual.\n Which creates a big problem. Because if we can generate code a whole lot faster but review doesn’t\n speed up, all we’ve done is moved the bottleneck in the system.</p>\n <p>Speaking of which, Armin Ronacher offers\n <a href=\"https://lucumr.pocoo.org/2026/2/13/the-final-bottleneck/\">The Final Bottleneck</a>, from which: “When one part of the\n pipeline becomes dramatically faster, you need to throttle input.” Think about that.</p>\n <h2 id=\"p-10\">Burnout</h2>\n <p>Meanwhile, evidence is piling up that LLM-based software development is driving\n developers to overwork and burnout. Here’s\n <a href=\"https://hbr.org/2026/02/ai-doesnt-reduce-work-it-intensifies-it\">a cool-eyed take</a> from <cite>Harvard Business\n Review</cite>. Then there’s Steve Yegge’s frantic, overly-long\n <a href=\"https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163\">The AI Vampire</a>. But my favorite, and I think a\n must-read, is Siddhant Khare’s\n <a href=\"https://siddhantkhare.com/writing/ai-fatigue-is-real\">AI fatigue is real and nobody talks about it</a>.\n From which: “AI reduces the cost of production but increases the cost of coordination, review, and decision-making. And those\n costs fall entirely on the human.”</p>\n <p>The argument we’re hearing is that GenAI makes development more efficient. And more efficient is better.\n <a href=\"https://www.tbray.org/ongoing/When/202x/2020/07/05/Too-Efficient\">Until it’s not</a>.</p>\n <p>I’m not sure the profession I joined last century would attract me today. And on Mastodon,\n <a href=\"https://cosocial.ca/@gordwait/116082229876399512\">@GordWait said</a> “At our office, we are\n noticing a huge drop in Comp Sci co-op applications. The next generation is convinced there’s no future in programming thanks to\n AI hype.”</p>\n <h2 id=\"p-11\">Can and should</h2>\n <p>Here’s another conundrum. Suppose we <em>can</em> build a whole lot more stuff, faster. <em>Should</em> we? I don’t know about you,\n but I am regularly enraged at tools that work just fine popping up “wonderful new features” modals in front of what I’m\n trying to get accomplished. Also at damaging UI churn, driven by product managers trying to get promoted. It’s\n just not obvious \n that speeding up software development is, in the big picture, a good thing.</p>\n <p>And I can’t help noting that every attempt to measure the productivity boost due to GenAI has shown zero (or worse)\n improvement. Of course, Claude’s cheering section will point out that those studies date to 2024 which is the stone age. Maybe\n they’re right.</p>\n <h2 id=\"p-8\">Vampires</h2>\n <p>(In which I once again go all\n <a href=\"/ongoing/When/202x/2023/01/16/Class-Reductionism\">class-reductionist</a>.) The real problem here is late-stage\n capitalism, and I think is best addressed in Yegge’s <cite>AI Vampires</cite> piece, from which I quote: \n “…dollar-signs appear in their <i>[employers’]</i> eyeballs, like cartoon bosses. I know that look. There’s no reasoning with\n the dollar-eyeball stare.” Yeah.</p>\n <p>Thus the ancient question: <i>cui bono?</i> Assuming GenAI genuinely boosts productivity, who gets the\n benefits? Because the ownership class sure doesn’t think they should go to their newly-more-efficient employees.</p>\n <h2 id=\"p-7\">But, what do I know?</h2>\n <p>I know that you gotta have test coverage or your software is an unmaintainable tangle of festering tech debt. I know you gotta\n have code review or your quality is on inexorable downhill drift. I <em>don’t</em> know how to build LLMs into a sane,\n sustainable software engineering culture. Nor what to do \n about capitalism’s AI Vampires.</p>\n <p>And I absolutely do <em>not</em> believe the wild-eyed claims of 10× productivity gains, assuming we demand (as we should) that\n they’re sustainable at scale.</p>\n <p>So, would I advise executives to tell software engineering shops to discard their\n culture in favor of vibe coding in the expectation of monstrous productivity wins? Nope.\n <a href=\"https://simonwillison.net/2025/Oct/7/vibe-engineering/\">Vibe engineering</a>, maybe.\n\n <a href=\"https://locusmag.com/feature/commentary-cory-doctorow-reverse-centaurs/\">Centaurs, not reverse centaurs</a>? Indeed.</p>\n <p>But would I say “Stay away, don’t even look”? Nope. I’d probably suggest pointing the LLM at well-delimited non-strategic\n issues and \n optimizations, and emphasize no shortcuts on reviewing or CI/CD standards.</p>\n <p>Also note that the GenAI apostles are at one in saying that this year’s tools are <em>so</em> much better than last year’s,\n and next year’s are guaranteed to be qualitatively still better! So why would you rush in and risk getting locked into\n soon-to-be-outmoded tooling?</p>\n <p>Rob Sayre wrote “I would never bother to type out these patches by hand. But I read them all.” I probably wouldn’t have\n either and I read them too. And now Quamina is roughly twice as fast. Which is to say, I got good results on a hobby\n project. That’s not nothing.</p>\n <p>But, also not conclusive.\n Once the AI bubble pops and we’ve recovered from the systemic damage, I think there’ll <em>probably</em> be a place for\n open-source LLM automation in developer toolkits.</p>\n <p>But maybe not. Wouldn’t surprise me much, either way.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/AI",
"term": "Technology/AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "AI",
"term": "AI",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2",
"title": "Quamina + Claude, Case 2",
"description": "Last time out I described a bunch of incremental-improvement Quamina PRs from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s quamina-rs, a Claude-based port of Quamina from Go to Rust. The next post is about where I stand on GenAI and code",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2",
"published": "2026-02-14T20:00:00.000Z",
"updated": "2026-02-14T20:00:00.000Z",
"content": "<p><a href=\"/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1\">Last time out</a> I described a bunch of incremental-improvement\n <a href=\"/ongoing/What/Technology/Quamina%20Diary/\">Quamina</a> PRs\n from a colleague working with Claude Opus. Today I want to talk about Rishi Baldawa’s\n <a href=\"https://github.com/baldawarishi/quamina-rs\">quamina-rs</a>, a Claude-based port of Quamina from Go to Rust.\n The next post is about where I stand on GenAI and code.</p>\n <p>Anybody who cares about this kind of thing will appreciate Rishi’s write-ups, starting with\n <a href=\"https://rishi.baldawa.com/posts/the-agents-kept-going/\">The Agents Kept Going</a> (also see\n <a href=\"https://rishi.baldawa.com/posts/scaffolding-for-agent-velocity/\">Scaffolding for Agent Velocity</a>).\n He doesn’t just say what he did, he draws lessons; good ones, I think.</p>\n <h2 id=\"p-1\">Background</h2>\n <p>Rishi and I worked together at AWS, can’t remember the details, but after I left he took over what we called Ruler, now known\n as <a href=\"https://github.com/aws/event-ruler\">aws/event-ruler</a>, Quamina’s ancestor. At the time I left it had been adopted\n by quite a number of AWS and Amazon services and various instances were processing, in aggregate, a remarkable number of\n millions of events per second. So he knows the territory.</p>\n <p>As for quamina-rs, go read his blogs. I’ve got little to add, but here are a couple of juicy quotes: “…at some point while I was\n mindlessly kicking off these sessions, the agents started picking up open issues from the Go version and implementing them on\n their own.“ Also, “And I think that’s the thing worth saying plainly. It’s human to care. Agents don’t care. Automation doesn’t\n care. They need to be told what to care about, and even then they’ll misbehave the moment you look away…”</p>\n <p>Both these stories ended with useful results.\n So empirically, you can get useful results by applying GenAI to the process of code construction.</p>\n <p>Yay. I guess. But there are a lot of smart people who think this whole LLM-fueled coding direction is irremediably toxic.\n\n <a href=\"/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion\">I’m not sure they’re wrong</a>.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/AI",
"term": "Technology/AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "AI",
"term": "AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology/Quamina Diary",
"term": "Technology/Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Quamina Diary",
"term": "Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1",
"title": "Quamina + Claude, Case 1",
"description": "With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any) GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current code playground, Quamina. Here’s the first story. I’m going to go ahead and share it even though it will make people mad at me",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/06/Q-Plus-C-Ch1",
"published": "2026-02-06T20:00:00.000Z",
"updated": "2026-02-06T20:00:00.000Z",
"content": "<p>With 47 years of coding under my belt, and still a fascination for the new shiny, obviously I’m interested what role (if any)\n GenAI is going to play in the future of software. But not interested enough to actually acquire the necessary skills and\n try it out myself. Someday, someday. Didn’t matter; two other people went ahead without asking and applied Claude to my current\n code playground, <a href=\"/ongoing/What/Technology/Quamina%20Diary/\">Quamina</a>. Here’s the first story. I’m going to go\n ahead and share it even though it will make people mad at me.</p>\n <h2 id=\"p-1\">Why share?</h2>\n <p>Because our profession’s debate on this topic is simultaneously ridiculous and toxic. No meaningful dialogue seems possible\n between the\n <a href=\"https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04\">Gas Town</a>-and-<a href=\"https://en.wikipedia.org/wiki/Moltbook\">Moltbook</a>\n faction and the\n <a href=\"https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/\">“AI” is a dick move</a> camp.\n So, I’m not going to join in today. This is pure anecdata: What happened when Rob applied Claude to Quamina. I’m going to \n avoid rhetoric (in the linguistic sense, language designed to convince) and especially polemic (language designed to\n attack). I promise to have conclusions before too long, just not today.</p>\n <h2 id=\"p-2\">What happened was…</h2>\n <p>There’s this guy\n <a href=\"https://github.com/sayrer\">Rob Sayre</a>, I’ve known him for many years, even been in the same room once or twice,\n in the context of IETF work. I’ve never previously collaborated on code with him. Starting in\n mid-January, he’s sent\n <a href=\"https://github.com/timbray/quamina/issues?q=is%3Apr%20author%3Asayrer\">a steady flow of PRs</a>, most of which I\n eventually accept and merge.</p>\n <p>The net result is that Quamina is now roughly twice as fast on several benchmarks designed to measure typical tasks.</p>\n <h2 id=\"p-3\">Technical details</h2>\n <p>The details of what Quamina is and does are in the\n <a href=\"https://github.com/timbray/quamina?tab=readme-ov-file#quamina\">README</a>. For this discussion, let’s ignore everything\n except to say that it’s a Go library and consider its two most important APIs. <code>AddPattern()</code> adds a Pattern (literal or\n regexp) to an instance, and\n <code>MatchesForEvent</code> considers a JSON blob and reports back which Patterns it matched. It’s really fast and the\n relationship is pleasingly weak between the number of Patterns that have been added and the matching speed.</p>\n <p>Quamina is based around finite automata (both deterministic and nondeterministic) and the rest of this technical-details\n section will throw around NFA and DFA jargon, sorry about that.</p>\n <p>For code like this that is neither I/O-bound nor UI-centric, performance is really all about choosing the right\n algorithms. Once you’ve done that, it’s mostly about memory management. Obviously in Quamina, the <code>AddPattern</code> call\n needs to allocate memory to hold the finite automata. But I’d like it if the <code>MatchesForEvent</code> didn’t.</p>\n <p>Go’s only built-in data structures are “map” i.e. hash table, and “slice” i.e. appendable array. (For refugees from Java, with\n its dozens of flavors of lists and hashes, this is initially shocking, but most Go fans come to the conclusion that Go is right\n and Java is wrong.)\n In really well-optimized\n code, you’d like to see all the time spent either in your own logic or in appending to slices and updating maps.</p>\n <p>In less-well-optimized code, the profiler will show you spending horrifying amounts of time in runtime routines whose names\n include “malloc”, and in the garbage collector.\n Now, both maps and slices grow automatically as needed, which is nice, except when you’re trying to minimize allocation.\n It turns out that slices have a <b>capacity</b>, and as long as the number of things you append is less than the capacity, you won’t\n allocate, which is good. Thus, there are two standard tricks in the inventory of 100% of people who’ve optimized Go code:</p>\n <ol>\n <li><p>When you make a new slice, give it enough capacity to hold everything you’re going to be adding to it. Yes, this can\n be hard because you’re probably using it to store input data of unpredictable size, thus…</p></li>\n <li><p>After you’ve made a new slice, keep it around, clear it after each input record, and its capacity will naturally grow\n until it gets to be big enough that it fits all the rest of the records, then you’ll never allocate again.</p></li>\n </ol>\n <h2 id=\"p-4\">Those PRs</h2>\n <p>Background: Quamina is equipped with what I think is a pretty good unit-test suite, and multiple benchmarks.</p>\n <p>I started getting Rob’s PRs and initially, 100% of them were finding ways along both of those well-trodden map-and-slice\n paths, in places where I hadn’t noticed the opportunity. They were decent PRs, well-commented, sensible code, no loss of test\n coverage. After I asked to see benchmark runs to prove the gains weren’t just theoretical, they started including benchmark runs. I’ve\n found a few things to push back on but Rob and I had no problem sorting those out.</p>\n <p>At the end of the day I had no qualms about merging them, but I did find myself wondering how they were built. So I\n asked.</p>\n <h2 id=\"p-6\">Workflow</h2>\n <p>Rob had told me right away on the first one that these were substantially Claude-generated. I asked him for his workflow and part\n of what he said was “I might say\n ‘let's do some profiles of memory and CPU on this benchmark, on main and on this branch.’ It will come up with good and bad\n ideas, then I pick them.”</p>\n <p>Also: “What might be counter-intuitive is that I can context switch really quickly with it. So, you leave a comment, and I\n just tell Claude to fix that, because you are correct. Sometimes I go in and hand edit, but usually it gets close or perfect\n (what they call a \"one-shot\"). But I just have the conversation open, so I just pick up where we left off.”</p>\n <p>Here’s a sample of Claude talking to Rob. You may have to enlarge it.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2026/02/06/claude-says.png\" alt=\"Dialogue with Claude\"></img>\n <h2 id=\"p-7\">Not just the same-old</h2>\n <p>Then I got a surprise, because Claude and Rob spotted two pretty big improvements that aren’t on the standard list.\n First: To traverse an NFA, for each state you have to compute its “epsilon closure”, the set of other states you can get to\n transitively following epsilon transitions. I had already built a cache so that as you computed them, they got remembered.\n C&R pointed out “Epsilon closures are a property of the automaton structure, not the input data. Once a pattern is added and the\n NFA is built, the epsilon closure for any given state is fixed and never changes.” So you might as well compute it and save it\n when you build the NFA.</p>\n <p>This is even better than it sounds, because (for good reasons following from Quamina’s concurrency model) my closure\n caches were per-thread, while the new epsilon closures were global, stored just once for all the threads. Not bad, and not trivial.</p>\n <p>Second, when you’re computing those closures, you have to memo-ize the key functions to avoid getting caught in NFA loops.\n I’d done this with a set, which in Go you implement as <code>map[whatever]bool</code>. R&C figured out that if you gave each\n state a “closure generation” integer field and maintained a global closure-generation value, you could dodge the necessity for the\n set at the cost of one integer per state. The benchmarks proved it worked.</p>\n <p>As I wrote this piece,\n <a href=\"https://github.com/timbray/quamina/pull/491\">another PR arrived</a> with a stimulating title: “kaizen: allocation-free\n on the matching path”.</p>\n <h2 id=\"p-5\">Kaizen?</h2>\n <p>It’s\n <a href=\"https://en.wikipedia.org/wiki/Kaizen\">the idea that</a> you make things substantially better by successively introducing\n small improvements. We try to \n use the term to tag Quamina PRs that change no semantics but just make performance better or more reliable or whatever.</p>\n <h2 id=\"p-8\">But GenAI is bad!?!</h2>\n <p>Yes, so they say. Go re-read that\n <a href=\"https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/\">dick-move</a> polemic.</p>\n <p>But, I’m going to leave this little case study conclusion-free for a bit because there are two follow-up pieces.\n Next,\n <a href=\"/ongoing/When/202x/2026/02/14/Q-Plus-C-Ch2\">the story of quamina-rs</a>, a Claude-drive port of Quamina to Rust.\n Finally, <a href=\"/ongoing/When/202x/2026/02/16/GenAI-and-OSS-opinion\">Open Source and GenAI?</a>.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/AI",
"term": "Technology/AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "AI",
"term": "AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology/Quamina Diary",
"term": "Technology/Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Quamina Diary",
"term": "Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links",
"title": "Long Links",
"description": "Welcome to the first Long Links of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to take in all of these, but there’s a good chance one or two might brighten your day",
"url": "https://www.tbray.org/ongoing/When/202x/2026/02/03/Long-Links",
"published": "2026-02-03T20:00:00.000Z",
"updated": "2026-02-04T22:41:25.000Z",
"content": "<p>Welcome to the first <cite>Long Links</cite> of this so-far-pretty-lousy 2026. I can’t imagine that anyone will have time to\n take in all of these, but there’s a good chance one or two might brighten your day.</p>\n <h2 id=\"p-17\">Unclassified</h2>\n <p>Thomas Piketty is always right. For example,\n <a href=\"https://thomaspiketty.wordpress.com/2026/02/03/europe-a-social-democratic-power/\">Europe, a social-democratic\n power</a>.</p>\n <p>Lying is wrong. Conservatives\n <a href=\"https://thetyee.ca/Opinion/2026/02/02/Today-Conservatives-Misinformation-Norm/\">do it all the time</a>. To be fair,\n that piece is about the capital-C flavor, as in the Canadian Tories. But still.</p>\n\n <p>Clothing is open-source: “If you slice the different parts off with a seamripper, lay them all down, trace them on new\n fabric, cut them out, and stitch them back together, you can effectively clone and fork\n garments.” From\n <a href=\"https://wiki.xxiivv.com/site/devine_lu_linvega.html\">Devine Lu Linvega</a>.</p>\n <p>The Universe is weird. The Webb telescope keeps showing astronomers things that shouldn’t be there. For example,\n <a href=\"https://www.nature.com/articles/s41586-025-09973-1\">An X-ray-emitting protocluster at z ≈ 5.7 reveals rapid structure\n growth</a>; ignore the title and read the Abstract and Main sections. With pretty pictures!</p>\n <h2 id=\"p-2\">Music</h2>\n <p>One time in Vegas, I was giving a speech, something about cloud computing, and was surprised to find the venue an ornate\n velvet-lined theater. I found out from the staff, and then relayed to the audience, that the last human before me to stand on this stage\n in front of an audience had been Willie Nelson. I was tempted to fall to my knees and kiss the boards.\n <a href=\"https://www.newyorker.com/magazine/2025/12/29/willie-nelson-profile\">How Willie Nelson Sees America</a>, from <cite>The\n New Yorker</cite>, is subtitled “On the road with the musician, his band, and his family” but it ends up being the kernel of a\n good biography of an interesting person. Bonus link; on YouTube,\n <a href=\"https://www.youtube.com/watch?v=3WIR3Riq4wM\">Willie Nelson - Teatro, featuring Daniel Lanois & Emmylou Harris,\n Directed by Wim Wenders</a>. Strong stuff.</p>\n <p>Speaking of recorded music, check out\n <a href=\"https://www.dazeddigital.com/music/article/69407/1/why-listening-parties-are-everywhere-right-now-rosalia-album-launch-artist\">Why \n listening parties are everywhere right now</a>. Huh? They are? As a deranged audiophile, sounds like my kind of thing. I’d go.</p>\n <h2 id=\"p-4\">Somewhere to put worker bees</h2>\n <p>When I was working at AWS in downtown Vancouver back starting in 2015, a lot of our junior engineers lived in these\n teeny-tiny little one-room-tbh apartments. It worked out pretty well for them, they were affordable and an easy walk from the\n office and these people hadn’t built up enough of a life to need much more room.\n For a while this trend of\n so-called-“studio” flats was the new hotness in Vancouver and I guess around quite a bit of the developed world.\n Us older types with families would look at the\n condo market and tell each other “this is stupid”.</p>\n <p>We were right. The\n bottom is falling out and they’re sitting empty in their thousands. And not just the teeniest either, the whole\n condo business is in the toilet. It didn’t help that for a few years all the prices went up every year (until they didn’t) and\n you could make serious money flipping unbuilt condos, so lots of people did (until they didn’t).</p>\n <p>Anyhow, here’s a nice write-up on the subject:\n <a href=\"https://www.bbc.com/news/articles/cqxq32zzq8eo\">‘Somewhere to put worker bees’: Why Canada's micro-condos are losing\n their appeal</a>. (From the BBC, huh?)</p>\n <h2 id=\"p-5\">AI AI AI</h2>\n <p>Sorry, I can’t not relay pro- and anti-GenAI posts, because that conversation is affecting all our lives just now. I am\n actually getting ready to decloak my own conclusions, but for the moment I’m just sharing essays on the subject that strike me as\n well-written and enjoyable for their own sake. Thus\n <a href=\"https://www.baldurbjarnason.com/notes/2026/note-on-debating-llm-fans/\">‘AI' is a dick move, redux</a> from Baldur\n Bjarnason. Boy, is he mad.</p>\n <p>Sam Ruby has been doing some\n <a href=\"https://intertwingly.net/blog/2026/01/28/Twilight-Zone.html\">extremely weird shit</a>, running Rails in the browser, as\n in without even a network connection or a Ruby runtime. Yes, AI was involved in the construction.</p>\n <h2 id=\"p-6\">Software</h2>\n <p>There’s this programming language called Ivy that is in the APL lineage; that acronym will leave young’uns blank but a few greying\n eyebrows will have been raised. Anyhow,\n <a href=\"https://commandcenter.blogspot.com/2026/01/implementing-transcendental-functions.html?m=1\">Implementing the\n transcendental functions in Ivy</a> is delightfully geeky, diving deep with no awkwardness. By no less than Rob Pike.</p>\n <p>Check out Mike Swanson’s\n <a href=\"https://blog.mikeswanson.com/backseat-software/\">Backseat Software</a>. That’s “backseat” as in “backseat driver”,\n which today’s commercial software has now, annoyingly, become. This piece doesn’t make any points that I haven’t heard (or made\n myself) elsewhere, but it pulls a lot of the important ones together in a well-written and compelling package. Recommended.</p>\n <p>Old Googler Harry Glaser\n <a href=\"https://www.linkedin.com/posts/harryglaser_i-worked-on-ads-at-google-15-years-ago-when-activity-7423057144402427905-nm3p/\">reacts\n with horror</a> to the introduction of advertising by OpenAI, and makes gloomy predictions about how it will evolve. His predictions\n are obviously correct.</p>\n <p>The title says it:\n <a href=\"https://petapixel.com/2026/01/17/discovering-a-digital-photo-editing-workflow-beyond-adobe/\">Discovering a Digital\n Photo Editing Workflow Beyond Adobe</a>. It’d be a tough transition for me, but the relationship with Adobe gets harder and\n harder to justify.</p>\n <h2 id=\"p-7\">Indigenous reconciliation</h2>\n <p>Khelsilem is one of the loudest and clearest voices coming out of the Squamish nation, one of the larger and better-organized\n Indigenous communities around here.</p>\n <p>There has been a steady drumbeat of Indigenous litigation going on for decades as a\n consequence of the fact that the British colonialists who seized the territory in what we now call British Columbia didn’t\n bother to sign treaties with the people who were already there, they just assumed ownership. The Indigenous people have been\n winning a lot of court cases, which makes people nervous.</p>\n <p>Anyhow, Khelsilem’s\n <a href=\"https://khelsilem.substack.com/p/the-source-of-the-reconciliation\">The Real Source of Canada's Reconciliation Panic</a>\n covers the ground. I’m pretty sure British Columbians should read this, and suspect that anyone in a jurisdiction undergoing similar\n processes should too.</p>\n <h2 id=\"p-8\">Resonant computing, Black and Blue sky</h2>\n <p>There’s this thing called the \n <a href=\"https://resonantcomputing.org\">Resonant Computing Manifesto</a>, whose authors and signatories include names you’d\n probably recognize. Not mine; the first of its Five Principles begins with “In the era of AI…” Also, it is entirely oblivious to\n the force driving the enshittification of social-media platforms: Monopoly ownership and the pathologies of late-stage\n capitalism.</p>\n <p>Having said that, the vision it paints is attractive. And having said <em>that</em>, it’s now featured on the flags waved by\n the proponents of ATProto, which is to say Bluesky. See Mike Masnick’s\n <a href=\"https://www.techdirt.com/2026/01/27/atproto-the-enshittification-killswitch-that-enables-resonant-computing/\">ATproto:\n The Enshittification Killswitch That Enables Resonant Computing</a> (Mike is on Bluesky Corp’s Board). That piece is OK but, in\n the comments, Masnick quickly gets snotty about the Fediverse and Mastodon, in a way that I find really off-putting. And once\n again, says nothing about the underlying economic realities that poison today’s platforms.</p>\n <p>I want to like Bluesky, but I’m just too paranoid and cynical about money. It is entirely unclear who is funding the people\n and infrastructure behind Bluesky, which matters, because if Bluesky Corp goes belly-up, so does the allegedly-decentralized service.</p>\n <p>On the other hand,\n <a href=\"https://blackskyweb.xyz\">Blacksky</a> is interesting. They are trying to prove that ATProto really can be made\n decentralized in fact not just in theory.\n <a href=\"https://blackskyweb.xyz/overview/\">Their ideas and their people</a> are stimulating, and their\n <a href=\"https://opencollective.com/blacksky\">finances are transparent</a>. I’ll be\n <a href=\"https://docs.blacksky.community/migrating-to-blacksky-pds-complete-guide\">moving my ATProto presence to Blacksky</a>\n when I get some cycles and the process has become a little more automated.</p>\n <h2 id=\"p-14\">Good crypto</h2>\n <p>The cryptography community is working hard on the problem of what happens should quantum computers ever become real products as\n opposed to over-invested fever dreams. Because if they ever work, they can probably crack the algorithms that we’ve been using\n to provide basic Web privacy.</p>\n <p>The problem is technically\n hard<span class=\"dashes\"> —</span> there are good solutions though<span class=\"dashes\"> —</span> and also politically fraught,\n because maybe the designers or standards orgs are corrupt or incompetent. It’s reasonable to worry about this stuff and people\n do. They probably don’t need to: Sophie Schmieg dives deep in\n <a href=\"https://keymaterial.net/2025/11/27/ml-kem-mythbusting/\">ML-KEM Mythbusting</a>.</p>\n <h2 id=\"p-16\">Books</h2>\n <p>Here’s one of the most heartwarming things I’ve read in months:\n <a href=\"https://blog.openlibrary.org/2026/01/30/a-community-curated-nancy-drew-collection/\">A Community-Curated Nancy Drew\n Collection</a>. Reminder: The Internet can still be great.</p>\n <p>John Lanchester’s\n <a href=\"https://www.lrb.co.uk/the-paper/v46/n17/john-lanchester/for-every-winner-a-loser\">For Every Winner a Loser</a>,\n ostensibly a review of two books about famous financiers, is in fact an extended howl of\n (extremely instructive) rage against the\n financialization of everything and the unrelenting increase in inequality. What we need to do is to take the ill-gotten gains\n away from these people and put it to a use<span class=\"dashes\"> —</span> any use<span class=\"dashes\"> —</span> that improves\n human lives.</p>\n <p>I talk a lot about late-stage capitalism. But Sven Beckert published a\n <a href=\"https://www.nytimes.com/2025/11/26/books/review/capitalism-sven-beckert.html?searchResultPosition=1\">1,300-page monster entitled <cite>Capitalism</cite></a>;\n the link is to a <cite>NYT</cite> review and makes me want to read it..</p>\n <p>Charlie Stross, the sci-fi author, likes webtoons and\n <a href=\"https://www.antipope.org/charlie/blog-static/2025/12/webtoons-revisited.html\">recommends a bunch</a>. Be careful, do\n not follow those links if you’re already short of time. Semi- or fully-retired? Go ahead!</p>\n <p>I have history with dictionaries. For several years of my life in the late Eighties, I was the research project manager for\n the\n <a href=\"https://cs.uwaterloo.ca/~fwtompa/newoed-project.html\">New Oxford English Dictionary</a> project at the University of\n Waterloo. Dictionaries are a fascinating topic and, for much of the history of the publishing industry, were big money-makers;\n they dominate any short list of the biggest-selling books in history. Then came the Internet.</p>\n <p>Anyhow, Louis Menand’s\n <a href=\"https://www.newyorker.com/magazine/2025/12/29/unabridged-the-thrill-of-and-threat-to-the-modern-dictionary-stefan-fatsis-book-review\">Is\n the Dictionary Done For?</a> starts with a review of a book by Stefan Fatsis entitled <cite>Unabridged: The Thrill of (and\n Threat to) the Modern Dictionary</cite> which I haven’t read and probably won’t, but oh boy, Menand’s piece is big and rich and\n polished and just a fantastic read. If, that is, you care about words and languages. I understand there are those who don’t, which is\n weird. I’ll close with a quote from Menand:</p>\n <blockquote><p>“The dictionary projects permanence,” Fatsis concludes, “but the language is Jell-O, slippery and mutable and\n forever collapsing on itself.” He’s right, of course. Language is our fishbowl. We created it and now we’re forever trapped\n inside it.</p></blockquote>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "The World",
"term": "The World",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "The World",
"term": "The World",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0",
"title": "Quamina v2.0.0",
"description": "There’ve been a few bugfixes and optimizations since 1.5, but the headline is: Quamina now knows regular expressions. This is roughly the fourth anniversary of the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and other tech enthusiasms.) Open-source software, it’s a damn fine hobby",
"url": "https://www.tbray.org/ongoing/When/202x/2026/01/20/Quamina-2.0",
"published": "2026-01-20T20:00:00.000Z",
"updated": "2026-01-21T23:27:06.000Z",
"content": "<p>There’ve been a few bugfixes and optimizations since 1.5, but the headline is:\n <a href=\"https://github.com/timbray/quamina?tab=readme-ov-file#quamina\">Quamina</a>\n now knows regular expressions. This is roughly the fourth anniversary of\n the first check-in and the third of v1.0.0. (But I’ve been distracted by family health issues and\n other tech enthusiasms.)\n Open-source software, it’s a damn fine\n hobby.</p>\n <p>Did I mention optimizations? There are <i>(sob)</i> also regressions; introducing REs had\n measurable negative impacts on other parts of the system.\n But it’s a good trade-off. When you ship software that’s designed for pattern-matching, it should\n really do REs. The RE story, about a year long, can be read starting\n <a href=\"/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series\">here</a>.</p>\n <h2 id=\"p-4\">Quamina facts</h2>\n <ol>\n <li><p>About 18K lines of code (excluding generated code), 12K of which are unit tests. The RE feature makes the tests run\n slower, which is annoying.</p></li>\n <li><p>Adding Quamina to your app will bulk your executable size up by about 100K, largely due\n to Unicode tables.</p></li>\n <li><p>There are a few shreds of AI-assisted code, none of much importance.</p></li>\n <li><p>A Quamina instance can match incoming data records on my 2023 M2 Mac at millions per\n second without much dependence on how many patterns are being matched at once. This assumes\n not too many horrible regular expressions. That’s per-thread of course, and Quamina does\n multithreading nicely.</p></li> \n </ol>\n <h2 id=\"p-1\">Next?</h2>\n <p>The\n <a href=\"https://github.com/timbray/quamina/issues\">open issues</a> are modest in number but\n some of them will be hard.</p>\n <p>I think I’m going to ignore that list for a while (PRs welcome, of course) and work on\n optimization. The introduction \n of epsilon transitions was required for regular expressions, but they really bog the matching\n process down. At Quamina’s core is the\n <a href=\"/ongoing/When/202x/2024/07/28/Union-of-Finite-Automata\">finite-automaton merge</a> logic,\n which contains fairly elegant code but generally throws up its hands when confronted with\n epsilons and does the simplest thing that could possibly work. Sometimes at an annoyingly slow pace.</p>\n <p>Having said that, to optimize you need a good benchmark that pressures the\n software-under-test.\n Which is tricky, because Quamina is so fast that it’s hard to\n to feed it enough data to stress it without the feed-the-data code dominating\n the runtime and memory use. If anybody has a bright idea for how to pull together a good\n benchmark I’d love to hear it. I’m looking at\n <a href=\"https://go.dev/blog/testing-b-loop\">b.Loop()</a> in Go 1.24, any reason not to go there?</p>\n <h2 id=\"p-3\">Book?</h2>\n <p>It occurs to me that as I’ve wrestled with the hard parts of Quamina, I’ve done the obvious\n thing and trawled the Web for narratives and advice. And, more or less, been disappointed. Yes,\n there are many lectures and blogs and so on about this or that aspect of finite automata, but\n they tend to be mathemagical and theoretical and say little about how, practically speaking,\n you’d write code to do what they’re talking about.</p>\n <p>The Quamina-diary <span class=\"o\">ongoing</span> posts now contain several tens of thousands\n of words. Also I’ve previously written\n <a href=\"/ongoing/When/200x/2006/04/18/XML-Grammar\">quite a bit</a> about Lark, the world’s\n first XML parser, which I wrote and was automaton-based. So I think there’s a case for a slim\n volume entitled something like <cite>Finite-state Automata in the Code Trenches</cite>. It’d be\n a big money-maker, I betcha. I mean, when Apple TV brings it to the screen.</p>\n <h2 id=\"p-2\">Why?</h2>\n <p>Let’s be honest. While\n <a href=\"https://github.com/timbray/quamina\">the repo</a> has quite a few stars, I truly have no idea who’s\n using Quamina in production. So I can’t honestly claim that this work is making the\n world better along any measurable dimension.</p>\n <p>I don’t much care because I just can’t help it. I love executable abstractions for their own sake.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/Quamina Diary",
"term": "Technology/Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Quamina Diary",
"term": "Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties",
"title": "Losing 1½ Million Lines of Go",
"description": "Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support character-property regexp features in Quamina. Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this is about (among other things) avoiding those 1½M lines. And really only of interest to people whose pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I think I should maybe have used",
"url": "https://www.tbray.org/ongoing/When/202x/2026/01/14/Unicode-Properties",
"published": "2026-01-14T20:00:00.000Z",
"updated": "2026-01-14T23:52:47.000Z",
"content": "<p>Confession: My title is clickbait-y, this is really about building on the Unicode Character Database to support\n character-property regexp features in\n <a href=\"https://github.com/timbray/quamina\">Quamina</a>.\n Just halfway there, I’d already got to 775K lines of generated code so I abandoned that particular approach. Thus, this\n is about (among other things) <em>avoiding</em> those 1½M lines. And really only of interest to people whose\n pedantry includes some combination of Unicode, Go programming, and automaton wrangling. Oh, and GenAI, which (*gasp*) I\n think I should maybe have used.</p>\n <h2 id=\"p-1\">Character property matching</h2>\n <p>I’m talking about regexp incantations like <code>[\\p{L}\\p{Zs}\\p{Nd}]</code>, which matches anything that Unicode classifies\n as a letter, a space, or a decimal number. (Of course, in Quamina “<code>\\</code>” is “<code>~</code>”\n <a href=\"/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series#p-7\">for excellent reasons</a>, so that reads\n <code>[~p{L}~p{Zs}~p{Nd}]</code>.)</p>\n <p>(I’m writing about this now because I just launched\n <a href=\"https://github.com/timbray/quamina/pull/465\">a PR</a> to enable this feature. Just one more to go before I can\n release a new version of Quamina with full regexp support, yay.)</p>\n <h2 id=\"p-3\">Finding the properties</h2>\n <p>To build an automaton that matches something like that, you have to find out what the character properties are.\n This information comes from the\n <a href=\"https://www.unicode.org/ucd/\">Unicode Character Database</a>, helpfully provided online by the Unicode consortium.\n Of course, most programming languages have libraries that will help you out, and\n <a href=\"https://pkg.go.dev/unicode#pkg-variables\">that includes Go</a>, but I didn’t use it.</p>\n <p>Unfortunately, Go’s library doesn’t get updated every time Unicode does. As of now, January 2026,\n it’s still stuck at Unicode 15.0.0, which\n <a href=\"https://www.unicode.org/history/publicationdates.html\">dates to September 2023</a>; the latest version is 17.0.0, last\n September. Which means there are plenty of Unicode characters Go doesn’t know about, and I didn’t want Quamina to settle\n for that.</p>\n <p>So, I fetched and parsed the famous master file from\n <a href=\"https://www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt\">www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt</a>.\n Not exactly rocket science, it’s a flat file with <code>;</code>-delimited fields, of which I only cared about the first\n and third. There are some funky bits, such as the pair of nonstandard lines indicating that the Han characters occur\n between U+4E00 and U+9FFF inclusive; but still not really taxing.</p>\n <p>The output is, for each Unicode category, and also for each category’s complement (<code>~P{L}</code> matches everything\n that’s <em>not</em> a letter; note the capital <code>P</code>), a list of pairs of code points, each pair indicating a subset\n of the code space where that category applies. For example, here’s the first line of character pairs with category <code>C</code>.</p>\n <pre><code> {0x0020, 0x007e}, {0x00a0, 0x00ac}, {0x00ae, 0x0377},</code></pre>\n <p>How many pairs of characters, you might wonder? There are 37 categories\n and it’s all over the place but adds up to a lot. The top three categories\n are L with 1,945 pairs, Ll at 664, and M at 563. At the other end are Zl and Zp, both with just 1.\n The total number of pairs is 14,811, and the generated Go code is a mere 5,122 lines.</p>\n <h2 id=\"p-5\">Character-property automata</h2>\n <p>Turning these creations into finite automata was straightforward: I already had the code to handle regexps like\n <code>[a-zA-Z0-9]</code>, logically speaking the same problem. But, um, it wasn’t fast. My favorite unit test, an exercise in\n <a href=\"/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1\">sample-driven development</a> with 992 regexps,\n suddenly started taking multiple seconds, and my whole unit-test suite expanded from around ten seconds to over twelve; since I\n tend to run the unit tests every time I take a sip of coffee or scratch my head or whatever, this was painful. And it occurred to\n me that it would be painful in practice to people who want for some good reason or another to load up a bunch of\n Unicode-property patterns into a Quamina instance.</p>\n <p>So, I said to myself, I’ll just precompute all the automata and serialize them into code. And now we\n get to the title of this essay; my data structure is a bit messy and ad-hoc and just for the categories, before I got to the\n complement versions, I was generating 775K lines of code.</p>\n <p>Which worked! But, it was 12M in size and while Go’s runtime is fast, there was a painful pause while it absorbed those data\n structures on startup. Also, opening the generated file regularly caused my IDE\n (<a href=\"https://www.jetbrains.com/go/\">Goland</a>) to crash. And I was only halfway there. The whole approach was painful to\n work with so I went looking for Plan B.</p>\n <p>The code that generates the automaton from the code point pairs is pretty well the simplest thing that could possibly work\n and it was easy to understand but burned memory like crazy. So I worked for a bit on making it faster and\n cheaper, but so far have found no low-hanging fruit.</p>\n <p>I haven’t given up on that yet. But in the meantime, I remembered \n Computer Science’s general solution for all performance problems, by which I mean caching. So now, any Quamina instance will\n compute the automaton for a Unicode property the first time it’s used, then remember it. So now Quamina’s speed at adding\n Unicode-property regexps to an instance has increased from 135/second to 4,330, a factor of thirty and Good Enough For\n Rock-n-Roll.</p>\n <p>It’s worth pointing out that while <em>building</em> these automata is a heavyweight process, Quamina can use them to match\n input messages at its typical rates, hundreds of thousands to millions per second. Sure, these automata are “wide”, with lots of\n branches, but they’re also shallow, since they run on UTF-8 encoded characters whose maximum length is four and average length\n is much less. Most times you only have to take one or two of those many branches to match or fail.</p>\n <h2 id=\"p-2\">Should I have used Claude?</h2>\n <p>This particular segment of the Quamina project included some <em>extremely</em> routine programming tasks, for example\n fetching and parsing\n UnicodeData.txt, computing the sets of pairs, generating Go code to serialize the automata, reorganizing source files that had\n become bloated and misshapen, and writing unit tests to confirm the results were correct.</p>\n <p>Based on my own\n <a href=\"/ongoing/When/202x/2025/07/01/First-AI-Code\">very limited experience</a> with GenAI code, and in particular after\n reading Marc Brooker’s\n <a href=\"https://brooker.co.za/blog/2025/12/16/natural-language.html\">On the success of ‘natural language programming’</a> and\n Salvatore (“antirez”) Sanfilippo’s\n <a href=\"https://antirez.com/news/158\">Don't fall into the anti-AI hype</a>, I guess I’ve joined the camp that thinks\n this stuff is going to have a place in most developers’ toolboxes.</p>\n <p>I think Claude could have done all that boring stuff, including acceptable unit tests, way faster than I did.\n And furthermore got it right the first time, which I didn’t.</p>\n <p>So why didn’t I use Claude? Because I don’t have the tooling set up and I was impatient and didn’t want to invest the time in\n getting all that stuff going and improving my prompting skills. Which reminds me of all the times I’ve been trying to evangelize other\n developers on a better way to do things and was greeted by something along the lines of “Fine, but I’m too busy right now, I’ll\n just going on doing things the way I already know how to.”</p>\n <p>Does this mean I’m joining the “GenAI is the future and our investments will pay off!” mob? Not in the slightest. I still\n think it’s overpriced, overhyped, and mostly ill-suited to the business applications that “thought leaders” claim for it.\n That word “mostly” excludes the domain of code; as I said\n <a href=\"/ongoing/When/202x/2025/09/26/GenAI-Predictions#p-5\">here</a>, “It’s pretty obvious that LLMs are better at predicting code\n sequences than human language.”</p>\n <p>And, as it turns out, the domain of Developer Tools has never been a Big Business by the standards of GenAI’s promoters. Nor\n will it ever be; there just aren’t enough of us. Also, I suspect it’ll be reasonably easy in the near future for open-source\n models and agents to duplicate the capabilities of Claude and its ilk.</p>\n <p>Speaking personally, I can’t wait for the bubble to pop.</p>\n <h2 id=\"p-4\">Quamina.next?</h2>\n <p>After I ship the numeric-quantifier feature, e.g. <code>a{2-5}</code>, Quamina’s regexp support will be complete and if no\n horrid bugs pop up I’ll pretty quickly release Quamina 2.0. Regexps in pattern-matching software are a qualitative difference-maker. \n After that I dunno, there are lots more interesting features to add.</p>\n <p>Unfortunately, a couple years into my Quamina work, I got distracted by life and by other projects, and ignored it. One\n result is that so did the other people who’d made major contributions and provided PR reviews. I miss them and it’s less fun\n now. We’ll see.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/Quamina Diary",
"term": "Technology/Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Quamina Diary",
"term": "Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026",
"title": "Regexp Lessons",
"description": "I’m just landing a chonky PR in Quamina whose effect is to enable the + and * regexp features. As in my last chapter, this is a disorderly war story not an essay, and probably not of general interest. But as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are dozens of us)",
"url": "https://www.tbray.org/ongoing/When/202x/2026/01/01/Quamina-2026",
"published": "2026-01-01T20:00:00.000Z",
"updated": "2026-01-06T18:19:29.000Z",
"content": "<p>I’m just landing a\n <a href=\"https://github.com/timbray/quamina/pull/461\">chonky PR</a> in\n <a href=\"https://github.com/timbray/quamina\">Quamina</a> whose effect is to enable the <code>+</code> and <code>*</code> regexp\n features. As in my\n <a href=\"/ongoing/When/202x/2025/07/21/Automaton-merge-war\">last chapter</a>, this is a disorderly war story not an essay, and\n probably not of general interest. But\n as I said then, the people who care about coercing finite automata into doing useful things at scale are My People (there are\n <em>dozens</em> of us).</p>\n <h2 id=\"p-5\">2014-2026</h2>\n <p>As I write this, I’m sitting in the same couch in my Mom’s living room in Saskatchewan where, on my first Christmas after\n joining AWS, I got the first-ever iteration of this software to work. That embryo’s mature form is available to the world as\n <a href=\"https://github.com/aws/event-ruler\">aws/event-ruler</a>. (Thanks, AWS!) Quamina is its direct descendent, which means\n this story is entering its twelfth year.</p> \n <p>Mom is now 95 and good company despite her failing memory. I’ve also arrived at a qualitatively later stage of life than in\n 2014, but would like to report back from this poorly-lit and often painful landscape: Executable abstractions are still fun,\n even when you’re old.</p>\n <p>Anyhow, the reason I’m writing all this stuff isn’t to expound on the nature of finite automata or regular expressions, it’s\n to pass on lessons from implementing them.</p>\n <h2 id=\"p-8\">Lesson: Seek out samples</h2>\n <p>In a previous episode I used the phrase\n <a href=\"/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1\">Sample-driven development</a> to describe my luck in\n digging up 992 regexp test cases, which reduced task task from intimidating to approachable.\n I’ve never previously had the luxury of wading into a big software task armed with loads of test cases written by other\n people, and I can’t recommend it enough. Obviously you’re not always going to dig this sort of stuff up, but give it a sincere\n effort.</p>\n <h2 id=\"p-9\">Lesson: Break up deliverables</h2>\n <p>I decomposed regular expressions into ten unique features, created an enumerated type to identify them, and implemented them\n by ones and twos. \n Several of the feature releases used\n techniques that turned out to be inefficient or just wrong when it came to subsequent features. But they worked,\n they were useful, and my errors nearly all taught me useful lessons.</p>\n <p>Having said that, here’s some cool output that combines this lesson and the one above, from the unit test that runs \n those test cases. Each case has a regexp then one \n or more samples each of strings that should and shouldn’t match. I instrumented the test to report the usage of regexp features\n in the match and non-match cases.</p>\n <pre>Feature match test counts:\n 32 '*' zero-or-more matcher\n 27 () parenthetized group\n 48 []-enclosed character-class matcher\n 7 '.' single-character matcher\n 29 |-separated logical alternatives\n 16 '?' optional matcher\n 29 '+' one-or-more matcher\n \nFeature non-match test counts:\n 45 '+' one-or-more matcher\n 24 '*' zero-or-more matcher\n 31 () parenthetized group\n 49 []-enclosed character-class matcher\n 6 '.' single-character matcher\n 32 |-separated logical alternatives\n 21 '?' optional matcher</pre>\n <p> Of course, since most of the tests combine multiple features, the numbers for all the features\n get bigger each time I implement a new one. Very confidence-building.</p>\n <h2 id=\"p-2\">Lesson: Thompson’s construction</h2>\n <p>This is the classic nineteen-sixties regular-expression implementation by Ken Thompson, described in Wikipedia\n <a href=\"https://en.wikipedia.org/wiki/Thompson%27s_construction\">here</a> and (for me at least) more usefully, in a\n storytelling style by Russ Cox,\n <a href=\"https://swtch.com/%7Ersc/regexp/regexp1.html\">here</a>.</p>\n <p>On several occasions I rushed ahead and implemented a feature without checking those sources, because how hard could it be?\n In nearly every case, I had problems with that first cut and then after I went and consulted the oracle, I could see where I’d\n gone wrong and how to fix it.</p>\n <p>So big thanks, Ken and Russ.</p>\n <h2 id=\"p-3\">Lesson: List crushing</h2>\n <p>In some particularly nasty regular expressions that\n combine <code>[]</code> and <code>?</code> and <code>+</code> and <code>*</code>, you can\n get multiple states connected in complicated ways with epsilon links.</p>\n <p>In Thompson’s Construction, traversing an NFA transitions not just from one state to another but from a current set of states\n to a next set, repeat until you match or fail. You also compute epsilon closures as you go along; I’m skipping over details\n here. The problem was that traversing these pathologically complex regexps with a sufficiently long string was leading to an\n exponential explosion in the current-states and next-states sizes<span class=\"dashes\"> —</span> not a figure of speech, I mean\n <code>O(2<sup>N</sup>)</code>. And despite the usage of the word “set” above, these weren’t, they contained endless\n duplicates.</p>\n <p>The <em>best</em> solution would be to study the traversal algorithm and improve it so it didn’t emit fountains of dupes. That\n would be hard. The next-best would to turn these things into actual de-duped sets, but that would require a hash table right in\n the middle of the traversal hot spot, and be expensive.</p>\n <p>So what I did was to detect whenever the next-steps list got to be longer than N, sorted it, and crushed out all the dupes.\n As I write, N is now 500 based on running benchmarks and finding a value that makes number go down.</p>\n <p>The reason this is good engineering is that the condition where you have to crush the list almost never happens, so in the\n vast majority of cases the the only cost is an <code>if len(nextSteps)>N</code> comparison. Some may find this approach\n impure, and they have a point. I would at some point like to go back and find a better upstream approach. But for now it’s still\n really fast in practice, so I sleep soundly.</p>\n <h2 id=\"p-4\">Lesson: Hell’s benchmark</h2>\n <p>I’ve\n <a href=\"/ongoing/When/202x/2025/07/21/Automaton-merge-war#p-1\">written before</a> about my struggles with the benchmark where I\n merge 12,959 wildcard patterns together. Back before I was doing epsilon processing correctly, I had a kludgey implementation\n that could match patterns in the merged FA at typical Quamina speeds, hundreds of thousands per second. With correct epsilon\n general-purpose epsilon handling, I have so far not been smart enough to find a way to preserve that performance. With the full\n 13K patterns, Quamina matches at less than 2K/second, and with a mere thousand, at 16K/second. I spent literally days\n trying to get better results, but decided that it was more valuable to Quamina to handle a large subset of regular expressions\n correctly than to run idiotically large merges at full speed.</p>\n <p>I’m pretty sure that given enough time and consideration, I’ll be able to make it better. Or maybe someone else who’s smarter\n than me can manage it.</p>\n <h2 id=\"p-11\">Question: What next?</h2>\n <p>The still-unimplemented regexp features are:</p>\n <pre>{lo,hi} : occurrence-count matcher\n~p{} : Unicode property matcher\n~P{} : Unicode property-complement matcher\n[^] : complementary character-class matcher</pre>\n <p>Now I’m wondering what to do next. <code>[^]</code> is pretty easy I think and is useful, also I get to invert a\n state-transition table. The\n <code>{lo,hi}</code> idiom shouldn’t be hard but I’ve been using regexps for longer than most of you have been alive and have\n never felt the need for it, thus I don’t feel much urgency. The Unicode properties I think have a good fun factor just because\n processing the Unicode character database tables is cool. And, I’ve used them.</p>\n <p><i>[Update: the <code>[^]</code> thing took a grand total of a couple of hours to build and test. Hmm, what next?]</i></p>\n <h2 id=\"p-10\">Lesson: Coding while aging</h2>\n <p>I tell people I keep working on code for the sake of preserving my mental fitness. But mostly I do it for fun. Same for\n writing about it. So, thanks for reading.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/Quamina Diary",
"term": "Technology/Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Quamina Diary",
"term": "Quamina Diary",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing",
"title": "Humanist Plumbing",
"description": "What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage capitalism. These days, that’s almost always a story worth telling",
"url": "https://www.tbray.org/ongoing/When/202x/2025/12/18/Humanist-Plumbing",
"published": "2025-12-18T20:00:00.000Z",
"updated": "2025-12-20T18:40:20.000Z",
"content": "<p>What happened was, a faucet started dripping. And then I managed to route around the malignant machineries of late-stage\n capitalism. These days, that’s almost always a story worth telling.</p>\n <p>Normally, faced with a drip,\n we’d pull out the old cartridge, take it to the hardware store, and buy another to swap in.\n But the fixture in our\n <a href=\"/ongoing/When/202x/2025/02/28/Moved\">recently-acquired</a> place was kind of exotic and abstract and neither of us\n could figure it out. We were gloomy because we’ve had terrible luck over the years with the local plumbing storefronts.\n So…</p>\n <h2 id=\"p-1\">The neighbors</h2>\n <p>Our neighborhood has an online chat; both sides of the streets in a square around a single city block. This is our first\n experience with such a thing. I gather that these don’t always work out well, but this one has been mostly pretty great.</p>\n <p>So at 9AM I posted “Hey folks, looking for a plumber recommendation” and by ten there were three.</p>\n <p><i>[Late-stage capital: “You’re supposed to ask the AI in your browser. It’ll \n provide a handy link to a vendor based on geography and reviews but mostly advertising spend.\n Why would you want to talk to other people?”]</i></p>\n <h2 id=\"p-2\">Thomas</h2>\n <p>I picked a neighbor’s suggestion, first name\n Thomas, and called the number. “Thomas here” on the second ring. I explained and he said “What’s the brand name? If\n it’s one of those Chinese no-names I probably have to replace the whole thing.” I said “No idea, but I’ll take a picture and send it to\n you.”</p>\n <p>Turns out the brand was\n <a href=\"https://riobel.design/en/\">Riobel</a>, never heard of them. I texted Thomas a picture and he got right back to me: “That’s\n high-end, it’s got a lifetime warranty. I’ll come by a little after 5 and take it out. Their dealer is in PoCo (an outer suburb)\n and I live out there, so I can swap it.”</p>\n <p><i>[Late-stage capital: “You’re supposed to engage with the chatbot on the site we sent you to, which will integrate with your\n calendar and arrange for a diagnostic visit a week from Wednesday. You could call them but you’d be in voice-menu hell and\n eventually end up at the same chatbot.”]</i></p>\n <p>When Thomas showed up, with a sidekick, he was affable and obviously competent.\n Within five minutes I was glad I’d called for help; that faucet’s construction was highly non-obvious. Thomas knew what he was\n doing and it still took him the best part of a half-hour to get it all disassembled and the cartridge extracted.</p>\n <h2 id=\"p-6\">Nothing’s perfect</h2>\n <p>The next morning, a text from Thomas: “Bad news. That part is back-ordered till May at Riobel’s dealer. We can maybe get it \n online but you’d have to pay.” He attached a screenie of a Web search for the part number; there were several online\n vendors.</p>\n <p>It’s irritating that the “lifetime warranty” doesn’t seem to be helping me, but to be fair, the part was initially installed\n in 2011.</p>\n <p><i>[Late-stage capital: “Lifetime warranty? Huh? Oh, of course you mean our VIP-class\n subscription offering, that’s monthly with a\n discount for annual up-front payment.”</i> (And the part would still be back-ordered.)]</p>\n <h2 id=\"p-3\">Kolani</h2>\n <p>High-end plumbing parts are expensive. But one of Thomas’ recommendations,\n <a href=\"https://kolani.ca\">Kolani Kitchen and bath</a>, was asking less.</p>\n <p>They had a phone number on their\n Web site so I called it and the voice menu only had three options: Location, opening hours, and Operator.\n The operator was an intelligent human and picked up right away.\n “Hi, I’m looking at ordering a cartridge and wanted to see if you had it in stock.” “Gimme the part number?” I\n did and she went away for a couple of minutes and came back “Yeah, it’s in stock.” So I ordered it and I have a tracking\n number.</p>\n <p><i>[Late-stage capital: “There aren’t supposed to be independent dealers; the manufacturer has taken PE money and eliminated \n the middlemen to better capture all the value-add.\n Or maybe there’ll be a wholesaler, but just one, because another PE rolled up all the distributors to maximize pricing power.\n Either way, you won’t be able to get a human on the line.”]</i></p>\n <h2 id=\"p-7\">Payment</h2>\n <p>Next morning, I got an email that my order had been canceled. So I called that intelligent operator and she said “I was going\n to email you. Our system won’t take payment if the billing and delivery addresses are different. Sorry. If you’re in a hurry you\n could do an e-transfer?” (In Canada, all the banks are in a payments federation that makes this dead easy.) So I\n did and the part has shipped.</p>\n <p><i>[Late-stage capital: “What? If you’d used our Integrated online payment offering, it would all just work. What if it\n doesn’t, you ask? Yeah, sucks to be you in that situation, of course there’d be nobody you could talk to about that.”]</i></p>\n <p>Thomas came by again to put the old cartridge back in for now and said “This thing, don’t worry about a drip, it’s not fast\n and it probably won’t get worse. Text me when the new part gets in.”</p>\n <h2 id=\"p-5\">Late-stage capitalism</h2>\n <p>It won’t be missed when it’s gone.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Business",
"term": "Business",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Business",
"term": "Business",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble",
"title": "After the Bubble",
"description": "The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the damage will be and what the hangover will feel like. On that basis, I was going to post a link on Mastodon to Paul Krugman’s Talking With Paul Kedrosky. It’s great, but while I was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.” So consider this a preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go read that",
"url": "https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble",
"published": "2025-12-07T20:00:00.000Z",
"updated": "2025-12-09T23:29:05.000Z",
"content": "<p>The GenAI bubble is going to pop. Everyone knows that. To me, the urgent and interesting questions are how widespread the\n damage will be and what the hangover will feel like.\n On that basis, I was going to post a link on Mastodon to Paul Krugman’s \n <a href=\"https://paulkrugman.substack.com/p/talking-with-paul-kedrosky\">Talking With Paul Kedrosky</a>. It’s great, but while I\n was reading it I thought “This is going to be Greek to people who haven’t been watching the bubble details.”\n So consider this a\n preface to the Krugman-Kedrosky piece. If you already know about the GPU-fragility and SPV-voodoo issues, just skip this and go\n read that.</p>\n <h2 id=\"p-2\">Depreciation</h2>\n <p>When companies buy expensive stuff, for accounting purposes they pretend they haven’t spent the money; instead they\n “depreciate” it over a few years. That is to say, if you spent a million bucks on a piece of gear and decided to depreciate it\n over four years, your annual financials would show four annual charges of $250K.\n Management gets to pick your depreciation period, which provides a major opening\n for creative accounting when the boss wants to make things look better or worse than they are.</p>\n <p>Even when you’re perfectly honest it can be hard to choose a fair figure. I can remember one of the big\n cloud vendors announcing they were going to change their fleet depreciation from three to four years and that having an impact on\n their share price.</p>\n <p>Depreciation is orderly whether or not it matches reality: anyone who runs a data center can tell you about racks with 20\n systems in them that have been running fine since 2012. Still, orderly is good.</p>\n <p>In the world of LLMs, depreciation is different. When you’re doing huge model-building tasks, you’re running\n those expensive GPUs flat out and red hot for days on end. Apparently they don’t like that, and flame out way more often than\n conventional computer equipment. Nobody who is doing this is willing to come clean with hard numbers but there are data points, for\n example from\n <a href=\"https://www.tomshardware.com/tech-industry/artificial-intelligence/faulty-nvidia-h100-gpus-and-hbm3-memory-caused-half-of-the-failures-during-llama-3-training-one-failure-every-three-hours-for-metas-16384-gpu-training-cluster\">Meta</a>\n and (very unofficially)\n <a href=\"https://www.tomshardware.com/pc-components/gpus/datacenter-gpu-service-life-can-be-surprisingly-short-only-one-to-three-years-is-expected-according-to-unnamed-google-architect\">Google</a>.</p>\n <p>So GPUs are apparently fragile. And they are expensive to run because they require huge\n amounts of electricity. More, in fact, than we currently have, which is why electrical bills are spiking here and there around\n the world.</p>\n <p>Why does this matter? Because when the 19th-century railway bubble burst, we were left with railways. When the\n early-electrification bubble burst, we were left with the grid. And when the \n <a href=\"https://en.wikipedia.org/wiki/Dot-com_bubble\">dot-com bubble</a> burst, we were left with a lot of valuable\n infrastructure whose cost was sunk, in particular dark fibre. The AI bubble? Not so much; What with GPU burnout and power charges,\n the infrastructure is going to be expensive to keep running, not something that new classes of application can pick up and use on\n the cheap.</p> \n <p>Which suggests that the post-bubble hangover will have few bright spots.</p>\n <h2 id=\"p-1\">SPVs</h2>\n <p>This is a set of purely financial issues but I think they’re at the center of the story.</p>\n <p>It’s like this. The Big-Tech giants are insanely profitable but they don’t have enough money lying around to build the\n hundreds of billions of dollars worth of data centers the AI prophets say we’re going to need. Which shouldn’t be a problem;\n investors would line up to lend them as much as they want, because they’re pretty sure\n they’re going to get it back, plus interest.</p>\n <p>But apparently they don’t want to borrow the money and have the debts on their balance sheet. So they’re\n setting up “Special Purpose Vehicles”, synthetic companies that are going to build and own the data centers; the Big Techs \n promise to pay to use them, whether or not genAI pans out and whether or not the data centers become operational. Somehow,\n this doesn’t count as “debt”.</p>\n <p>The financial voodoo runs deep here. I recommend Matt Levine’s\n <a href=\"https://newsletterhunt.com/emails/205961\">Coffee pod financing</a> and the <cite>Financial Times’</cite>\n <a href=\"https://www.ft.com/content/d0344253-b0a2-4c6d-8b97-520243678afd\">A closer look at the record-smashing ‘Hyperion’\n corporate bond sale</a>. Levine’s explanation has less jargon and is hilarious; the\n <cite>FT</cite> is more technical but still likely to provoke horrified eye-rolls.</p>\n <p>If you think there’s a distinct odor of 2008 around all this, you’d be right.</p>\n <p>If the genAI fanpholks are right, all the debt-only-don’t-call-it-that will be covered by profits and everyone can sleep\n sound. Only it won’t. Thus, either the debts will apply a meat-axe to Big Tech profits, or (like 2008) somehow they won’t be\n paid back. If whoever’s going to bite the dust is “too big to fail”, \n the money has to come from… somewhere? Taxpayers? Pension funds? Insurance companies?</p>\n <h2 id=\"p-3\">Paul K and Paul K</h2>\n <p>I think I’ve set\n <a href=\"https://paulkrugman.substack.com/p/talking-with-paul-kedrosky\">that piece</a> up enough now. It points out a few other\n issues that I think people should care about. I have one criticism: They argue that genAI won’t produce sufficient revenue from\n consumers to pay back the current investment frenzy. I mean, they’re right, it won’t, but that’s not what the investors are\n buying. They’re buying the promise, not of <em>more revenue</em>, but of <em>higher profits</em> that happen when tens of\n millions of knowledge workers are replaced by (presumably-cheaper) genAI.</p>\n <p>I wonder who, after the loss of those tens of millions of high-paid jobs, are going to be the\n consumers who’ll buy the goods that’ll drive the profits that’ll pay back the investors. But that problem is kind of\n intrinsic to Late-stage Capitalism.</p>\n <p>Anyhow, there will be a crash and a hangover. I think the people telling us that genAI is the future and we\n must pay it fealty richly deserve their impending financial wipe-out.\n But still, I hope the hangover is less terrible than I think it will be.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Technology/AI",
"term": "Technology/AI",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Technology",
"term": "Technology",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "AI",
"term": "AI",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics",
"title": "Tracy Numbers",
"description": "Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking a class in Afro-Cuban rhythms from Russell Shumsky, with whom I’ve studied West-African drumming for many years. Among the basics of Afro-Cuban are the Bell Patterns, which come straight out of Africa. The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It feels like it’s in four, particularly when played fast",
"url": "https://www.tbray.org/ongoing/When/202x/2025/12/02/Bell-Combinatorics",
"published": "2025-12-02T20:00:00.000Z",
"updated": "2025-12-02T20:00:00.000Z",
"content": "<p>Here’s a story about African rhythms and cancer and combinatorics. It starts a few years ago when I was taking\n a class in Afro-Cuban rhythms from\n <a href=\"https://drumming.ca\">Russell Shumsky</a>, with whom I’ve studied West-African drumming for many years. Among the\n basics of Afro-Cuban are the\n <a href=\"https://en.wikipedia.org/wiki/Bell_pattern\">Bell Patterns</a>, which come straight out of Africa.\n The most basic is the “Standard Pattern”, commonly accompanying 12/8music. “12/8” means there are four clusters of\n three notes and you can count it “one-two-three two-two-three three-two-three four-two-three”. It\n feels like it’s in four, particularly when played fast.</p>\n <p>Here’s the standard bell pattern in music notation. Instead of one 12/8 bar, I’ve broken it into four 3/8 chunks. Let’s call\n those “mini-measures”; I’ll use that or just “minis” in the rest of this piece.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png\" alt=\"standard 12/8 bell pattern\"></img>\n <div class=\"caption\"><p><audio controls=\"controls\" src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a\"></audio></p></div>\n <p>Bell patterns are never played in isolation, but circularly on fast repeat, so the first note immediately follows\n the last.</p>\n <p>In the sound sample, I’m playing a background beat on a conga, emphasizing the beginning of the 12/8 measures.\n The actual bell pattern is on the high “child” bell of a\n <a href=\"https://en.wikipedia.org/wiki/Ewe_drumming#Gankogui\">Gankoqui</a>, an African dual-cowbell set.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/PXL_20251201_192632520.png\" alt=\"Black cat considers a Gankoqui\"></img>\n <div class=\"caption\"><p><a href=\"/ongoing/When/202x/2021/02/22/Meet-Thorn\">“þ” the cat</a> was trying bell patterns but\n unfortunately<br></br>cats can’t count as high as 12. Collar by\n <a href=\"https://www.birdsbesafe.com\">BirdsBeSafe.com</a>.</p></div>\n <p>That’s my Gankoqui.\n I bought it off someone on Etsy who imports them from Ghana. \n It came with that little thin stick that sounds nice, but sometimes I use a regular drumstick when things get loud.</p>\n <h2 id=\"p-1\">The problem</h2>\n <p>Russell’s a good teacher and the standard pattern isn’t that tricky, but I just couldn’t get a grip on it.\n It’s a little harder than it looks what with cycling it really fast, and then\n you’re playing it against complicated music with other instrumental voices. \n I probably would have got there, but the lessons ran out of gas in the depths of Covid.</p>\n <h2 id=\"p-2\">Introducing Tracy</h2>\n <p>She was Russell’s long-time partner, a good person and good drummer too. When you were struggling\n with a complex rhythm it was helpful to watch Tracy’s hands, because she was <em>always</em> on the beat.</p>\n <p>Tracy lived with stage four metastatic cancer for many years and braved endless awful rounds of therapy while remaining generally\n cheerful. She could be morbidly funny; I bought her congas (you can hear one behind the beat in the samples) when she had a\n storage-space problem. She told me she was carefully planning her finances so she’d run out of money just before the cancer got\n her.</p>\n <p>I always enjoyed any time I spent with her. Then, a dozen years into her cancer\n journey, this last summer it got into her brain and it was pretty clear her end times were upon her.</p>\n <h2 id=\"p-3\">The hospice</h2>\n <p>Tracy’s last months were spent at\n <a href=\"https://stjohnhospice.ca\">St. John Hospice</a> in Vancouver’s far west. I can’t say enough\n good things about it. If you’re near Vancouver and your death becomes imminent, try to be there if you can’t be at home.\n It’s comfortable and the staff are expert and infinitely kind. The rules that apply at hospices\n are different from those at hospitals; for example, Tracy’s cat joined her in residency and had the run of the place.</p>\n <p>I (and other fans of Russell and Tracy) visited the hospice a few times. My last visit was just days before her death\n and, while she was fatigued and spaced-out, it was still Tracy.\n I wasn’t close enough to call her a friend, but I miss her.</p>\n <p>We got to talking about Afro-Cuban music and I laughed at myself, saying how I never could get that damn bell pattern\n down. Said Russell: “Oh, you mean the standard 12/8 pattern? Tracy, let’s show him” and on the second try, they were doing it\n together, just voices, <i>ta ta ta-ta, ta ta ta</i>. </p>\n <p>Driving home from the hospice, I told myself that if Tracy could manage the bell pattern in her condition, I could bloody\n well learn it. So I studied the details and used a metronome app and after a while\n I thought I had it down pretty well.</p>\n <h2 id=\"p-4\">Sounds cool</h2>\n <p>I go to a weekly by-invitation African drum jam where I’m on the weaker end of the skill\n spectrum. The first time a 12/8 came along after I thought I’d learned the pattern, I had to summon up courage\n and then I fluffed the first few bars. But after a while I \n was grooving along and smiling and thinking the bell sounded pretty cool against the thunder of all the djembés and dununs.</p>\n <p>And, even played amateurishly, it does sound cool. Let’s have another look at the music.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.png\" alt=\"standard 12/8 bell pattern\"></img>\n <div class=\"caption\"><p><audio controls=\"controls\" src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/standard.m4a\"></audio></p></div>\n <p>West-African drumming often tries to achieve rhythmic tension, where a given note could fit in multiple ways and your\n ear is not 100% sure what’s going on. The standard pattern does this, twice.</p>\n <p>Remember, I said that 12/8 sounds like it’s\n “in four”, especially if you hit the first beat of each of the four mini-measures. But two of\n the four minis here go around the first note, weakening the 4/4 feel.\n Especially on that third mini; you can feel the beat slide by the missing “one”.</p>\n <p>Also, the last three notes are evenly spaced two beats\n apart, so six of them would fill the 12-beat pattern, suggesting that this might be in triple time, not 12/8.</p>\n <p>The effect, to my ears, is of the bell, higher-pitched than the drums, shifting against the rhythm, or even dancing\n across it. At the drum jam, at almost any given moment it won’t be just drums, one or more people will have\n clave sticks or rattles or tambourines or cowbells weaving through the beat.</p>\n <h2 id=\"p-5\">Mixing it up</h2>\n <p>After I felt confident playing the standard pattern, it still sounded cool, but I wanted to branch out, not just\n go around and around the same seven notes. So the first thing I did was start mixing in a few of these.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-1.png\" alt=\"bell pattern variation\"></img>\n <div class=\"caption\"><p><audio controls=\"controls\" src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/5333.m4a\"></audio></p></div>\n <p>This repeats the second bar through the end of the phrase. In the sound sample I mix it up with the standard pattern.\n It’s got less rhythmic tension but on the other hand\n flows along smoothly with the drum thunder. Also you don’t have to think at all, so you can enjoy listening to what the other\n people are playing.</p>\n <p>Then I got a little more ambitious and reshuffled:</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/variation-2.png\" alt=\"bell pattern variation\"></img>\n <div class=\"caption\"><p><audio controls=\"controls\" src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/5253.m4a\"></audio></p></div>\n <p>The mini-measures are the same as in the standard pattern, just in a different order. Anyhow, this kind of thing is fun.</p>\n <h2 id=\"p-6\">Combinatorics</h2>\n <p>Then one evening I was lying in bed, thoughts wandering, and wondered “How many bell patterns are there?”\n A little mental math showed that of course there are eight possible arrangements of tones\n in a 3-note mini-measure. Here they are:</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/12/02/8-measures.png\" alt=\"Possible arrangements of notes in 3/8 time\"></img>\n <div class=\"caption\"><p>I’ll use the boxed numbers to identify the minis.</p></div>\n <p>Why are the minis numbered in that order? Every computer programmer looking at this already knows, but for the rest of you: If the\n notes are ones and the rests are zeroes, they are the eight binary numbers between zero and seven inclusive.\n So each number’s binary bits show where the drumstrokes are. \n By the way, numbers four through\n seven have a note on the one beat, zero through three don’t.</p>\n <p>Is it weird to have a zero i.e. silent mini? I don’t think so, sometimes spaces between the notes really matter.</p>\n <h2 id=\"p-7\">Patterns</h2>\n <p>Anyhow, the original question was about the number of different bell patterns. Each has four\n mini-measures with 8 possible values. So the answer is 8 ⨉ 8 ⨉ 8 ⨉ 8, which is 4,096.</p>\n <p>And each of them can be identified by four little numbers, ranging from T0000 (I can hear the bandleader yelling “gimme zeroes\n for the sax break”) to T7777, a flurry of eighth notes that you might use in the big encore-number finish designed to leave the\n audience yelling as you walk off stage. The standard bell pattern is T5325; in binary “101 011 010 101” and the 1’s are drumstrokes.\n The first variation above is T5333 and the second is T5253.</p>\n <p>The “T” in front of each bell pattern number is for Tracy.</p>\n <p>If you go look at the\n <a href=\"https://en.wikipedia.org/wiki/Bell_pattern\">Wikipedia Bell-pattern article</a>, they emphasize that there are lots of\n different patterns. Now they all have numbers! The article\n <a href=\"https://en.wikipedia.org/wiki/Bell_pattern#128_bell_patterns\">makes special mention of</a> T5124, T5221, and T5244.</p>\n <h2 id=\"p-8\">But why, Tim?!</h2>\n <p>I’m a computer programmer with a Math degree, and an amateur musician.\n Anyone who thinks that these are disjoint disciplines is wrong.\n And, I think the notation is (on a very small scale) kind of pleasing.</p>\n <p>But the work has actually helped me.\n Now that I’ve considered each mini-measure and its personality. I find all of them sneaking into\n my Gankoqui excursions, which have gotten noticeably weirder, for example T5635.\n Nobody’s threatened to kick me out of the jam, so far.</p>\n <p>Also, this has given me a real appreciation of whoever it was that, probably thousands of years ago and certainly in Africa,\n picked the “standard” pattern as, well, standard. Because it’s great.</p>\n <h2 id=\"p-9\">What’s missing?</h2>\n <p>You may have noticed that Gankoquis have two bells and I’ve been ignoring that fact. Normally you’d play these patterns\n on the smaller “child” bell, but sometimes bringing the big parent bell in for a couple of strokes works \n well.\n <a href=\"https://www.youtube.com/watch?v=X2K0i8e6Ftc\">Here’s an example</a> (h/t Russell).</p>\n <p>Also, this discussion has been limited to 3/8 minis in 12/8 measures. There’s another whole universe of 4/4 rhythms that\n also have bell patterns (but everything exists in the shadow of the\n <a href=\"https://en.wikipedia.org/wiki/Clave_(rhythm)\">clave rhythm</a>).\n In that world a pattern has four measures, each of which can have sixteen possible values, so there are 65,536 different ones.</p>\n <p>And I could repeat the numbers construction above for 4/4. But I’m not going to, because the rewards feel smaller. In my\n experience, 4/4 rhythms lope smoothly along and everyone knows where the one is even when there’s no note on it, so there’s less\n ambiguity to work with.\n Anyhow, any neophyte (like for example me) can play a pretty smooth bell line against 4/4; just start with\n <a href=\"https://en.wikipedia.org/wiki/Clave_(rhythm)\">clave</a> and add\n variations (or don’t) and you’ll be fine.</p>\n <h2 id=\"p-10\">Useful?</h2>\n <p>These numbers are just elementary mathemusical fun. If anyone else wanted to use them that’d be a pleasant surprise.\n If “anyone else” is you, go ahead, but they have a name and you have to use it. These are called Tracy Numbers.</p>\n <h2 id=\"p-11\">Colophon</h2>\n <p>Music fragments by\n <a href=\"https://www.mu.se/musescore-studio\">MuseScore Studio</a>. Sound samples facilitated by GarageBand, a Shure MV51, and PSB\n Alphas.</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Arts/Music",
"term": "Arts/Music",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Arts",
"term": "Arts",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Music",
"term": "Music",
"url": "https://www.tbray.org/ongoing/What/"
}
]
},
{
"id": "https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football",
"title": "Fútbol Joy",
"description": "Last Saturday I had one of my peak 2025 experiences, at the MLS semifinal between the Vancouver Whitecaps FC (hereinafter “Caps”) and Los Angeles FC (“LAFC”). Both those FC’s stand for “Fútbol Club”. 53,095 other fans were there with my son and I; we came home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports",
"url": "https://www.tbray.org/ongoing/When/202x/2025/11/23/Soccer-vs-Football",
"published": "2025-11-23T20:00:00.000Z",
"updated": "2025-11-28T04:38:07.000Z",
"content": "<p>Last Saturday I had one of my peak 2025 experiences, at the\n <a href=\"https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs\">MLS semifinal</a> \n between the <a href=\"https://www.whitecapsfc.com/\">Vancouver Whitecaps FC</a> (hereinafter “Caps”) and\n <a href=\"https://en.wikipedia.org/wiki/Los_Angeles_FC\">Los Angeles FC</a> (“LAFC”). Both those FC’s stand for “Fútbol Club”.\n 53,095 other fans were there with my son and I; we came\n home smiling. I’d like to share a bit of the joy and an unexpected side-effect: I’ve gone off most other TV sports.</p>\n <p>Earlier this year\n <a href=\"/ongoing/When/202x/2025/05/04/Southsiders\">I wrote about becoming a Caps fan</a>. Anyone who enjoys this will probably\n like that piece too.</p>\n <p>Let’s set the scene with pictures.</p>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_004124670.png\" alt=\"Before the fútbol at the pub\"></img>\n <div class=\"caption\"><p>Supporters gather pre-game at a nearby Irish-flavored pub.</p></div>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_011735082.png\" alt=\"Parading from the pub to the match\"></img>\n <div class=\"caption\"><p>Supporters march to the game.<br></br>When you’re in a frivolous parade, everyone smiles<br></br>at\n you, even the drivers hemmed in by paraders.</p></div>\n <img src=\"https://www.tbray.org/ongoing/When/202x/2025/11/23/PXL_20251123_024033770.png\" alt=\"Whitecaps tifo banner: fire that burns / blue melts gold\"></img>\n <div class=\"caption\"><p>The banner is what’s called a\n <a href=\"https://en.wikipedia.org/wiki/Tifo\">tifo</a>.<br></br>I have to admit I failed to parse it.</p></div>\n <h2 id=\"p-5\">The game</h2>\n <p>It was 120 minutes of ridiculously over-the-top psychodrama. I was exhausted at the end.\n If you want a full retrospective, type “whitecaps lafc” into any Web search to get the particulars. Or\n <a href=\"https://www.mlssoccer.com/playoffs/2025/news/vancouver-whitecaps-keep-mls-cup-dream-alive-unbelievable-win-lafc-playoffs\">hit\n this</a>. But here’s the short version:</p>\n <ol>\n <li><p>The Caps came out sharp and fast and had LAFC pretty well flummoxed through most of the first half, scoring two goals,\n\n <a href=\"https://www.youtube.com/watch?v=9nEOw8ckWMA\">one of which was a jaw-dropper</a>.\n They also managed to contain LAFC’s superstar\n <a href=\"https://en.wikipedia.org/wiki/Son_Heung-min\">Son Heung-min</a>.</p></li>\n <li><p>In the second half, the visitors reconfigured and were much better. Son did the superstar thing and scored two goals,\n <a href=\"https://www.youtube.com/watch?v=-L9N8pkrkSM\">one another jaw-dropper</a>, just as the game was ending, to tie things\n up.</p></li> \n <li><p>The Caps lost two players, one for fouls, one to injury, and were down two men through most of overtime. LAFC’s assault\n was relentless but the Caps held on, getting more than a little lucky.</p></li>\n <li><p>So it went to a penalty-kick competition. Son, shockingly, missed; he was exhausted and limping. At the end of the\n day the Caps scored four out of five to LAFC’s three and got the win.</p></li>\n </ol>\n <p>Suffice it to say that the dramatic peak wasn’t\n any of the flashes of brilliance, but rather the errors that happen when people are at the limit of their endurance. Vancouver\n made one fewer, that’s all there was to it.</p>\n <h2 id=\"p-3\">That sound</h2>\n <p>There’s not another like it on this planet. I mean tens of thousands of voices in a big stadium greeting a home goal.\n Fútbol specifically because its goals, compared to North American sports where points come in dozens, are\n such huge markers. The sound-pressure wavefront, coming from every direction, of all those inarticulate howls of joy,\n all in the same tiny fraction of a second, is a whole-body experience.</p>\n <h2 id=\"p-6\">The side effect</h2>\n <p>I’ve long been a televised-sports fan; the only TV show that isn’t scripted and thus has real drama. But\n since getting mixed up in fútbol, I’ve sort of gone off the other sports I used to watch. I had to think a bit to figure\n out why.</p>\n <p>It’s the ads. The football, basketball and hockey broadcasts screech to a halt\n <a href=\"https://qz.com/150577/an-average-nfl-game-more-than-100-commercials-and-just-11-minutes-of-play\">every ten or fewer\n minutes</a> for a couple of minutes of advertising. Most of the ads are dumb, many are offensive, and the relentless\n addiction-promoting gambling pitches are both. On top of which there’s the bone-headed repetition; someone somewhere thinks\n I’m gonna lean toward this generic SUV as opposed to that one because of the 138th time they’ve run that commercial where hip young\n people with fulfilling lives are going to have sex because of its dashboard geometry and motorized hatchback.\n I mean, the other SUVs have that stuff too, but this one’s actors are more convincingly likely to be headed for bed?</p>\n <p>Being in the room with this shit makes me angry even though my mute-button skillz are sharp.\n The world being what it is, I really don’t need to be around something that angers me several times per hour.\n So, while when young I loved playing both football and basketball, and while the pro games are good entertainment, \n my patience seems to be running out.</p>\n <p>Fútbol, on the other hand, has two fiftyish-minute chunks of continuous action, so you can sink into the flow of the\n game. The contrast, switching back and forth between that and the other North American sports, is stark.</p>\n <p>(Except for I’m mostly forgiving baseball because its natural rhythm is full of stops suitable for hot dogs and beer and\n admiring cute babies and T-shirts and discussions of etymology and epidemiology. I mean, the ads are still mindless repetitive\n shit, we’re just more accustomed to switching attention away when nothing’s happening.)</p>\n <p>And I’m not claiming that fútbol is more virtuous or less dirty than any other sport; after all, its global\n organizing body FIFA has repeatedly been exposed as\n <a href=\"https://en.wikipedia.org/wiki/FIFA#Corruption\">galactically corrupt</a>. I’m just saying it offers a better\n experience.</p>\n <h2 id=\"p-9\">Soccer?</h2>\n <p>That word is an awkward invention by nineteenth-century British toffs based on abbreviating “association”. I accept that on my\n continent “football” means gridiron, but people who enjoy “soccer” still say it so in print I offer “fútbol”, which is a\n typographically nice little cluster; please humor me.</p>\n <p>Anyhow, you might want to check out your local team; in North America, the prices are lower than the other sports, who could\n be against cheap happiness with fewer gambling ads?</p>",
"image": null,
"media": [],
"authors": [
{
"name": "Tim Bray",
"email": null,
"url": null
}
],
"categories": [
{
"label": "Sports/Football",
"term": "Sports/Football",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Sports",
"term": "Sports",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Football",
"term": "Football",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Sports/Soccer",
"term": "Sports/Soccer",
"url": "https://www.tbray.org/ongoing/What/"
},
{
"label": "Soccer",
"term": "Soccer",
"url": "https://www.tbray.org/ongoing/What/"
}
]
}
]
}