How someone jumped to beginner-friendly from that is the real question.

How much time will be left in the Defender’s Window between now and an organization getting Daybreak Access?

I just did a release build of Codex CLI with "lto = false" for codex CLI binary and code mode host only, and it took 75 minutes, of it 1063 seconds for the final rustc of codex bin. Windows Defender off. That's on a 4-core 2021-era Intel laptop with 32GB RAM and a half-TB SSD. And I can't let the build run at default concurrency, because rustc OOMs the machine, so this is with cargo jobs = 4. Regardless, the final rustc call is independent of that and that was 1063s with lto=false. Previous build was 90 minutes with default thinlto for the same CLI build.

How can Codex write fast-to-compile Rust code, do tell?? Do tell!

We stopped doing big design up-front for a reason, yet it’s roaring back.

We know the devil is in the implementation details and you can’t anticipate everything before you try to implement it. The implement/discover/adjust approach cycle is the best cycle for a reason.

The approach of handing plans down to dumber agents is also a bad idea, for the same reason. A dumber agent will plow right through unanticipated friction in the implementation, and it won’t know to stop and raise an issue.

Even smarter agents will try to complete a plan as written without altering course.

Nothing beats implementing quickly, reviewing, addressing, then reviewing again.

If you’re on a sub, you can afford to waste tokens on this planning theater, I suppose.

Claude Code turned on the remote-control server by default with an update (no explanation or notification). BUT Claude Code didn't break the expectation that the hooks and the commands you run inherit your environment. So it was hard to notice.

Whereas when Codex App server became enabled by default, and as per OpenAI, it was never contractual that hooks run in the client's environment. Sure, let's break long-standing expectations of where code runs when you run a CLI--it was never contractual, you see. Now you have to figure out how to turn this crap off, just to UNBREAK your workflow!

This is why it's apples and oranges here, with Claude Code and Codex.

So you can buy repair manual access for 1-3 days or on a subscription. You don’t get car software updates. You don’t get the diagnostic interface documentation. It’s a joke.

Incremental compilation is not cleaned up. Older deps pile up and don’t get cleaned.

Run out of disk space? Oh it’s just the 200+ GB codex-rs target folder.

Forget about doing worktrees.

Rust has a lot of work to do.

The excuse was it was still “in preview” and the enterprise didn’t opt in to the preview channel.

With Google, it’s either in beta or deprecated.

https://pdfhost.io/v/2CVhPGy9Kw_CLEAR_Function_Hooks_Core_Ar...

- Autoplay transitioned to a per-device setting… suddenly default-on on every new device you log in to.

- Watching a video with computer-to-TV account connection? Automatic “TV queue,” a concept absent from the TV app, with incomprehensible behavior for how it’s used, so now videos are auto-played anyway.

- Watching a video from a playlist? Autoplay cannot be turned off.

Is it simply bad/absent product management and product design? Or is it actively user-hostile decisions meant to prop up view numbers and continue to have the users hooked on YouTube?