<?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: CSS doesn’t suck, you’re just doing it wrong.</title>
	<atom:link href="http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/</link>
	<description>A Term of Endearment</description>
	<lastBuildDate>Thu, 20 Oct 2011 16:37:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nicole Sullivan</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-14235</link>
		<dc:creator>Nicole Sullivan</dc:creator>
		<pubDate>Sat, 03 Jul 2010 23:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-14235</guid>
		<description>@Rory I&#039;m sorry you took offense. Keep in mind that this post (as I stated in the first couple sentences) was a reply to a rant on Ajaxian. I expressed my frustration that so much attention is given to these perennial &quot;css sucks&quot; articles. I rarely rant, so bear with me. ;)</description>
		<content:encoded><![CDATA[<p>@Rory I&#8217;m sorry you took offense. Keep in mind that this post (as I stated in the first couple sentences) was a reply to a rant on Ajaxian. I expressed my frustration that so much attention is given to these perennial &#8220;css sucks&#8221; articles. I rarely rant, so bear with me. <img src='http://www.stubbornella.org/content/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rory</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-14228</link>
		<dc:creator>Rory</dc:creator>
		<pubDate>Sat, 03 Jul 2010 16:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-14228</guid>
		<description>I really don’t like the second person in this rant. It felt like you were insulting me and attacking me the whole way through, even though I personally am quite comfortable with CSS, accessibility, languages that don’t compile, etc. Even people who know CSS, or at least have already &quot;admitted their discomfort with the problem space”, might read this article just to affirm that they are on the right track – getting rid of the second person would make sure that these people don’t have to be slandered.</description>
		<content:encoded><![CDATA[<p>I really don’t like the second person in this rant. It felt like you were insulting me and attacking me the whole way through, even though I personally am quite comfortable with CSS, accessibility, languages that don’t compile, etc. Even people who know CSS, or at least have already &#8220;admitted their discomfort with the problem space”, might read this article just to affirm that they are on the right track – getting rid of the second person would make sure that these people don’t have to be slandered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garann</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13321</link>
		<dc:creator>Garann</dc:creator>
		<pubDate>Tue, 16 Jun 2009 19:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13321</guid>
		<description>Sorry for commenting on such an old post, but I stumbled on this after reading your OOCSS stuff (which is awesome) and just wanted to say thanks for putting it so plainly. I&#039;ve had frustrations with people hating on CSS many, many times, and have never been able to be this articulate about why they&#039;re being unfair. Nice work!</description>
		<content:encoded><![CDATA[<p>Sorry for commenting on such an old post, but I stumbled on this after reading your OOCSS stuff (which is awesome) and just wanted to say thanks for putting it so plainly. I&#8217;ve had frustrations with people hating on CSS many, many times, and have never been able to be this articulate about why they&#8217;re being unfair. Nice work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13218</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Fri, 24 Apr 2009 04:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13218</guid>
		<description>While I&#039;m sure with a lot of practice and knowledge you can get good at CSS and make it &quot;predictable&quot;, I&#039;d say that that is exactly the problem.  I can accept that complex problems can have complex solutions that require a deeper understanding of what you&#039;re doing but learning CSS seems to mean learning its quirks and workarounds rather than learning its power.  In my experience, rarely has the intuitive solution lead to the proper output in CSS.  I&#039;d rather have something more complex to program that was at least predictable and intuitive.

Many people are quick to blame IE for every problem.  I hate IE with a passion but I&#039;d say that the standards themselves are to blame for all of the bugs and incompatibilities.  IE may have made the biggest hash of it (by far) but every browser got it wrong, and that to me indicates that there is a problem with the specification itself.</description>
		<content:encoded><![CDATA[<p>While I&#8217;m sure with a lot of practice and knowledge you can get good at CSS and make it &#8220;predictable&#8221;, I&#8217;d say that that is exactly the problem.  I can accept that complex problems can have complex solutions that require a deeper understanding of what you&#8217;re doing but learning CSS seems to mean learning its quirks and workarounds rather than learning its power.  In my experience, rarely has the intuitive solution lead to the proper output in CSS.  I&#8217;d rather have something more complex to program that was at least predictable and intuitive.</p>
<p>Many people are quick to blame IE for every problem.  I hate IE with a passion but I&#8217;d say that the standards themselves are to blame for all of the bugs and incompatibilities.  IE may have made the biggest hash of it (by far) but every browser got it wrong, and that to me indicates that there is a problem with the specification itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13203</link>
		<dc:creator>john</dc:creator>
		<pubDate>Sat, 18 Apr 2009 15:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13203</guid>
		<description>No, CSS sucks.  it&#039;s a kludge to allow for multiple vendors to completely ignore the fact that a standard exists to prevent the need to make a kludge like CSS to work across multiple products.  While CSS does an admirable job at its task, the task itself is the major problem.  I would submit that CSS can NEVER work well, as its a solution to the wrong side of the problem of incompatible browsers and standards</description>
		<content:encoded><![CDATA[<p>No, CSS sucks.  it&#8217;s a kludge to allow for multiple vendors to completely ignore the fact that a standard exists to prevent the need to make a kludge like CSS to work across multiple products.  While CSS does an admirable job at its task, the task itself is the major problem.  I would submit that CSS can NEVER work well, as its a solution to the wrong side of the problem of incompatible browsers and standards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13202</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 17 Apr 2009 21:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13202</guid>
		<description>When I read some articles, I almost feel like the people writing are completely separated from the &quot;web&quot; when they throw around titles involving the word &quot;engineer.&quot;  Sometimes people get way too conceptual.  CSS was, is, and always will be easy for anyone who considers themselves to be even a decent web designer/developer/front-end &quot;engineer.&quot;  If it&#039;s not, don&#039;t use the title :D</description>
		<content:encoded><![CDATA[<p>When I read some articles, I almost feel like the people writing are completely separated from the &#8220;web&#8221; when they throw around titles involving the word &#8220;engineer.&#8221;  Sometimes people get way too conceptual.  CSS was, is, and always will be easy for anyone who considers themselves to be even a decent web designer/developer/front-end &#8220;engineer.&#8221;  If it&#8217;s not, don&#8217;t use the title <img src='http://www.stubbornella.org/content/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13201</link>
		<dc:creator>Nicole</dc:creator>
		<pubDate>Fri, 17 Apr 2009 19:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13201</guid>
		<description>@Jim You are right, it is still pretty fragile.  I&#039;d recommend watching my video from Web Directions North about Object Oriented CSS. Do that first, then check out the code on the OOCSS open source project on github.  You&#039;ll notice that grids + templates are less than 1K. modules are around 2K.  The OO approach is why it stays so light, and yet it allows a lot of flexibility. The goal is that all of the heavy lifting is done in the structure objects, which are then extended by extremely predictable skin objects.

&lt;embed src=http://d.yimg.com/cosmos.bcst.yahoo.com/up/fop/embedflv/swf/fop.swf?shareEnable=1&amp;id=12627860&amp;autoStart=0&amp;infoEnable=0&amp;shareEnable=0&amp;prepanelEnable=1&amp;carouselEnable=0&amp;postpanelEnable=1 width=400 height=300 type=application/x-shockwave-flash&gt;&lt;/embed&gt;
There is an &lt;a href=&quot;http://developer.yahoo.net/blogs/theater/archives/2009/03/website_and_webapp_performance.html&quot; rel=&quot;nofollow&quot;&gt;HD-ish version of the video available&lt;/a&gt; for download from the YDN site. 

The example code:
http://wiki.github.com/stubbornella/oocss

Keep in mind that OOCSS isn&#039;t a framework, this is just an example.  OOCSS is more like another language, anyone can write it, it just requires us to think in an object based way, separate structure objects from skins, and separate containers and content.</description>
		<content:encoded><![CDATA[<p>@Jim You are right, it is still pretty fragile.  I&#8217;d recommend watching my video from Web Directions North about Object Oriented CSS. Do that first, then check out the code on the OOCSS open source project on github.  You&#8217;ll notice that grids + templates are less than 1K. modules are around 2K.  The OO approach is why it stays so light, and yet it allows a lot of flexibility. The goal is that all of the heavy lifting is done in the structure objects, which are then extended by extremely predictable skin objects.</p>
<p><embed src=http://d.yimg.com/cosmos.bcst.yahoo.com/up/fop/embedflv/swf/fop.swf?shareEnable=1&#038;id=12627860&#038;autoStart=0&#038;infoEnable=0&#038;shareEnable=0&#038;prepanelEnable=1&#038;carouselEnable=0&#038;postpanelEnable=1 width=400 height=300 type=application/x-shockwave-flash></embed><br />
There is an <a href="http://developer.yahoo.net/blogs/theater/archives/2009/03/website_and_webapp_performance.html" rel="nofollow">HD-ish version of the video available</a> for download from the YDN site. </p>
<p>The example code:<br />
<a href="http://wiki.github.com/stubbornella/oocss" rel="nofollow">http://wiki.github.com/stubbornella/oocss</a></p>
<p>Keep in mind that OOCSS isn&#8217;t a framework, this is just an example.  OOCSS is more like another language, anyone can write it, it just requires us to think in an object based way, separate structure objects from skins, and separate containers and content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13200</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 17 Apr 2009 19:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13200</guid>
		<description>... but it still seems pretty fragile.</description>
		<content:encoded><![CDATA[<p>&#8230; but it still seems pretty fragile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13199</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 17 Apr 2009 19:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13199</guid>
		<description>OK so CSS doesn&#039;t suck and it is different (ie not just another programming language). So how do you make it &quot;... predictable, scalable, modular and even object oriented.&quot;?? I have made attempts at getting there but it still seems pretty.</description>
		<content:encoded><![CDATA[<p>OK so CSS doesn&#8217;t suck and it is different (ie not just another programming language). So how do you make it &#8220;&#8230; predictable, scalable, modular and even object oriented.&#8221;?? I have made attempts at getting there but it still seems pretty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: studdugie</title>
		<link>http://www.stubbornella.org/content/2009/02/12/css-doesn%e2%80%99t-suck-you%e2%80%99re-just-doing-it-wrong/comment-page-1/#comment-13070</link>
		<dc:creator>studdugie</dc:creator>
		<pubDate>Wed, 11 Mar 2009 11:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.stubbornella.org/content/?p=226#comment-13070</guid>
		<description>@Nicole: Thanx for the link. Let the healing begin!</description>
		<content:encoded><![CDATA[<p>@Nicole: Thanx for the link. Let the healing begin!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: www.stubbornella.org @ 2012-02-07 06:28:07 -->
