sorted by: recent | see : popular

Content Tagged with WebKit + w3c

“Why something as poorly designed as the Web became The Next Big Thing, and what that means for the future.” Well designed but "fixed" systems were over taken by the evolvable but poorly designed Web. I'm wonderig if these same "evolving" principles apply to standard organizations? Put WebKit up against the standard orgs in charge of key WebKit components, and you see clearly that WebKit would fail misably if they stuck to the hapless efforts of the W3C, Ecma and ISO. Besides the fact that entrenched players such as Microsoft are sitting on those standards orgs in position to dumb down or put into terminal stall much needed innovations. For instance, WebKit deepneds on HTML5, CSS3, SVG, and JavaScript. All of which are stalled at various standards orgs. As a reaction to this org stall, the WebKit group pushes forward anyway relying instead on OSS Community style innovation and consensus model sharing.

I reformatted my response to marbux concerning HTML5 and web application lack of interoperability. The original article these comments were posted to is titled, <a href="http://mondaybynoon.com/2008/06/30/siding-with-html-over-xhtml-my-decision-to-switch