3 ms·
I think this is a really good step in the right direction, the specification process is now matching up with the way the standard are actually implemented. I t
by daleharvey 16y ago
I think this is a really good step in the right direction, the specification process is now matching up with the way the standard are actually implemented.
I think in the last few days the w3c + whatwg have taken really positive steps, both for the understanding of the technologies and the marketing of them.
- patrickaljord 16y ago> think in the last few days the w3c + whatwg have taken really positive steps w3c releasing an HTML 5 logo and the whatwg renaming HTML 5 to HTML doesn't sound that great.
- ghshephard 16y agoThink of it as "English as Documented in OED2" versus "English as used on the street" Both definitions are actually useful in different contexts. The second one certainly allows for more flexibility in growth and development. whatwg is recognizing that HTML, like chrome, isn't as important in a particular ordinal identifier, as they are in the features they offer and the development model behind them. I'm guessing 95% of the people using chrome don't what version they are currently using - but it has never impacted web developers, or users, from making use of the browser. It also aligns with agile development practices, and, if I can stretch a bit, dvcsystems - people are free to complete new stories in the HTML definition or browser, without worrying too much about other teams work, or particular releases.
- daleharvey 16y agoI think the more people understand these technologies and their terminologies, the more people will feel comfortable using them, the more people using them the faster their development will progress. I think these last 2 announcements have drastically helped clarify things. So as a web enthusiast I do find it great