<?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"
	>
<channel>
	<title>Comments on: 12 Ways to Learn - or Improve - Your CSS</title>
	<atom:link href="http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/</link>
	<description>Making Web 2.0 More Than a Catchprhase</description>
	<pubDate>Sat, 11 Oct 2008 09:41:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: ajm</title>
		<link>http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/#comment-20</link>
		<dc:creator>ajm</dc:creator>
		<pubDate>Sun, 01 Oct 2006 01:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/#comment-20</guid>
		<description>I totally agree that the cascade is a basic thing best left to a tutorial, and really comes natural to those of us that do heavy lifting in CSS. However, I've noticed that as more "back-end" developers start working or dabbling in "front-end" stuff, the cascade is one of the things they miss. 

Often, CSS is knocked as being "limited" or "bulky" because people write lines and lines of code since they assume CSS doesn't have any more capabilities than changing font colors or adding borders to different elements. Really good CSS developers use CSS just like really good Java developers use classes: they build stylesheets that take advantage of the cascade to build things like inheritence into their stylesheets. But, most developers just starting out (and I've worked with them in many different situations), really miss the point and power of the cascade (and one of the big powers of CSS), so I wrote my response for any of those "newbies" who might be looking for that "one thing" that would crank their levels up a notch.

You wrote a great article that deserved a lot more comment than what I wrote!</description>
		<content:encoded><![CDATA[<p>I totally agree that the cascade is a basic thing best left to a tutorial, and really comes natural to those of us that do heavy lifting in CSS. However, I&#8217;ve noticed that as more &#8220;back-end&#8221; developers start working or dabbling in &#8220;front-end&#8221; stuff, the cascade is one of the things they miss. </p>
<p>Often, CSS is knocked as being &#8220;limited&#8221; or &#8220;bulky&#8221; because people write lines and lines of code since they assume CSS doesn&#8217;t have any more capabilities than changing font colors or adding borders to different elements. Really good CSS developers use CSS just like really good Java developers use classes: they build stylesheets that take advantage of the cascade to build things like inheritence into their stylesheets. But, most developers just starting out (and I&#8217;ve worked with them in many different situations), really miss the point and power of the cascade (and one of the big powers of CSS), so I wrote my response for any of those &#8220;newbies&#8221; who might be looking for that &#8220;one thing&#8221; that would crank their levels up a notch.</p>
<p>You wrote a great article that deserved a lot more comment than what I wrote!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben</title>
		<link>http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/#comment-19</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Sat, 30 Sep 2006 20:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amodernfable.com/2006/09/27/12-ways-to-learn-or-improve-your-css/#comment-19</guid>
		<description>I should be packing up my things - between apartments - but instead I'm egosurfing.  You can tell that MY priorities are straight.

I just wanted to drop in and say thanks for the commentary.

One thoughts:

I left out the cascade because it's implied and the task of pointing to it is best suited to a tutorial rather than any kind of prose.

Beyond that, it's great to see someone riff on what I wrote!  (I whish more people had.)</description>
		<content:encoded><![CDATA[<p>I should be packing up my things - between apartments - but instead I&#8217;m egosurfing.  You can tell that MY priorities are straight.</p>
<p>I just wanted to drop in and say thanks for the commentary.</p>
<p>One thoughts:</p>
<p>I left out the cascade because it&#8217;s implied and the task of pointing to it is best suited to a tutorial rather than any kind of prose.</p>
<p>Beyond that, it&#8217;s great to see someone riff on what I wrote!  (I whish more people had.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
