Panel: Web
summary
Panelists debate concrete tradeoffs: micro frontends lacks a shared definition so applicability varies; run sites through webpagetest and Lighthouse to see real bottlenecks (waterfalls, megabyte image counts); adopt TypeScript for fewer runtime bugs; model complex UI with state machines like XState. Notes: compile-time approaches and pre-rendering reduce payloads, Rust ports of tooling (Babel) show 10–16x speedups, and devtools local overrides prove image optimization gains.
AI-written summary · about
chapters (16)
- 0:00Web panel welcome
- 1:02Panelist backgrounds
- 2:27Micro frontends hype vs reality
- 4:34Angular React or Vue
- 9:08Next big web tool
- 14:01Reliable web toolchain
- 16:27Browser compatibility quest
- 18:57State management in apps
- 20:42Open source favorites
- 24:15Becoming web performance expert
- 27:46Web dev best and worst
- 28:50Server-side rendering versus single-page apps
- 31:39Most interesting talk
- 34:07AR frameworks like Viro
- 36:16Advice for new web devs
- 40:55Closing remarks
