yearolinuxdsktp

Gherkin! The only way to do behavior-driven development!

When you wanted to have a layer of brittle regex expressions to have to maintain and debug in your testing setup!

When you wanted to write tests that look like plain language, but have none of its flexibility!

When you wanted to have massive friction when refactoring your tests!

/s

Project headline is “The smallest functional Emacs in less than 2000 lines of C.”

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

Yes, and so does Claude “auto mode”, but it’s free.

And this disregard for non-tmux usability is why I stopped using Ghostty. First it took up until 1.3 to get search, then fixing this significant quality-of-life problem is clearly not a priority.

What good is Fable 5.1 for when you have Opus 5.5 anyway?

This and the terrible writing, esp by Anthropic models. Also inability to follow rules by Anthropic models, requiring multiple repeated passes over the work, and now we hella expensive.

Patch the Planet? Not with OpenAI tools.

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

You can't compare rustc to a large application. Yes it's a large program, no it's nowhere near as large as Codex CLI. 1420 crates.

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!

All this upfront planning is a giant waste of tokens and altogether a poor approach. Especially at the level superpowers prescribes, it is quite insane.

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.

OpenCode is barely usable with local LLMs. Plan mode to build mode switch and lose all your prefix. Compaction throws away your prefix (just fixed in v2... I guess v1 gets to stuff it). Pi throws away your prefix during compaction too. I think all these tools' devs and users use it with hosted models. Pi doesn't come with basic permission capabilities--YOLO, write your own or hope the extension you find in the Pi extension store isn't an absolute dumpster fire.

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.

I disagree it’s impossible to solve. Huge C++ projects don’t have continuously growing build directories and can still compile incrementally correctly.

Manufacturers laugh in the face of right to repair laws. They have no teeth.

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.