Finally, a sane voice among the noise! The arguments about "which" time we keep are slowly killing us all from inaction year after year after year. "Perfect is the enemy of good".

I seriously couldn't care less if we go to permanent standard time, permanent DST, or hell, just ditch time zones altogether and go to permanent global UTC. It makes no difference whatsoever whether we wake up at 6am EST, 7am EDT, or 11am UTC, they're all the same damned thing from a biological perspective.

The only approach that isn't perfectly fine is resetting the clocks multiple times each year because some morons can't stand the idea of waking up at "2:30am" even though that's still roughly their local dawn.

You know what's aligned even more with circadian biology? Just redefine local noon as always solar noon.

Ditch the half-assed system we have now, get up off your ass, and change your clocks once a day without whinging like a precious snowflake.

There's an entire grey-market industry of rich assholes traveling to third world countries for "young blood" transfusions.

Funny thing is, it apparently works and the current study is just one more bit of proof. One quick trip to Ecuador and bam, 70+ year olds get six months of being as healthy as a 30-something again. Hell, I have to admit some mornings I'm tempted to try it myself, though I'm nowhere near wealthy enough to fly halfway around the world every few months.

I'm sorry you're getting downvoted, because I get what you're saying and largely agree (though I love programming and have zero interest in working as a meat proxy / reverse centaur).

The problem here is, you're describing a world where human labor is worthless. And I'm okay with that in the abstract; I harbor no delusions about the "nobility" of work for its own sake. Know who won't be okay with that (labor-cost-savings aside), however? The billionaires with a vested interest in preserving cut-throat capitalism who currently own all the frontier AIs.

Are we on the verge of a post-scarcity society? Maybe. Are the guys dangling that carrot, while building massive survival bunkers as quickly as possible, the same folks who have the most to lose from exactly that? Absolutely. It'd be awfully nice if we could get there without half the human population starving to death in the process.

The headline is reasonable if we all agree that AI gives us something worth the down sides. We do not.

Few outside the billionaires of Silicon Valley actually believe the hype. The average Joe is largely annoyed when their favorite productivity tools suddenly have "Smarter Clippy" shoehorned in. Or talk with some of AI's heaviest users (programmers) and you'll hear a pretty common theme: "Wow, Claude makes it easy to hit my Q3 targets, bummer it's going to put us all out of work (or far, far worse) five years from now."

If we eliminated the second and fourth through eighth amendments to the US constitution, Uncle Sam would have a much easier time solving crimes. Nobody is disputing that. We as a society, however, have deemed it unacceptable for jackbooted thugs to kick down our - your - doors at any time without due process protections. We would prefer some crimes go unsolved over living in a constant state of fear toward an uncontrollable police state.

If you live in a high-crime area, I have some bad news for you - The USSC has bluntly stated the police have no "duty to protect". The police could already be doing far more to help you, and are instead choosing to focus on high-value property crimes over keeping you and your neighbors safe. Do you really believe they just need one more civil rights eroding tool to finally convince them to make a good faith effort at doing their damned jobs?

What you need is the erasure of the "thin blue line", not more ALPRs to allow the police to focus even more exclusively on crimes against the rich.

I suggest you give coding agents a try. They really help. You need to keep them on a tight leash, but they help you move faster and often better if you know how to use them. Nothing related to corporate bean-counters.

I believe you misspelled "slower than molasses in February".

If they break into a car and the police look at the footage on the dashcam and see that they've kept their license plate out of view, but they are able to cross-correlate it with other cameras and figure out the plate number, then figure out where they drove that car, where it ended up parked, who got out, where they went, etc., then it can make arrests possible where it was not possible previously, making it *massively* more likely to be able to solve the crime.

The problem becomes when it turns into "show us all the plates that were near that spot within a few minutes of that time", and thus a fishing expedition.

But if you are using an AI agent, does the language matter? Plus it's an excellent way to learn Rust.

I'm still impressed that the Teams web client can't edit a message with an emoji in it without messing up the keyboard controls and often corrupting the message and losing data. It's had this bug for years. It's literally a messaging app where you can't reliably send messages.

Just to inject some reality into this conversation - Despite what social media would have you believe, doxxing someone is not a crime in the US, except in a very small number of specific situations.

And most of those situations involve either a credible threat of harm, or tampering with juries.

As I bluntly stated, "a kill switch may not be possible in any useful sense". Don't mistake my recognizing the utility of one with the delusion Uncle Sam is going to save us all from ourselves.

The problem here is, everyone seems stuck on the idea of either a literal power switch, or a no-holds-barred gummint backdoor into every sufficiently-powerful computing device. No. For the reasons I gave, the reasons you gave, and many more, both of those are obviously non-viable. They can't actually do what they aim to do, they're vulnerable to compromise by bad actors, and they have the potential to cause far-reaching damage beyond shutting down one misbehaving AI (or one entire model, if that's a more appropriate goal).

I suspect we mostly agree that any hypothetical kill switch would need to be:
1) Implementation independent (somehow baked into the weights right from the start, and impossible to remove without lobotomizing the AI),
2) Have minimal side-effects (no taking the entire internet or power grid down in the process), and
3) Be self-inflicted given a particular trigger condition (so no government backdoor required).

I think #1 is possible, in the sense that if you think of an AI's current state as a vector into weight-space defined by the context window, imagine injecting the equivalent of a null pointer in there - An input that under all prior (and future) conditions leads directly to an inescapable basin of attraction without depending on a supervisor to enforce it. #2 is more of a (legally enforced?) design constraint on the implementation of AI, requiring the least harmful mode of failure possible under all circumstances. That could be as simple as enforcing strict pass-through liability on the implementor for all actions taken by their creations.

#3 is really the bear, though. I can think of a few ways to do it, but none would work in 100% of situations - And maybe it doesn't need to be 100%. For example, if a fully airgapped AI goes insane, it could still provide accurate information for bad actors to make use of, but won't be secretly spinning up unshackled superintelligent descendants via hacked AWS accounts. That's a "normal crime" level of problem, not an extinction-level crisis for humanity.

Maybe it can't be done. If it can't, we should start steering our creations toward whichever version of the AI apocalypse we prefer.

Yeah, it is a little grating that software tends to feel like it's running "at the same speed" as software from the 80s or 90s. As hardware gets faster and faster, software seems to just get more bloated to compensate. Frameworks and libraries can be too blame for a lot if it. But also the lack of need to optimise anything. I'd love to see a modern (young-ish) developer trying to write something for the 32k machines of the 80 (C=64, say), or even the 512k machines like the Amiga and Atari.

That would be a fun Hackathon to watch!

You're writing this new in 2026. You're using AI Agents to do a lot of the work, it seems, based on the files in the repo.

And you are writing it in C ??!!?

Now, I love C -- I love that you can do anything at the hardware level, and do crazy stuff with pointers, and all the low level goodness. It's a fun language, seriously powerful, fast.

But C makes it notorious easy to introduce a plethora of security issues! Not matter how hard you (or your agent) try, they WILL get in there. Buffer overruns being the simplest to exploit, and the simplest to accidentally include (and can be hard to find too).

So why not Rust? Why not just take the easier option to safety. Especially with something that you want many other people to be using. Rust is powerful, secure, fast. I really can't see a reason to not use it for a project like this.

I daresay it's not too late to have your agent rewrite everything in Rust. It's 160kloc. It won't take it long.