What are the key takeaways from this Shop Talk Show episode?

Key insights include: **Safari 26 Features:** Adopted stylesheets, anchor positioning, and web components support now available across multiple macOS versions including Sequoia and older systems, though early adopters report bugs requiring fixes in upcoming release cycles before production use.; **TypeScript Without Build Tools:** Modern deployment platforms including Deno, Cloudflare Workers, Vite, Next.js, and Astro now accept TypeScript files directly without manual build configuration. ESBuild processes TypeScript instantly by stripping types without validation, eliminating traditional build step overhead.; **Progressive Enhancement Button Problem:** Hiding submit buttons after JavaScript loads creates layout shift and flash issues. NoScript tags with embedded styles handle JavaScript-off scenarios, but the unloaded-JavaScript-available state remains unsolved, requiring careful consideration of all four state combinations.

How long is this episode of Shop Talk Show?

This episode is 54 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Shop Talk Show

683: iOS 26 Safari, Material Support on the Web, and Fixing The Button Problem

September 22, 2025

54 min episode · 2 min read

Episode

54 min

Read time

2 min

Topics

Fundraising & VC, Software Development, Product & Tech Trends

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓Safari 26 Features: Adopted stylesheets, anchor positioning, and web components support now available across multiple macOS versions including Sequoia and older systems, though early adopters report bugs requiring fixes in upcoming release cycles before production use.
✓TypeScript Without Build Tools: Modern deployment platforms including Deno, Cloudflare Workers, Vite, Next.js, and Astro now accept TypeScript files directly without manual build configuration. ESBuild processes TypeScript instantly by stripping types without validation, eliminating traditional build step overhead.
✓Progressive Enhancement Button Problem: Hiding submit buttons after JavaScript loads creates layout shift and flash issues. NoScript tags with embedded styles handle JavaScript-off scenarios, but the unloaded-JavaScript-available state remains unsolved, requiring careful consideration of all four state combinations.
✓Stack Migration Decision Framework: Evaluate technology changes using three criteria: deployment speed improvements, stability and bug frequency, and team knowledge retention. Create comparison tables listing current problems versus new stack capabilities before proposing expensive rewrites to stakeholders.

What It Covers

Safari 26 release brings new web features including web components and anchor positioning with some bugs. Discussion covers TypeScript adoption decisions, progressive enhancement challenges, and when agencies should rebuild their technology stack.

Key Questions Answered

•Safari 26 Features: Adopted stylesheets, anchor positioning, and web components support now available across multiple macOS versions including Sequoia and older systems, though early adopters report bugs requiring fixes in upcoming release cycles before production use.
•TypeScript Without Build Tools: Modern deployment platforms including Deno, Cloudflare Workers, Vite, Next.js, and Astro now accept TypeScript files directly without manual build configuration. ESBuild processes TypeScript instantly by stripping types without validation, eliminating traditional build step overhead.
•Progressive Enhancement Button Problem: Hiding submit buttons after JavaScript loads creates layout shift and flash issues. NoScript tags with embedded styles handle JavaScript-off scenarios, but the unloaded-JavaScript-available state remains unsolved, requiring careful consideration of all four state combinations.
•Stack Migration Decision Framework: Evaluate technology changes using three criteria: deployment speed improvements, stability and bug frequency, and team knowledge retention. Create comparison tables listing current problems versus new stack capabilities before proposing expensive rewrites to stakeholders.

Notable Moment

The hosts debate whether web standards should include material properties like glass, plastic, or wood textures similar to 3D design tools, questioning why CSS filters evolved but Adobe's proposed CSS shaders for materials never materialized despite clear use cases.

Know someone who'd find this useful?