EPISODE · Aug 7, 2019 · 1H 19M
Object references considered helpful
from Frontend First · host Frontend First
Topics include: 0:00 – Unique keys for lists in React and Ember 8:40 – Why Handlebars feels safe 9:34 – Solving a stale state React hooks bug, and how Ember avoids this via object references 24:29 – ESPN's website and self-imposed technical constraints 28:10 – React in Codesandbox 36:53 – Tradeoffs between "magic" in a framework vs. learning how to wire things up yourself - especially in a fast-moving ecosystem like JavaScript 50:35 – Hooks vs. components, and clarity in boundaries 53:29 – Pairing with Tuple experience Listener questions: 55:43 – How can you limit FastBoot from turning user-specific bugs into bugs that take down your entire production app? (@davewasmer) 1:10:47 – What's the future of web components? (selbyk) Sponsors: TrueCoach, check out their engineering culture and hiring pages Links: Sam's tweet on list keys in React Codesandbox StaticKit.com Tuple, an app for remote pairing Stencil.js APIs are about policy
Embed this episode
What this episode covers
Sam and Ryan talk about a stale state bug in a React app, and how Ember's decision to use object references helps developers avoid these sorts of bugs. They also talk about how Ember's framework magic can sometimes make folks feel ill-equipped to work in the larger JavaScript ecosystem, despite being extremely pleasant. Then they answer some listener questions.
Ready to play
Object references considered helpful
No transcript for this episode yet
Similar Episodes
No similar episodes found.
Similar Podcasts
No similar podcasts found.