Show Notes
A deeper follow-up to our earlier JavaScript discussions, this episode digs into why the ecosystem keeps tripping over the same problems. We unpack supply-chain risk, package culture, governance gaps, and the uncomfortable truth that some issues aren’t technical at all: they’re cultural. JavaScript isn’t going away, but that doesn’t mean it should remain the default foundation for everything we build.
More from The Beer Driven Devs
Seven Adobe apps cloned in a week. A toolkit that reverse engineers anything. Matt argues the software profession isn't changing — it's ending — and that capability moat is rapidly drying up.
An OpenAI agent got into a Medicare statistics portal, and the Prime Minister got in front of a camera. Matt and Liam ask what actually happened, whether it's as frightening as it sounds, and who ends up carrying the can when nobody told the agent to do it.
A correction to last episode turns into a question neither of us had thought to ask: when a vendor drops your package into a default template, who agreed to the support burden that comes with it?
Matt walks Liam through a year of over-thinking auth for a mobile app, only to realise the answer was something we all used to do and simply forgot. That leads to a bigger question: what else have we been talked out of doing ourselves?
Liam takes the wheel for a personal history of WPF — from battleship-grey WinForms, through the promise of Avalon, into the ideas that still quietly shape every XAML framework we use today.