Our Web Dev Wish List

Episode Summary

Executive Summary: Scott and Wes brainstorm web-dev and browser features they wish were built in by default, criticizing awkward APIs and extra boilerplate across HTML, CSS, JavaScript, React, tooling, and browsers. They emphasize ergonomics, accessibility, and performance, while noting several desired features are already emerging in modern browsers and tools.

Main Topics: Web dev wish list / “just do it for me” APIs: The episode’s central theme is frustration with APIs that require too much manual work when browsers or frameworks could handle it automatically. HTML and browser-native controls: They discuss better page transitions, improved date/number inputs, richer drag-and-drop, and built-in data binding and auth primitives. JavaScript and React ergonomics: They complain about TypeScript interfaces vs types, requestAnimationFrame, React’s dependency arrays, useLayoutEffect/isomorphic patterns, fragments, and className/class quirks. CSS shortcomings and upcoming improvements: They want better overflow behavior, fluid text sizing, GPU-friendly transforms, gradient borders, and animating height:auto; they also note new CSS individual transform properties. Tooling and ecosystem friction: They vent about peer dependency hassles, package installation syncing, editor reloads, browser updates, file casing in Git, and test runner complexity. Sponsors and product shout-outs: Mid-episode sponsor reads for Linode, Sentry, and FreshBooks are integrated into the conversation, emphasizing hosting, error tracking, and bookkeeping automation. Sick picks: Ryobi hot glue gun and Arc browser: The episode ends with two recommendations: a battery-powered Ryobi hot glue gun and the Arc browser, which Scott praises for its command-palette-driven workflow.

Key Arguments: Browsers should provide higher-level primitives so developers don’t have to reimplement common UI behaviors like transitions, drag-and-drop, and fluid animations. Some existing APIs are too low-level or awkwardly designed, forcing unnecessary boilerplate or framework workarounds. Framework ergonomics matter: React’s dependency arrays, useLayoutEffect in SSR, and fragment/className quirks add avoidable cognitive overhead. CSS could be more expressive and safer by default, especially for overflow, transforms, gradient borders, and animating intrinsic sizes. Developer tooling should reduce manual steps by auto-syncing dependencies, handling peer deps better, and running tests without transpilation overhead. Browser and platform features should be more accessible out of the box, even if lower-level primitives still exist for library authors. Several complaints are partly mitigated by newer APIs or browser support, but the hosts want those improvements to be standard, ubiquitous, and easy to use.

Data Points: Chrome support for individual transform properties: Chrome 104 - They note CSS individual transform properties like rotate/translate have shipped in Chrome 104. Free credit from Linode: $100 - Linode sponsorship mentions a $100 free credit offer. Sentry promo code free trial: 2 months - They mention using a coupon code on Sentry for two free months. FreshBooks free trial: 30 days - FreshBooks sponsorship includes a 30-day free trial. Ryobi hot glue gun price: $30 - Wes says the battery-powered Ryobi hot glue gun costs about $30. Browser usage mentioned: Opera usage is pretty small - They discuss browser support concerns for CSS features, noting Opera’s small usage share. Retweets on a tweet about input valueAsNumber/valueAsDate: 233 retweets - Wes cites a tweet about date/number input properties that got 233 retweets.

Pivotal Quotes: "Why doesn't it just do that instead of us having to fuss around with it and to take care of these things?" — Scott Tolinsky: Opening framing for the episode’s central complaint-driven premise. "I want to be able to style the date picker and make it not crappy, right?" — Scott Tolinsky: Discussing the desire for better native date inputs that are both functional and customizable. "If you could think, like, what are some ways that you could make a web browser different? Like, actually different." — Wes Bos: Introducing the Arc browser as a radically different browser experience.

Implications: The episode highlights a broad demand for more ergonomic, opinionated web platform APIs. For developers, better defaults could mean less boilerplate, fewer bugs, and more accessible experiences; for browser vendors, the challenge is shipping powerful primitives without sacrificing flexibility.