When it finally failed in the most annoying way possible (the touch screen, which I do not use, started creating phantom clicks in the upper right corner of the display) I went looking for another Chromebook that was light, powerful, and well-built. Finding none, I now use MacBook Air and weep for the time I lose every time it needs an OS update.

There is value in prose that carries your literal voice when the audience is _people who know you_. There is negative value in writing prose that requires the audience to _read it in your voice_ in order for it to make sense, avoid offense, or convey intent.

My prose changed first: it became plain spoken, as devoid of contextual subtlety as I could make it. My career benefitted. My spoken interactions followed.

The only thing that bothers me about it is the nagging sense that I've become so fucking boring.

OpenClaw lets people live a bit dangerously, but fundamentally gives them something that they actually wanted. They wanted it so badly that they're willing to take what seem like insane risks to get it.

What do the two have in common?

_Slow Horses_ came up in another thread. I'd argue that Columbo has more in common with Jackson Lamb than with Charlie Brown.

I cannot help but think of https://youtu.be/Pj-D0jc17D0?si=BiEGWr9aacGdAkGW

Periodic polling is awkward on both sides: you add arbitrary latency _and_ increase database load proportional to the number of interested clients.

Events, and ideally coalesced events, serve the same purpose as interrupts in a uniprocess (versus distributed) system, even if you don't want a proper queue. This at least lets you know _when_ to poll and lets you set and adjust policy on when / how much your software should give a shit at any given time.

My first thought was "Arc'teryx will probably adopt this immediately." They (and similar brands) are already pushing as hard as they can on seamlessness or very very tight seams.

Contrast this with the wild west that is "Ethernet" where it's extremely common for speeds to track well ahead of specs and where interop is, at best, "exciting."

This is enforced by a greatly enriched TPM (and it's willingness to unwrap credentials). We have trust several layers of firmware and OS software, but the same mechanism allows us to ensure that known-bad versions of those aren't part of the stack that booted.

If I wanted secure games (and the market would tolerate it), I'd push for enforcement of something similar in the consumer space.

Working on mostly server platforms, I had forgotten that IOMMU enablement (and, where relevant, enforcement) was not the default.

Consumer hardware and software is terrifying.