Software can be finished - Ross Wintle
There’s quite a crossover between resilience and longevity:
- Understand the requirements
- Keep scope small and fixed
- Reduce dependencies
- Produce static output
- Increase Quality Assurance
Reimagining Single-Page Applications With Progressive Enhancement – Smashing Magazine
Some really great thinking here by Heydon on how to make single page apps but using HTML for the views instead of relying on client-side JavaScript for the rendering. He explains the code he’s using, but what really matters here isn’t the specific solution; it’s the approach. Smart!
Related links
What You Need to Know about Modern CSS (2025 Edition) – Frontend Masters Blog
Here’s a comprehensive round-up of new CSS that you can use right now—you can expect to see some of this in action at Web Day Out!
Polishing your typography with line height units | WebKit
I should be using the lh and rlh units more enough—they’re supported across the board!
A pragmatic browser support strategy | Go Make Things
- Basic functionality should work on any device that can access the web.
- Extras and flourishes are treated as progressive enhancements for modern devices.
- The UI can look different and even clunky on older devices and browsers, as long as it doesn’t break rule #1.
Progressive enhancement brings everyone in - The History of the Web
This is a great history of the idea of progressive enhancement:
It is an idea that has been lasting and enduring for two decades, and will continue.
Related posts
Simplify
Reminding myself just how much you can do with CSS these days.
Making the new Salter Cane website
A redesign with modern CSS.
Browser support
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Applying the four principles of accessibility
Here’s how I interpret the top-level guidance in the Web Content Accessibility Guidelines.
Speculation rules
A performance boost in Chrome.