In this sub-series, I'm normalizing knowledge between WPF, UMG and React UI by going over their concepts together in a head to head to head comparison. 

Again, this is Notebook LM. 101 References on this one. I had to trim the first few minutes with Audacity as my prompt oversteered and produced a bunch of weird repitition and junk. I mispelt my meta-prompt I gave to chatGPT to produce the prompt I gave to Notebook LM.

Here's the prompt:

```
You are writing Podcast Episode 000 for a special mini-series called “UI Rosetta Stone”.
Audience: experienced UI devs coming from WPF/XAML, Unreal UMG/Slate, and React/web.
Goal: explain the *runtime + tooling* model for each stack at a “controls and workflow” level (not deep engine internals).
Tone: direct, practical, engineering-first. Assume middle to senior devs.
Must cover:
- WPF runtime: .NET CLR, Dispatcher/UI thread, layout+render pipeline at a high level, app executable + OS integration.
- Unreal runtime: what Slate is, how UMG sits on top, game loop + frame budget context, PIE vs packaged build.
- Web runtime: browser JS engine (V8/SpiderMonkey/etc), DOM/CSS/layout, React on top, plus Node/server accessed via browser.
- Debugging in each: Visual Studio debugger + WPF inspection tools; Unreal Widget Reflector/Slate tools + logs; browser DevTools + React DevTools.
- Dev environments: Visual Studio vs VS Code vs Unreal Editor tooling, typical iteration loops.
- Source control workflows: git, Perforce, SVN, Mercurial — where each commonly appears and why (big binaries, branching, CI realities).
Output format:
1) Title
2) 2–3 sentence episode synopsis
3) Segment outline with timestamps (rough)
4) Full narration script (spoken-word, no code)
5) “Crosswalk” table: concept → WPF term → Unreal term → Web/React term
6) Show notes: bullets + key terms glossary
Rules:
- Don’t invent specific tool feature claims you’re unsure about. If uncertain, write “(verify)” inline.
- Keep examples conceptual (no code).


```



This episode includes AI-generated content.