{"id":16545,"date":"2012-07-23T09:32:19","date_gmt":"2012-07-23T07:32:19","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=16545"},"modified":"2012-07-23T09:32:19","modified_gmt":"2012-07-23T07:32:19","slug":"html5-splits-into-two-standards","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2012\/07\/23\/html5-splits-into-two-standards\/","title":{"rendered":"HTML5 splits into two standards"},"content":{"rendered":"\n

Just when web developers got a little bit of hope, Slashdot reports<\/a> on the bad news.<\/p>\n

Until now the two standards bodies working on HTML5 (WHATWG<\/a>\u00a0and\u00a0W3C<\/a>\u00a0) have cooperated. An announcement by WHATWG makes it clear that this is no longer true.\u00a0WHATWG is going to work on a living standard for HTML<\/a>\u00a0which will continue to evolve as more technologies are added. W3C is going the traditional and much more time consuming route of creating a traditional standard which WHATWG refers to as a ‘snapshot’ of their living standard. Of course now being free of W3C’s slower methods WHATWG can accelerate the pace of introducing new technologies to HTML5. Whatever happens, the future has just become more complicated \u2014 now you have to ask yourself ‘Which HTML5?’<\/p><\/blockquote>\n

Even if it sounds good, it is actually really bad. \u00a0HTML5 is already complicated enough, and all major browsers support a different subset of it, and even those things which are supported do differ in the way of how. \u00a0Splitting the standard just complicated things further. \u00a0The fact that this is not exactly new<\/a>, doesn’t really matter. \u00a0Saying that it won’t be harmful<\/a>, is silly. \u00a0As is the whole point of a “living standard”. \u00a0Like a few people mentioned in Slashdot comments, “living standard” is an oxymoron. The whole point of standard is to provide a static point of reference. \u00a0Splitting is not a solution to the problem. \u00a0It’s quite the opposite. \u00a0Consider this xkcd comics<\/a> for illustration, which is nothing but the truth.<\/p>\n

\"\"<\/a><\/p>\n\n","protected":false},"excerpt":{"rendered":"\n

Just when web developers got a little bit of hope, Slashdot reports on the bad news. Until now the two standards bodies working on HTML5 (WHATWG\u00a0and\u00a0W3C\u00a0) have cooperated. An announcement by WHATWG makes it clear that this is no longer true.\u00a0WHATWG is going to work on a living standard for HTML\u00a0which will continue to evolve … Continue reading HTML5 splits into two standards<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":16546,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false,"_links_to":"","_links_to_target":""},"categories":[1,18,62,1334],"tags":[918,20,1190,1216,1330],"keyring_services":[],"class_list":["post-16545","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general","category-programming","category-technology","category-web-work","tag-announcements","tag-browsers","tag-html","tag-standards","tag-web-development"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t