<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The great divide</title>
	<atom:link href="http://kilianvalkhof.com/2008/web/the-great-divide/feed/" rel="self" type="application/rss+xml" />
	<link>http://kilianvalkhof.com/2008/web/the-great-divide/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 15:17:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: NatalieMac</title>
		<link>http://kilianvalkhof.com/2008/web/the-great-divide/comment-page-1/#comment-7356</link>
		<dc:creator>NatalieMac</dc:creator>
		<pubDate>Sat, 12 Jul 2008 00:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=74#comment-7356</guid>
		<description>Once IE8 takes hold, browsers compliant with the current standards will comprise nearly 100% of the market. The specs for CSS3, HTML5, and XHTML2 aren&#039;t finished yet, and while browser manufacturers can start to experiment with implementing these new standards, it&#039;s unreasonable to expect them to invest a lot of time and effort into implementing standards that aren&#039;t finished yet and might change.

As long as a browser provides me with standards support, I don&#039;t care if they add extra features on top of that - especially if they are enhancements that degrade gracefully. If I don&#039;t like them, I won&#039;t use them, and if I like reflections or text shadows, then they&#039;ll be enhancements for the browsers that support them and the people using other browsers won&#039;t miss a thing.

So many of the standards we have now began as proprietary features in one browser or another - the browsers competing against one another has historically been the biggest driver of innovation in web technology. If browser manufacturers weren&#039;t innovating and adding new features, we&#039;d have to depend on the standards bodies to innovate - and we see how slowly that happens. The CSS 2.1 spec is &lt;em&gt;ten years&lt;/em&gt; old.

