Hasty Treat - Old Browsers, Fallbacks and Polyfills - Part 1

Episode Summary

Executive Summary: The episode focuses on deciding whether to support older browsers, how to test across desktop and mobile devices, and which tools make cross-browser validation practical. Wes and Scott argue that browser support should be driven by audience, business value, and cost, and that real-device testing plus tools like Can I Use, BrowserSync, and remote debugging are essential for reliable modern web development.

Main Topics: Deciding whether to support older browsers: The hosts explain that browser support should be based on audience analytics, the type of product, and the business cost of compatibility work. Government and education sites often need broader support, while developer-focused products usually do not. Using analytics to guide support decisions: They emphasize Google Analytics and audience knowledge as the best way to determine which browsers and devices matter most, citing cases where a tiny browser share still represented important revenue. Testing on real devices vs emulation: They argue that emulators are useful, but real hardware is more reliable for discovering layout, rendering, and interaction issues across desktop and mobile browsers. Tools for browser compatibility research: Can I Use is presented as the go-to reference for checking feature support before building, helping teams avoid surprises and choose fallbacks or polyfills proactively. Mobile browser fragmentation and remote debugging: The discussion covers the complexity of mobile testing, especially Android browser diversity and Safari quirks, plus the need for remote debugging on actual phones and tablets. Syncing and live-testing workflows: BrowserSync and similar tools are highlighted for syncing scrolling, form submits, and CSS changes across many devices to speed up debugging and responsive design checks.

Key Arguments: Browser support should be determined by your audience, not by default assumptions about all users. Government, education, and enterprise contexts often require more legacy support than developer-focused products. A very small percentage of traffic can still matter if those users represent major revenue or critical actions. Real-device testing catches issues that emulation can miss, especially with rendering and mobile browser behavior. Can I Use helps developers know browser support upfront, reducing guesswork and avoiding unsupported features. Mobile Safari and Android browser diversity remain the most common sources of compatibility frustration. BrowserSync and remote debugging make it easier to test changes quickly across multiple devices in parallel.

Data Points: View School catalog size: 160+ lessons - Promoted as part of the sponsor mention for the new subscription model. View School monthly price: $12/month - Full catalog access including the VueJS Masterclass. View School intro offer: $5 for the first month - Discount for Syntax listeners. Old browser support in one example: IE11 at less than 1% of traffic - Still worth supporting because those visitors were purchasing expensive team licenses. Team license value: Hundreds, if not thousands, of dollars - Used to justify fixing IE11 compatibility despite low traffic share. Legacy browser usage example: IE7 at 0.5% of users - Agencies used this low usage number to justify dropping IE7 support from contracts. Testing window for Windows images: 90-day free images - Modern.ie Windows VMs can be rolled back using snapshots before expiration. Number of devices in one testing drawer: 15-20 phones - Scott keeps many phones around for testing different Android and iOS versions.

Pivotal Quotes: "emulation is great, but there's no substitute for the real thing." — Scott: On why real devices are preferred for testing over virtualized or browser-based emulation. "we need to now say, in all contracts going forward, that we will not be supporting IE7 regardless of your needs." — Wes: Describing an agency decision to stop supporting an obsolete browser after reviewing usage data. "nothing better than the real thing." — Scott: Summarizing the value of physical devices and real-world testing conditions.

Implications: Teams should base browser support on measurable audience and revenue impact, not fear of missing edge cases. Real-device testing, feature support research, and remote debugging will remain essential as browser fragmentation shifts from desktop to mobile.