> It's much more important to focus on what features are implemented and > what you CAN use rather than throwing up your hands and acting like > all of it is out of reach.
I certainly don't claim to understand the standards "process" (which doesn't seem like much of a "process" anyway :oP), but as fast as technology and the programming that makes it work changes, to have an official standard take from 2008 (first working draft) to 2022 to be "fully implemented", seems a bit bizarre... 14 years? By 2022, we may not even *use* browsers anymore, much less HTML5! I'm just complaining about the age-old browser incompatibilities and having to add mobile development into that mix. Perhaps if one "group" of browsers work closely together, implementing an incremental approach to development of features simultaneously, then developers wouldn't have to endure the "fits and starts" of random feature inclusion and have to bother with browser *or* feature detection. I'd love to hear all the browser vendors announce, "the HTML5 video tag is now working on all our browsers, so enjoy! And next, we'll be all working on the HTML5 audio tag! As it stands now, we need massive charts just to check on every new tag that is developed to see if it's something we can use based on browser targets. (Yes, I know, do feature detection. But that's just as much a pain as "graceful degradation.") And, as I'm sure I don't understand the standards process, would someone please explain why it takes 14 years to develop a new standard? There is something wrong with this picture... -----Original Message----- From: Sean Corfield [mailto:[email protected]] Sent: Saturday, June 25, 2011 6:52 PM To: cf-talk Subject: Re: Need some perspective... On Sat, Jun 25, 2011 at 6:53 AM, Rick Faircloth <[email protected]> wrote: > Something's got to change with the development of standards. > HTML5 not "complete and full interoperable" until 2022 !?!?! You need to read a bit deeper into the subject - as Peter suggests. Standards organizations have to set future milestones but that doesn't mean you can't use HTML5 until then. I'll draw a parallel with my own experience with C++. The standard itself is officially updated once a decade. In reality, updating is an ongoing process and vendors track the changes and add features for compliance over time. That means that most vendors implement most things in any current draft over time and by the time the official document is published by ISO, vendors are either already compliant or very close to it, depending on how much change occurred during the final public review period. > We need some sort of "continuously updated standard" with > more nimble browser updating, as well. I'd say we have exactly that. > By 2022, official standards and de facto standards are going > to be so far apart at the current rate of change, we will > all have gone insane. Like I say, you don't understand the standards process (or you're misreading it). It's much more important to focus on what features are implemented and what you CAN use rather than throwing up your hands and acting like all of it is out of reach. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ Railo Technologies, Inc. -- http://www.getrailo.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:345718 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
