<?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: CSS3 = Fail</title>
	<atom:link href="http://byme.se/jquery/css3-fail.html/feed" rel="self" type="application/rss+xml" />
	<link>http://byme.se/jquery/css3-fail.html</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 23:38:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Chris Caldwell</title>
		<link>http://byme.se/jquery/css3-fail.html#comment-4996</link>
		<dc:creator>Chris Caldwell</dc:creator>
		<pubDate>Mon, 30 Jan 2012 16:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://byme.se/?p=3680#comment-4996</guid>
		<description>If this article was written when browser support for javascript was just coming into practice you&#039;d have written something to the effect of &quot;don&#039;t use javascript because it&#039;s not the supported by the lowest common denominator browser&quot;.

Honestly, if we keep pandering to IE as the lowest common denominator – we as a design/dev community are saying go ahead IE, dictate the course of the web to us. However; if we build for the future of the web we want, by providing better experiences in browsers that are support modern standards and techniques, we can help drive technology forward.

Browser update models and release structures have changed for the better ensuring faster adoption of new standards and the IT departments and out moved browser manufacturers that aren&#039;t paying attention will be left behind. 

And if the content is also designed to work on these outdated browser platforms then there is absolutely nothing wrong with using new techniques and tools that modern browsers support.

Your jQuery example only supports the argument for CSS3 being used and implemented. Does anyone remember the day when your web pages had to work without javascript. This argument, in my opinion holds no water. CSS is a presentation layer and should be used for visual styles as well as layout.

I agree that &#039;progressive enhancement&#039; is a viable approach but favour &#039;graceful degridation&#039; as it&#039;s focus is on pushing technology forward first.

Progressive enhancement VS Graceful Degradation is the real debate at the heart of this article.

Progressive Enhancement == Build for the world as it appears at this exact moment and extend it to more mature browsers that are driving the technology.

Graceful Degradation == Build for the world we want and ensure that people using reasonably older technology can still get to the content.

