Software Unscripted

The episode contains several genuinely non-obvious claims per the memory-safety/correctness/safety tripartite distinction, checked arithmetic being off by default in Rust safe builds, and the economics of linear developer salary vs. exponential software asset value. However, roughly a third of the runtime is occupied by mutual Zig appreciation, wandering LLM commentary, and soft landing-pad questions that dilute overall density.

“memory safety is one of a thousand in terms of correctness. And yet our view of correctness I think is too small. It needs to be bigger as an industry.”

“by default in a safe build, it's disabled. And what people don't know is in Zig, uh, and positively speaking, I think I'm sure that Rust will change this default, and they really should. In safe builds, it must be on.”

The physical-vs-logical memory safety distinction is articulated more sharply here than in most industry discourse, and the supply-chain-attack argument inverting the 'memory-safe language = secure' assumption is genuinely contrarian with a practitioner basis. The Nabokov/Hemingway language analogy for correctness being a design property rather than a language property is an original framing; the LLM section recycles broadly circulating takes and drags the originality score down.

“it's kind of like saying, I'm going to choose the language I grew up speaking as a baby from my parents... if I speak Russian, I'll become Nabokov, and if I speak English, I can become Hemingway. So I'm expecting English to make me a great writer.”

“most Rust developers I chat to uh, don't realize it doesn't give you logical memory safety, it gives you only physical memory safety”

Joran Greef is an authentic practitioner who built a production distributed financial database from scratch in three and a half years, operates it for major financial institutions, passed a rigorous Jepsen audit, and ran his own in-house DST fleet - not a conference-circuit thought leader. His deep specificity about systems-level tradeoffs reflects genuine hands-on experience rather than borrowed frameworks.

“we built everything in Tiger Beetle to very high standard. We didn't take anything off the shelf. So we built every line of code is handcrafted, very high standards, tight, strict tolerances. And we got to production in three and a half years.”

“he actually could also use antithesis. So he could use their DST against us. Um, and he didn't find anything like that.”

The episode delivers several concrete, verifiable specifics - the 1,024-core Finland DST fleet, 700x speedup yielding ~2,000 simulated years per day, 60ms SLA for multi-regional deployment, $256K TigerBeetle donation matched to $500K total - which anchor the technical claims solidly. The main drag is that customers are described only by category ('second biggest brokerage in a country') and there are 10,000 assertions claimed without any breakdown or external citation.

“there's a fleet of 1024 cores dedicated Ah, they're in Finland... There's a speed up factor of around 700. So one second on one core is worth 700 seconds and we've got a thousand cores so it's like 2000 years a day of simulated runtime”

“some of the SLAs are like 60 milliseconds even for multi regional deployment which is like incredibly tight”

Richard Feldman is a technically literate host who adds genuine substance - notably the Rust global-allocator ecosystem point and the out-of-memory attack vector hypothesis - but the conversation tips heavily toward mutual agreement, especially in the LLM and Zig sections, with almost no productive pushback or probing of unchallenged assertions. Follow-up questions are present but tend to extend rather than interrogate the guest's claims.

“I would bet that if you had used Rust or you had used JavaScript that Kyle would have been able to find ways to break Tiger Beetle or cause it to go down by exploiting out of memory errors”

“I often wonder if there's all this talk about large language models making people able to get stuff off the ground faster and, and a lot of the rhetoric around that kind of reminds me of the NPM stuff”