So this is the product of an acquisition?

> Prism builds on the foundation of Crixet, a cloud-based LaTeX platform that OpenAI acquired and has since evolved into Prism as a unified product. This allowed us to start with a strong base of a mature writing and collaboration environment, and integrate AI in a way that fits naturally into scientific workflows.

They’re quite open about Prism being built on top of Crixet.

Or the JavaScript ORM.

> Confronted with a list like this — a deluge like this — we look for details that might explain why these people were subjected to this treatment, details that might reassure us that we, by contrast, are not in danger.

These people were absolutely murdered unnecessarily. At the same time, it’s not that simple. Neither Renée nor Alex were simply standing safely out of the way filming or protesting off a sidewalk when they were killed. Both encounters unfolded in the middle of active, chaotic confrontations involving federal agents. The details matter because we’re talking about how decisions are made in split-second, violent moments and about how we ensure that law enforcement is trained and held accountable.

Altman with the double polo.

…the AI…

Both countries had gay cakes.

Maybe it’s not the place, so that’s why I can’t find anything, but I don’t see any mention of “AGI” or “General” intelligence. Which is refreshing, I guess.

Make sure you’re clicking “Keep” to “approve” the changes. It’s annoying but I don’t think there is a way around having to do that. Then if you manually edit something, you can mention it in your next chat message, e.g., “I made a few changes to <file>. <Next instruction>”

“Yes officer, it was the goober thinking he looked cool in the leather jacket.”

Author is conflating vibe coding with LLM-assisted development. Many such cases.

The author spent much time defining the differences. Where do you see conflation?

They explain it as if one has transformed into the other. Vibe coding has always been where you ignore the output.

The author describes how their use of agents has transformed, not how "vibe" coding has transformed. See these passages for example

> But a year of daily use changes things. The way most engineers I know actually work with these tools now—myself included—has evolved into something different.

> What we’re actually doing # So if “vibe coding” doesn’t describe it, what does? I’ve been calling it agentic coding. The distinction matters: it’s using AI agents while maintaining the expertise and judgment that keeps the output good, rather than letting it rip with zero validation.

See also their passages around how using vibe coding for side projects is different from agentic coding for professional projects

> Vibe coding has always been where you ignore the output.

Does this definition apply to (say) Fortran compilers from the 50s?

The difference is the author has zero clue what they’re talking about and likely vibe coded this whole waste of time post.