Both will achieve a similar result, but the intent and purpose are different. Do you want to push the technology forward or slow it down and try to keep it where it&#039;s at?</description>
		<content:encoded><![CDATA[<p>If this article was written when browser support for javascript was just coming into practice you&#8217;d have written something to the effect of &#8220;don&#8217;t use javascript because it&#8217;s not the supported by the lowest common denominator browser&#8221;.</p>
<p>Honestly, if we keep pandering to IE as the lowest common denominator – we as a design/dev community are saying go ahead IE, dictate the course of the web to us. However; if we build for the future of the web we want, by providing better experiences in browsers that are support modern standards and techniques, we can help drive technology forward.</p>
<p>Browser update models and release structures have changed for the better ensuring faster adoption of new standards and the IT departments and out moved browser manufacturers that aren&#8217;t paying attention will be left behind. </p>
<p>And if the content is also designed to work on these outdated browser platforms then there is absolutely nothing wrong with using new techniques and tools that modern browsers support.</p>
<p>Your jQuery example only supports the argument for CSS3 being used and implemented. Does anyone remember the day when your web pages had to work without javascript. This argument, in my opinion holds no water. CSS is a presentation layer and should be used for visual styles as well as layout.</p>
<p>I agree that &#8216;progressive enhancement&#8217; is a viable approach but favour &#8216;graceful degridation&#8217; as it&#8217;s focus is on pushing technology forward first.</p>
<p>Progressive enhancement VS Graceful Degradation is the real debate at the heart of this article.</p>
<p>Progressive Enhancement == Build for the world as it appears at this exact moment and extend it to more mature browsers that are driving the technology.</p>
<p>Graceful Degradation == Build for the world we want and ensure that people using reasonably older technology can still get to the content.</p>
<p>Both will achieve a similar result, but the intent and purpose are different. Do you want to push the technology forward or slow it down and try to keep it where it&#8217;s at?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommie Hansen</title>
		<link>http://byme.se/jquery/css3-fail.html#comment-2912</link>
		<dc:creator>Tommie Hansen</dc:creator>
		<pubDate>Wed, 11 May 2011 19:15:45 +0000</pubDate>
		<guid isPermaLink="false">http://byme.se/?p=3680#comment-2912</guid>
		<description>@&lt;a href=&quot;#comment-2888&quot; rel=&quot;nofollow&quot;&gt;A2daK&lt;/a&gt;: I agree that it CSS3 a step forward.... for CSS.

I&#039;m not worried. The problem is more that we tend to see a trend where people show off their &quot;glorious&quot; stuff with the latest &quot;cool&quot; thing that doesn&#039;t work for 70% of users.

It is a little like when people that design only on MACs show of their cool stuff with the problem being that it look like crap on a PC due to difference in anti aliasing. It&#039;s just so blatantly lame on unprofessional.

The reason i wrote the post is due to the fact that i&#039;m so sick of posts showing the latest and greatest in CSS3, but that never seem to consider those other 70% that lives in the real world (&quot;real world&quot; as in The Matrix -- yes!).

For now CSS3 seems to be more about effects and less about *REAL* layout. I really miss stuff like cross browser columns (for text content) etc that really *WORK* (not a javascript hack that &quot;sort of work&quot;).</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-2888" rel="nofollow">A2daK</a>: I agree that it CSS3 a step forward&#8230;. for CSS.</p>
<p>I&#8217;m not worried. The problem is more that we tend to see a trend where people show off their &#8220;glorious&#8221; stuff with the latest &#8220;cool&#8221; thing that doesn&#8217;t work for 70% of users.</p>
<p>It is a little like when people that design only on MACs show of their cool stuff with the problem being that it look like crap on a PC due to difference in anti aliasing. It&#8217;s just so blatantly lame on unprofessional.</p>
<p>The reason i wrote the post is due to the fact that i&#8217;m so sick of posts showing the latest and greatest in CSS3, but that never seem to consider those other 70% that lives in the real world (&#8220;real world&#8221; as in The Matrix &#8212; yes!).</p>
<p>For now CSS3 seems to be more about effects and less about *REAL* layout. I really miss stuff like cross browser columns (for text content) etc that really *WORK* (not a javascript hack that &#8220;sort of work&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A2daK</title>
		<link>http://byme.se/jquery/css3-fail.html#comment-2888</link>
		<dc:creator>A2daK</dc:creator>
		<pubDate>Tue, 10 May 2011 09:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://byme.se/?p=3680#comment-2888</guid>
		<description>CSS3 is a great step forward in my opinion. You can easily code up fallbacks if you are worried about css3 styling degrading properly on old browsers. Im fairly sure that most modern browsers (Chrome, FF4 &amp; Safari) support the majority of CSS3 properties. 

Users who have old browsers such as IE6/IE7 or just IE in general deserve to suffer a little. They end up suffering ascetically. 

Some of the webkit only transform CSS3 is a bit wild but never useless...</description>
		<content:encoded><![CDATA[<p>CSS3 is a great step forward in my opinion. You can easily code up fallbacks if you are worried about css3 styling degrading properly on old browsers. Im fairly sure that most modern browsers (Chrome, FF4 &amp; Safari) support the majority of CSS3 properties. </p>
<p>Users who have old browsers such as IE6/IE7 or just IE in general deserve to suffer a little. They end up suffering ascetically. </p>
<p>Some of the webkit only transform CSS3 is a bit wild but never useless&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn Nelson</title>
		<link>http://byme.se/jquery/css3-fail.html#comment-864</link>
		<dc:creator>Glenn Nelson</dc:creator>
		<pubDate>Tue, 22 Jun 2010 13:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://byme.se/?p=3680#comment-864</guid>
		<description>I&#039;m honestly glad that someone out there understands that just because you can make some little sh*tty site that looks great in Chrome but sucks everywhere else doesn&#039;t cut it. Making a site that looks the same and functions the same in all browsers is what marks a true web developer. This site is definitely one I&#039;m going to follow.</description>
		<content:encoded><![CDATA[<p>I&#8217;m honestly glad that someone out there understands that just because you can make some little sh*tty site that looks great in Chrome but sucks everywhere else doesn&#8217;t cut it. Making a site that looks the same and functions the same in all browsers is what marks a true web developer. This site is definitely one I&#8217;m going to follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

