About this talk
I'm building a programming language. When I got to the frontend, I ran into a problem: React's mental model is elegant, but the mental model is at odds with the code. Hooks, effects, and render passes create a runtime that bears little resemblance to the code we write. The Elm programming language works differently and its architecture (TEA = The Elm Architecture) has been adopted by other tools over the years. So I copied it as well. My language embeds TEA at the language level, not as a library. This unlocks time-travel debugging, reproducible application state and serializable bug reports that include the entire program state. This talk covers the quick introduction of my language, TEA, why TEA is the right fit and what becomes possible when the architecture is baked into the language itself.