I haven't seen media outlets picking up on "agentic misalignment".

The core of your claim is that it's not a legit research. But that's basically a conspiracy theory. We know for a fact that Anthropic employs some of the best people in the industry, including ones who are deeply concerned about safety. Their interpretability research is some of the best. So what's more likely:

* Research is fake and everyone is on it * It's a legit research even if not very interesting

OTOH with Windows 95 it's not really clear how to make a program or do something creative. So I'd argue C64 or similar might be a better choices that W95 PC for kids under 15 y.o.

I think both of these machines are really good for learning BASIC: much fewer distractions, you type commands and computer does something.

E.g.

> A 1.6GB Docker image for a Node app. Every code change rebuilds npm install from scratch. CI takes 8 minutes for a one-line fix.

> The team's proposal: add more CI runners.

Would it be surprising if that team makes a React app which does 10x more requests than necessary, has 10x more JS code than necessary, flickers, etc. People just don't care, and it has nothing to do with AI. "Engineering" is too big of a word for this kind of activity.

On the other hand, I think AI can amplify capabilities of those people who still care, and it's a good thing.

Container is quite like a "separate user" except you can explicitly define what it can access.

(Even if all your daemons have good auth, it's now quite common for _apps_ to open listening sockets without much auth...)

If we assume 250W for a continuously running agent, Grok 4 training run estimate would be around 50 million session-days, so a half-million people might consume as much running agents continuously for 100 days.

But it's also extremely brittle and unstable. It's really the opposite of what people look in agents.

You don't need to be superstitious here: disk activity, including writes in particular, can be measured. E.g. `iostat` or `vmstat` on Linux.

Both are public companies so they might be required to reveal these details

It won't count executable pages and memory-mapped file use as "used" memory, so your system might display gigabytes "free" when it's starving, executables getting paused when code pages are paged-in from disk.

It's just less useful than what's displayed now. "Everyone is doing it wrong" is usually a signal that you're missing something.

AFAIK it's practical only if you make use of TPM. And if you do, you're basically at mercy of TPM.

   type ProfileSpec = Frond.NodeSpec<{
     readonly args: Frond.Args.None;
     readonly key: Frond.Key.Singleton;
     readonly deps: {
       readonly http: Frond.Dep;
     };
    readonly result: Profile;
   }>;