717: Better DX for Web Components, What Was Popular That Now We’re Used To?

The hosts discuss their personal efforts to improve their video quality for streaming or recording. Dave experimented with camera angles, background setup, and lighting accessories like Elgato light strips and Apple post-processing effects, often on a budget. They also indulge in hobby projects—Dave built a custom mount for his van and upgraded his Starlink installation, blending tech tinkering with hobby interests. The conversation touches on the joy and pitfalls of hobbies, from hardware store trips to guitar repair challenges, highlighting how hobbies can be both rewarding and time-consuming.

A significant portion of the episode focuses on older and current web development technologies: the evolution of CSS preprocessors like Sass, the decline of jQuery, and the persistence of tools like static site generators. They reflect on technologies once hyped—such as Adobe Flex or PhoneGap—that faded or transformed over time. Discussions also explore modern frameworks and how they could be simplified or replaced, emphasizing that many complex tools are often used for internal or historical reasons rather than necessity. The hosts advocate for more lightweight, effective solutions like web components and native technologies, including discussions on reactivity, component composition, and the ongoing evolution of web APIs.

The hosts speculate on what the web still can't do—such as holograms or perfect flow content—and what improvements are on the horizon. They highlight missing or underdeveloped features like styling grid cell borders directly, flowing content between grid cells, and more advanced text rendering behaviors. They discuss recent API advancements—CSS subgrid, container queries, new animation APIs—and how these are expanding the web's capabilities. The conversation emphasizes the importance of ongoing innovation and surprising improvements that push the limits of web technology.

Another major topic is the growth of web components and how to better structure and compose custom elements, especially for developers coming from frameworks like React. They discuss the concept of 'leaf' components—self-contained, isolated widgets that don't need complex hierarchy—and how web components can fit into various architectures with Shadow DOM and slots. The hosts recommend separating component rendering from UI orchestration and considering tools like custom element manifests for better developer experience. They also reflect on the importance of reducing complexity in JavaScript frameworks by embracing native web standards.