{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Better with Kent","title":"The Framework wars are over. Why no one dethroned React","html":"","width":"100%","height":180,"duration":693,"description":"Kent reacts to Dax's question on X — why no framework dethroned React — and connects it to Jobs Theory, network effects, and why framework choice matters less when agents write the code.Chapters00:00 — Why did nobody dethrone React?00:24 — Dax's question on X00:49 — React is the last UI library (2020)02:47 — Functional first, then social and emotional03:36 — What made React functionally better06:43 — Network effects and \"nobody got fired for choosing React\"07:38 — Why framework choice matters less with agents09:27 — Jobs Theory: apply this to everything you ship11:14 — Wrap-upBetter with Kent — durable skills for people who ship software.Every few years the internet declares the framework wars over — usually with React as the loser. Svelte was going to win. Then Solid. Vue had its moment. Angular never left. And somehow, after a decade of \"React is dead\" takes, React is still the default for an absurd amount of real product work.Kent's take: React won functionally first (state sync, composition, drop-in UI focus), then socially and emotionally once it hit critical mass. Challengers can still be \"better\" on paper — but once agents can use any capable stack, the throne fight stops mattering the way it used to.LinksDax (@thdxr) — why no framework dethroned ReactKent (2020) — React is the last UI library anyone needs to learnBetter with Kent — Practical Jobs TheoryWatch on YouTubeBetter with KentReactBecome an Epic Product Engineer","thumbnail_url":"https://img.transistorcdn.com/0wjkGi4W_ChGSElUbb2U5VdTqEiZ7zMTtpZP0KLENes/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9jZmU5/ZWRlNjZkMDRkOGU3/ZTNkMWY4ZjgyNGRi/ZTJiMS5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}