The Duran ·Alex Christoforou and Alexander Mercouris discuss what they describe as Ukraine's worsening military, financial, and diplomatic position. Mercouris attributes a collapsing front and tax base to Russian strikes, treats a reported Lyman counterattack as unconfirmed public-relations warfare, and says US approaches to Moscow through Ratcliffe's pressure and Witkoff and Kushner's inducements both failed. He reports that Putin told Trump the war ends if Washington stops helping Ukraine. These statements remain the hosts' claims, not independently verified facts.

No Priors ·Chess.com co-founder and CEO Erik Allebest describes the company's growth, its financing choices, the continuing anti-cheating problem, and a view of AI as a way to support learning and product coaching rather than simply replace human skill.

Dwarkesh Podcast ·Ryan Greenblatt and Dwarkesh Patel examine whether increasingly capable systems could automate AI R&D and create a rapid feedback loop. Greenblatt argues that verifiable research tasks, scaling, and transfer could make acceleration plausible, while Patel tests the argument against bottlenecks in data, experimentation, and real-world work. The latter half shifts to alignment: both speakers discuss reward hacking, the risk of superficial remediation, transparency, and governance. Forecasts and takeover scenarios remain explicitly attributed and unresolved.

Acquired ·Ben Gilbert and David Rosenthal reconstruct Disney's history from the 1984 corporate crisis through the Eisner-Wells-Katzenberg turnaround. Their account treats animation as the creative core of a wider flywheel: successful stories feed theatrical releases, home video, consumer products, Broadway, resorts, and parks. Capital Cities/ABC added distribution and, unexpectedly, ESPN, whose cable affiliate-fee economics became a major profit engine. The same period also demonstrates the fragility of management systems: after Frank Wells's death, Katzenberg's exit, animation decline, the September 11 shock, and shareholder revolt, Disney again faced strategic and governance pressure. The middle of the episode uses Pixar to explain Bob Iger's response. Pixar combined computer-graphics technology, an iterative creative culture, and durable characters, while Steve Jobs's circumstances made Disney the most plausible long-term home. The hosts present Pixar, Marvel, and Lucasfilm as acquisitions that restored Disney's creative pipeline and supplied roughly two decades of franchise growth. This is their interpretation of the record, not independent verification of every valuation, profit estimate, or negotiating detail. The concluding analysis argues that streaming changed the environment more profoundly than any individual executive choice. Disney+ asks a quality-focused brand to supply continuous content, replaces bundle revenue with active subscriber economics, and competes against Netflix's scale while parks and sports remain strategically distinct. The bear case is subscale streaming, reduced reach, and franchise exhaustion; the bull case is that Disney's generational stories, parks, and institutional ability to steward external IP remain unusually durable. The hosts ultimately expect survival and selective prosperity, but not a simple return to the structural abundance of peak cable, home video, and theatrical distribution.

The Peterman Pod ·Ryan Peterman interviews Anders Hejlsberg about TypeScript's origins, the native rewrite of its compiler, programming-language design, and software engineering in the age of AI. Hejlsberg explains that TypeScript began in JavaScript because self-hosting kept the project inside its target ecosystem and enabled broad tooling and platform reach. He describes the native rewrite as a performance and scalability project, with shared-memory concurrency and multi-core utilization as important motivations. The team chose to port the existing compiler to preserve semantics and compatibility rather than start over. The conversation closes with a cautious view of AI-assisted programming: agents can write substantial amounts of code, but engineers still need to understand, review, and take responsibility for the result.