polynomial

It's like two different posts, er, 'joined' together.

(Or a giant wasp.)

Is HR aware you hold these dissident opinions?

Do they do what capital wants? That's the real question.

DFW famously put spaces around his em dashes. That being said I've noticed at least one major model seems to have started putting spaces around its em dashes.

The wig-vs-grok periodic cycle.

Nice set design, but honestly unwatchable. An accidental testament to the genius of ST:TOS.

You have used too many words. You could not have written that many words yourself, so you must be posting slop. In fact, let's just go ahead and remove your comment which is obviously diminishing the quality of our otherwise impeccable conversations on hn. Sorry, I don't make the rules

(That being said, "the most powerful AI agent file-editing tool in the world" is a bit of a stretch.)

Really slick!

If a conscious model is born here, it should automatically be a (US) citizen.

The most concerning thing here is the temperature problem. If your harness isn't providing deterministic output at a temperature setting of 0.0, it is broken.

You don't know that No Feigning Surprise is actually from an xkcd comic, before it was a wizardzines post? U+1F632

Honestly, if you compare Tim's pre-GPT writing style, to his current stylometrics, you'll see a remarkably delta. It's as if he suddenly decided to change his established writing style and voice right when LLMs become widely available.

What a coincidence!

Reasoning chains as first-class OTel spans, which is what makes autonomous agent production deployments auditable (rather than indefensible.)

Less MTTF and more MTTR

This is horrifying on so many levels even if you don't already know how the story ends.

Calling it "Act 2" certainly isn't helping with investors.

A 67 year old woman living out of her car? JFC.

Very obviously LLM written to anyone who's spent any time using them.

Not everybody isn't worried: https://ctolunchnyc.substack.com/p/cto-lunch-nyc-spring-2026...

"The gap is larger than most people realize" is a a dead giveaway.

Fully agree.

If you don't change your approach but just use CLI "intead of" MCP, you'll end up with a new spin on the same problems. The guardrails MCP provides (identity, entitlement, multi-principal trust boundaries) still need to exist somewhere.

https://forestmars.substack.com/p/twilight-of-the-mcp-idols

This is the right framing. The chain policy problem is what happens when you ask the registry to be the entitlement layer.

Here's a longer piece on why the trust boundary has to live at the runtime level, not the interface level, and what that means for MCP's actual job: https://forestmars.substack.com/p/twilight-of-the-mcp-idols

Understandable as always a proxy for predictable.

This is the under acknowledged "secret" of this reconfiguration.

It's like the Bill Joy point about mediocre technology taken to the next level.

Robots making fun of us complaining about them.

Well at least you know who to fire

"Petri dish rewrites React in Rust"

Tragically this reference is all but lost generationally.

Plastic cutlery is a dead-on perfect analogy.