>No-one who is actually developing web sites can use all the bleeding edge stuff the day it's released anyway
Progressive enhancement disagrees. OK well maybe not quite but all the new features ...
I've used a few sites in the last couple of days using the new HTML5-ish drag+drop file uploads in the wild (not yet officially released browsers working to not yet officially completed specs).
> Progressive enhancement disagrees. OK well maybe not quite but all the new features ...
Really? How do you progressively enhance a video site to use HTML5 video, or a site-wide menu system to use CSS3 transitions? The alternatives are things like Flash and JavaScript, which we have been using for a while anyway. However, if you have to write the Flash/JavaScript version anyway, where is the benefit in also supporting HTML5 and CSS3?
Progessive enhancement is a great idea for minor details, like having a site use a subtle rounding on corners when a browser supports it but just square cutting them otherwise if that's the visual effect you're looking for. However, in a world with desktop vs. mobile sites, persistent local storage, multimedia content, etc., it's becoming ever clearer that the idea of a single page with progressive enhancement doesn't scale to support fundamental functionality in a complex web app or interactive site, and multiple versions of the presentation/functionality are needed to cope with the ever increasing and diversifying range of visitors we need to support.
Progressive enhancement disagrees. OK well maybe not quite but all the new features ...
I've used a few sites in the last couple of days using the new HTML5-ish drag+drop file uploads in the wild (not yet officially released browsers working to not yet officially completed specs).