Be Prepared for Failure and Handle it Gracefully

Remember the early 2000s web dev mantra? Tiny websites (under 100KB), JavaScript only for enhancements, and robust fallbacks for everything. No JavaScript? The site still functioned perfectly, albeit less flashy. Dial-up's slow speeds necessitated this approach. Connecting to the internet alone was a multi-minute endeavor!

Those were simpler times. The limitations, in my view, fostered better web design. But broadband and fiber have rendered those constraints obsolete.

Today's web development prioritizes developer experience over user experience: build processes, framework choices, and SEO optimization dominate. Framework wars and gatekeeping have replaced discussions about elegant JavaScript-free solutions. Ultimately, it all boils down to HTML, CSS, and JavaScript; use what works.

However, the reliance on JavaScript for even basic functionality is alarming. Websites now average a hefty 2MB per page! Disable JavaScript, and you're greeted with the "white screen blizzard"—a blank page instead of content.

My recent move to a rural area brought back memories of dial-up. While my broadband is acceptable, mobile connectivity outside or during power outages is abysmal. Reader mode and JavaScript disabling (along with image lazy loading) are essential for browsing. But disabling JavaScript renders many sites unusable, resulting in that dreaded white screen.

My home WiFi handles work, shopping, and bill paying. But a recent power outage highlighted the problem. I needed the electric company's website to check service restoration, but its 3MB (plus 8.6MB in resources) mobile site failed to load, even with JavaScript enabled.

My Twitter rant yielded positive responses, pointing to examples like traintimes.org.uk and NPR's text-only version. Why not offer text-only versions of critical pages for users with unreliable internet?

While my power outage was a temporary situation, many globally experience consistently unreliable internet access. NPR's article on pandemic-era educational challenges in areas with poor internet access underscores this reality.

The constraints of early web development offered a significant advantage: websites loaded reliably on any device, anywhere. The 1996 Space Jam website exemplifies this. Developers should embrace adaptive loading strategies, ensuring accessibility for users with slow networks or low-end devices.

The above is the detailed content of Be Prepared for Failure and Handle it Gracefully. For more information, please follow other related articles on the PHP Chinese website!