Mikeal and Chris welcome (back) special guest Fred K. Schott, who you may recall from our episode on Pika. This time, we’re talking ESM: what it is, what’s new about it, why it’s the future, writing libraries with it, and much more.
Jerod assembles a team of WebRTC experts (Suz, Feross, Mikeal) for a deep, deep dive on this practically-ubiquitous yet still-complicated web API.
We review its history, share really cool applications using the tech, provide an excellent primer on what you need to know about it, and details some production gotchas. ALSO we celebrate how Feross single-handedly “upgraded the internet”! 🙌
An amalgam of interest on this week’s episode starting with a peek at what’s finally coming in Vue 3. We talk about the process of change in the Vue ecosystem and what interesting features are coming either very soon or not for a while depending on how you view time right now. Then, the panelists share what they’ve learned recently, and finish off with shout outs to the projects, ideas, and people we’re appreciative of.
KBall, Jerod, and Nick Nisi dive into GraphQL – what it can do, what the challenges are, and how it differs from REST – all with a generous helping of metaphor about buffets, restaurants, and of course bacon.
Blitz.js creator Brandon Bayer joins Jerod to dive deep into the foundational principles of this fullstack React framework. We talk about its inspiration (Ruby on Rails), its differentiation (a “no-API” data layer), and its aspirations (built-in auth, plugins, recipes, and more).
Did you know Feross taught Web Security at Stanford last Fall? On this episode, Divya and Nick enroll in his security school to learn about XSS, CSP, ambient authority, and a whole lot more.
Then Feross shares his new app, Nick talks fiction books, and Jerod switches coding fonts.
We often try new frameworks and tools in side projects or throwaway contexts, but you don’t learn that much about a thing until you use it to build something real. That’s why we have Mat Ryer and David Hernandez joining us to share their experience of using Svelte while building their new startup, Pace.dev.
JS Danger is back! Suz, Emma, and Divya square off in our don’t-call-it-jeopardy game show. Will Emma totally redeem herself? Are Divya’s trivia skills as on point as her debate skills? Will Suz murder Jerod in a fit of terrible-question-inducing rage?! Listen and play along!
This is a wide-ranging discussion about all things Deno. We discuss why they’re using Rust, how they’re rewriting parts of the TypeScript compiler, their take on package management, what adoption looks like, their code of conduct, and more.
Node 14, Vue’s Vite, and
is-promise are in the news. We’ve got some working from home tips and unpopular opinions to share. And… shout outs! 👏
Gatsby creator Kyle Mathews joins Jerod fresh off the launch of incremental builds to tell the story of this feature that’s 3 years in the making. We talk about Kyle’s vision for Gatsby, why incremental builds took so long, why it’s not part of the open source tool, how he makes decisions between Cloud and open source features, and more.
This week Feross and Emma chat with Segun Adebayo about Chakra UI, a modular React component library that’s changing the game for design systems and app development.
Emma, Divya, and Suz are joined by Quincy Larson from freeCodeCamp where they chat about virtual conferences. Are they better than in-person conferences? What are the differences? Let’s find out!
Our Jeopardy-style (but don’t call it Jeopardy) game is back! This time Jerod plays the part of Alex Trabeck and Emma tries her hand at contestant-ing. Can Scott Tolinski from the Syntax podcast hang with Emma and Nick? Listen and play along!
Divya and Jerod welcome ZEIT founder Guillermo Rauch to the show for a deep discussion on the state of JAMstack, what’s new & exciting with Next.js, and some big picture analysis of where the industry is heading.
Jerod and KBall are joined by Micro Frontends in Action author Michael Geers to discuss (you guessed it) micro frontend architecture. We ask: what is the concept? How is it similar/different to micro services? Who is it best fitted for? How do you put it in practice? And much more.
With most of us working from home for the first time (or for a long time), we thought it’d be a good idea to share our experiences and opinions on how to manage it. We discuss how to optimize your location, your schedule, your communications, and the rest of you life during these stressful times.
Tom Preston-Werner (co-founder of GitHub, board member at Netlify) joins the party and brings his new, opinionated, full-stack, serverless web app framework with him. Will Redwood help usher in the future Tom predicted back in 2018? We discuss that and a whole lot more on this must-listen episode.
We sit down with Tobias Koppers of webpack fame to talk about his life as a full-time maintainer of one of the most highly used (4 million+ dependent repos!) and influential tools in all of the web.
Things we ask Tobias include: how he got here, how he pays himself, has he ever gotten a raise, what his typical day is like, how he decides what to work on, if he pays attention to the competition, and if he’s ever suffered from burnout.
This week we’re talking about building technical courses! From video courses to written courses, we’ll give you our tips for building an effective and memorable course.
Dustin Schau joins the party to talk about the state of Gatsby and the changes and improvements to it in the last year. We talk about what Gatsby delivers to the front end and how it does it quickly with improvements to the build system. Dustin also fields our questions and talks about Gatsby Cloud and where things are going.
KBall interviews Brian Leroux in a wide-ranging discussion covering “Progressive Bundling” with native ES Modules, building infrastructure as code, and what the future of JamStack and serverless deployment might look like.
Divya leads a deep discussion with Jerod, KBall, and Nick on what’s stagnating in browsers. What has remained the same in browser tech over the last 20 years that remains a pain point in working with browsers? For example - Focus in browsers hasn’t changed much in 20 years. Why is that and how do we go about making all the stale things in browser tech better?