I don't quite see it that way, Peter. I would like to see the "continuously updated" aspect be the burden of the W3C, et al, and the browser creators, instead the burden of the developers to continuously jump through hoops to make "front-end sense" of the tangled mess of browsers and standards that become "official" once every few decades.
Instead of major milestone releases on the part of standards groups and browser creators, I'd rather them take on one enhancement at a time and implement it across the spectrum of browsers. Instead of FF3 and FF4, IE7, IE8, and IE9... there's just FF and IE, each with "nightlies" enhanced a little bit each day or so. I realize, however, that browser creators have a vested interest in maintaining incompatibilities. (Although I fail to see the continued business benefit in doing so; it's not like they're selling the browsers or really getting much benefit from being on the desktop of computers sold, as it was 15 years decade ago...) A case-in-point is a recent book I *almost* purchased from SitePoint.com, "HTML5 and CSS3 for the Real World". I worked through some of the sample material and the by the time I set up the project that was to be created by the end of the book, I found that even IE9 couldn't implement all of the features on the homepage of the project. HTML5 and CSS3 for the "Real World" should work in all browsers (the latest official releases, anyway...). I don't development for anything but the latest FF, Chrome, Safari, IE8 and IE9. Everyone but IE users update very quickly, and I'm not going to continue to support any IE users who are more than two versions behind the latest release. That's just ridiculous. But all said, things were complicated enough trying to deal with desktop browsers... now I'm throwing smart phone browser issues into the mix, as well. Just more complication to add frustration. It's been a looooong week... -----Original Message----- From: Peter Boughton [mailto:[email protected]] Sent: Saturday, June 25, 2011 10:09 AM To: cf-talk Subject: Re: Need some perspective... >We need some sort of "continuously updated standard" with >more nimble browser updating, as well. That is *EXACTLY* what HTML5 is now - an evolving standard which you CAN use on the desktop right now (if you do things correctly; detect features not browsers). http://html5doctor.com/how-to-use-html5-in-your-client-work-right-now/ Also: > The WHATWG HTML spec can now be considered a "living standard". > It's more mature than any version of the HTML specification to > date, so it made no sense for us to keep referring to it as > merely a draft. >From http://blog.whatwg.org/html-is-the-new-html5 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345675 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
