It’s especially ironic considering the title and the fact that many employees are not US citizens.

The situation in which people exchange favors within their mutually beneficial personal networks seems to be the basic and typical way things function. It’s actually remarkable that we are able to resist this tendency and normalize fair and impartial institutions.

Why for you is innate grit any more commendable than innate intelligence?

Can’t speak for others but I think I learnt grit. Didn’t really show it very young but by 16 I was just able to grind through anything.

Are they even a developer? “Safety and alignment” as AI buzzwords are quite different from “security and privacy”. In any case, I wouldn’t take a random person with a sinecure job as exemplary of anything.

HTML also comes with a button and an accordion.

I had to vibe code a proxy to hide tokens from agents (https://github.com/vladimirkras/prxlocal) because I haven’t found any good solution either. I planned to add genai otel stuff that could be piped into some tool to view dialogues and tool calls and so on, but I haven’t found any good setup that doesn’t require lots of manual coding yet. It’s really weird that there are no solutions in that space.

nice, I'm working on something similar with macroons so the tokens can be arbitrarily scopes in time and capability too.

Mine uses an Envoy sidecar on a sandbox container.

https://github.com/dtkav/agent-creds

Expressive linting seems more useful for that than lax typing without null safety.

What are the exact features that require it to be a new language with new syntax?

Reactive DOM updates – When you change state, the compiler tracks dependencies and generates efficient update code. In WebCC C++, you manually manage every DOM operation and call flush().

JSX-like view syntax – Embedding HTML with expressions, conditionals (<if>), and loops (<for>) requires parser support. Doing this with C++ macros would be unmaintainable.

Scoped CSS – The compiler rewrites selectors and injects scope attributes automatically. In WebCC, you write all styling imperatively in C++.

Component lifecycle – init{}, mount{}, tick{}, view{} blocks integrate with the reactive system. WebCC requires manual event loop setup and state management.

Efficient array rendering – Array loops track elements by key, so adding/removing/reordering items only updates the affected DOM nodes. The compiler generates the diffing and patching logic automatically.

Fine-grained reactivity – The compiler analyzes which DOM nodes depend on which state variables, generating minimal update code that only touches affected elements.

From a DX perspective: Coi lets you write <button onclick={increment}>{count}</button> with automatic reactivity. WebCC is a low-level toolkit – Coi is a high-level language that compiles to it, handling the reactive updates and DOM boilerplate automatically.

These features require a new language because they need compiler-level integration – reactive tracking, CSS scoping, JSX-like templates, and efficient array updates can't be retrofitted into C++ without creating an unmaintainable mess of macros and preprocessors. A component-based declarative language is fundamentally better suited for building UIs than imperative C++.

TL;DR There is no secret sauce, it's the same set of techniques you’ve seen in most PostgreSQL scaling guides. Those techniques do work.

The article puts punctuation into its rendering of the original text. That confused me too.

I'll note that it's not this decision is not coming from the newspaper article's writer, it's coming from any common transliteration of the manuscript that you'll find. But it's clearly a transliteration decision made because the people doing this assume it is an interjection, and they're using modern punctuation rules accordingly.

> But it's clearly a transliteration decision made because the people doing this assume it is an interjection, and they're using modern punctuation rules accordingly.

I think that's what I missed.