jsolson

macOS largely _does_ bake this into the OS, and it is annoying. They also provide a way to turn it off for specific applications (including, for example, Terminal.app).

It had me looking up the specs for the Atari Lynx II that I had as a kid in lieu of a more popular handheld.

Then, if you want to know about using optical switches to connect Clos segments without a fixed spine, check out Google's "Mission Apollo" paper: https://arxiv.org/pdf/2208.10041

Huh, now I feel like I should scan my dog.

Thank you.

For most of my time here I used exclusively Chrome OS, and switched to it for personal use as well. My daily driver for years was a bright red Samsung Chromebook Galaxy (the first gen with the actual metal case). Literally none of my work is local, and it could run Secure Shell, Cider-V, and Docs as installed PWAs with their own taskbar items, etc. It was glorious.

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.

I would not argue with this, but I regret to confess that I am merely an engineer. I no longer aspire to artistry.

This is largely where I'm ending up, but I started at the other end.

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.

I'm trying to put together what you could possibly mean by this -- rolling coal is fundamentally about spite. In isolation, nobody _wants_ their vehicle to spew black smoke. It only comes close to making sense in the context of another population (EV owners, typically, or more generally "the libs").

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?

You're not wrong, but PnP including the configuration basis for PCI which still sits at the config space layer of the latest and greatest PCIe. That's the piece I find so significant. I work with GPUs that mostly communicate over a proprietary C2C connection, but how does the OS find them? PCI enumeration.

I don't remember if Plug-n-Play shipped with the original Windows 95 (it's certainly there in the final OSR), but that was a pretty big shift from the manual IRQ and port mapping days of DOS/Windows 3.1.

Columbo is anything but a failure, though, and the audience knows that. His genius is leveraging humility to convince killers that he's a bumbling idiot, while in reality he's onto them from the first encounter.

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

It's so far from comedy that I couldn't make it through the series. When it comes up in conversation, I tend to describe it as "grief porn."

Yes, highly recommend Reynolds, generally, although the third Rev Space book takes some fortitude to get through.

I realize this isn't the meat of your post, but you ate a lobster sandwich at Walmart?

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

You might have even better precision if you stay away from CPU0 and also set idle=poll in your kernel command line. Lots of things (including other interrupts) often land on CPU0. It would not be my first choice for something where I wanted high timing precision.

This comment is incorrect: https://storage.googleapis.com/deepmind-media/Model-Cards/Ge...

TPUs: https://storage.googleapis.com/deepmind-media/Model-Cards/Ge...

I'd say certain countries in Europe give us a run for our money: https://caw.ceu.edu/other-activities/academic-blog/politics/...

I agree with nearly everything except your point (1).

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.

That would make sense.

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.

This actually makes sense from a spec perspective if you want to give enough to allow hardware to catch up with the specs and to support true interop.

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."

Datacenter Blackwell is Gen6, which is critical when pairing it with CX8 (2x400G) as otherwise you'd be stranding NIC BW.

In my world, we won't let a system boot with production credentials unless the IOMMU is enabled.

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.

Those are already unstoppable because they now use Direct Memory Access over the PCI-E bus, so the cheats don't even run on the same computer anymore.

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.

I was surprised to see a mention of the Carnegie Science Center's Omnimax and the year 1978 -- my recollection was that this theater didn't open until I was both alive and cognizant enough of the world around me to remember it.

That seems consistent with this announcement from 2017 that the theater was going to close (citing a quarter century): https://www.pittsburghmagazine.com/rangos-omnimax-theater-to...

I couldn't find any press covering it from 1978, although this directory of IMAX/Omnimax theaters from 1992 matches my recollection of it opening in ~1991.

It can dance if it wants to...

It can leave LLMs behind...

'Cause LLMs don't dance, and if they don't dance, well, they're no friends of mine.

Love it, but it needs an icon so I can install it as a PWA.

Oh, and can I get the icon in corn-flower blue?

The bus bar itself is an SPoF, but it's also just dumb copper. That doesn't mean that nothing can go wrong, but it's pretty far into the tail of the failure distribution.

The power shelf that keeps the busbar fed will have multiple rectifiers, often with at least N+1 redundancy so that you can have a rectifier fail and swap it without the rack itself failing. Similar things apply to the battery shelves.

Note that "device tree" can include things like "PCIe root port"

This device tree is describing fixed (per BOM/schematic) hardware. Things below that hardware are still enumerated.

I really wish this had won out over ACPI. It didn't, though, so Arm Server ready is all ACPI-ified, complete with the tooling trash-fire that the ecosystem entails.

Why do you want to avoid virtualization?