So I say, as long as you&#039;re implementing standards, go ahead and innovate. If you produce something useful that enhances the web, the other browsers will pick it up, the standards bodies will pick it up and it will eventually become a standard.</description>
		<content:encoded><![CDATA[<p>Once IE8 takes hold, browsers compliant with the current standards will comprise nearly 100% of the market. The specs for CSS3, HTML5, and XHTML2 aren&#8217;t finished yet, and while browser manufacturers can start to experiment with implementing these new standards, it&#8217;s unreasonable to expect them to invest a lot of time and effort into implementing standards that aren&#8217;t finished yet and might change.</p>
<p>As long as a browser provides me with standards support, I don&#8217;t care if they add extra features on top of that &#8211; especially if they are enhancements that degrade gracefully. If I don&#8217;t like them, I won&#8217;t use them, and if I like reflections or text shadows, then they&#8217;ll be enhancements for the browsers that support them and the people using other browsers won&#8217;t miss a thing.</p>
<p>So many of the standards we have now began as proprietary features in one browser or another &#8211; the browsers competing against one another has historically been the biggest driver of innovation in web technology. If browser manufacturers weren&#8217;t innovating and adding new features, we&#8217;d have to depend on the standards bodies to innovate &#8211; and we see how slowly that happens. The CSS 2.1 spec is <em>ten years</em> old.</p>
<p>So I say, as long as you&#8217;re implementing standards, go ahead and innovate. If you produce something useful that enhances the web, the other browsers will pick it up, the standards bodies will pick it up and it will eventually become a standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Short</title>
		<link>http://kilianvalkhof.com/2008/web/the-great-divide/comment-page-1/#comment-6996</link>
		<dc:creator>Anthony Short</dc:creator>
		<pubDate>Fri, 04 Jul 2008 03:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=74#comment-6996</guid>
		<description>The differences between the browsers are slowly closing. The best solution would be for each of the browsers to adopt a single rendering engine, and apply extensions to it so they will all render exactly the same under the CSS3 spec. If browsers such as Safari want to expand and test new waters, they can implement their drop shadows, variables etc. But are optional extras. 

These extra properties won&#039;t make much of a difference. It&#039;s selectors that need to be consistent. 

However, they&#039;re all too stubborn to even consider that option. They&#039;re more concerned with business rather than how far we can push the boundaries of web development for the future.</description>
		<content:encoded><![CDATA[<p>The differences between the browsers are slowly closing. The best solution would be for each of the browsers to adopt a single rendering engine, and apply extensions to it so they will all render exactly the same under the CSS3 spec. If browsers such as Safari want to expand and test new waters, they can implement their drop shadows, variables etc. But are optional extras. </p>
<p>These extra properties won&#8217;t make much of a difference. It&#8217;s selectors that need to be consistent. </p>
<p>However, they&#8217;re all too stubborn to even consider that option. They&#8217;re more concerned with business rather than how far we can push the boundaries of web development for the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buzu</title>
		<link>http://kilianvalkhof.com/2008/web/the-great-divide/comment-page-1/#comment-6818</link>
		<dc:creator>Buzu</dc:creator>
		<pubDate>Mon, 30 Jun 2008 23:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=74#comment-6818</guid>
		<description>Oh no! that sounds bad, but we all know that. The true is that simple web developers can make the difference, but some just don&#039;t want to do it. It&#039;s easy, just ask your self Why in the world do I want a reflection in my pictures? When you realize that you don&#039;t want or at least you don&#039;t need that reflection, you&#039;ll be able to not to use it. Then if you don&#039;t use it, why would they want to continue working on that? It&#039;s just easy, the best way to force them to develop standard browsers is keeping your websites standard and showing that you don&#039;t want to use any cool effect unless it it standard. It&#039;s hard to believe, but it&#039;s true. Oh, by the way,if we have an XHTML why do we want an HTML 5?</description>
		<content:encoded><![CDATA[<p>Oh no! that sounds bad, but we all know that. The true is that simple web developers can make the difference, but some just don&#8217;t want to do it. It&#8217;s easy, just ask your self Why in the world do I want a reflection in my pictures? When you realize that you don&#8217;t want or at least you don&#8217;t need that reflection, you&#8217;ll be able to not to use it. Then if you don&#8217;t use it, why would they want to continue working on that? It&#8217;s just easy, the best way to force them to develop standard browsers is keeping your websites standard and showing that you don&#8217;t want to use any cool effect unless it it standard. It&#8217;s hard to believe, but it&#8217;s true. Oh, by the way,if we have an XHTML why do we want an HTML 5?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Gasston</title>
		<link>http://kilianvalkhof.com/2008/web/the-great-divide/comment-page-1/#comment-6816</link>
		<dc:creator>Peter Gasston</dc:creator>
		<pubDate>Mon, 30 Jun 2008 21:40:59 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=74#comment-6816</guid>
		<description>I don&#039;t agree. When IE8 launches we will, for the first time, have four major browsers (or browser engines) with a solid baseline implementation of CSS2.1. On top of that, we&#039;ll have a load of experimental features implemented in three of those four which will help immensely the development of CSS3 &amp; HTML5 - and, they should all degrade elegantly.

One thing that&#039;s much better now than in the original &#039;browser war&#039; is that many of these new features - animations, variables, etc - are documented as they are released. I was critical of Webkit&#039;s decision to implement so many new features (and really, they are to act as a replacement for Flash on the iPhone more than anything else, IMHO), but at least they&#039;ve written released technical specs for everything they&#039;ve implemented.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree. When IE8 launches we will, for the first time, have four major browsers (or browser engines) with a solid baseline implementation of CSS2.1. On top of that, we&#8217;ll have a load of experimental features implemented in three of those four which will help immensely the development of CSS3 &amp; HTML5 &#8211; and, they should all degrade elegantly.</p>
<p>One thing that&#8217;s much better now than in the original &#8216;browser war&#8217; is that many of these new features &#8211; animations, variables, etc &#8211; are documented as they are released. I was critical of Webkit&#8217;s decision to implement so many new features (and really, they are to act as a replacement for Flash on the iPhone more than anything else, IMHO), but at least they&#8217;ve written released technical specs for everything they&#8217;ve implemented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Clark</title>
		<link>http://kilianvalkhof.com/2008/web/the-great-divide/comment-page-1/#comment-6803</link>
		<dc:creator>Adam Clark</dc:creator>
		<pubDate>Mon, 30 Jun 2008 13:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://kilianvalkhof.com/?p=74#comment-6803</guid>
		<description>Make you wonder why, as web designers, we bother some times. We work our typing fingers to the bone with the best of intentions to create something standards compliant and beautiful only to find that isn&#039;t as fully cross browser as you&#039;d been lead to believe.

The little hand says it&#039;s time to &lt;strong&gt;rebel&lt;/strong&gt;...</description>
		<content:encoded><![CDATA[<p>Make you wonder why, as web designers, we bother some times. We work our typing fingers to the bone with the best of intentions to create something standards compliant and beautiful only to find that isn&#8217;t as fully cross browser as you&#8217;d been lead to believe.</p>
<p>The little hand says it&#8217;s time to <strong>rebel</strong>&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

