<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: &#8220;Everything Floats Down Here&#8221;</title>
	<atom:link href="http://endurefort.wordpress.com/2009/02/02/everything-floats-down-here/feed/" rel="self" type="application/rss+xml" />
	<link>http://endurefort.wordpress.com/2009/02/02/everything-floats-down-here/</link>
	<description>People are strange, when you're a stranger</description>
	<lastBuildDate>Sun, 18 Oct 2009 12:13:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://endurefort.wordpress.com/2009/02/02/everything-floats-down-here/#comment-101</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 03 Feb 2009 16:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://endurefort.wordpress.com/?p=39#comment-101</guid>
		<description>I really like how you posted some arguments to the other side of the story. I went through the same deal as you did at work. Lucky for me I was in my intro to scripting class about the same time I started my internship. I was the only one who stuck to table-less layouts and everyone always joked around about how much longer it took me to slice down a site and build it in html / css. The learning curve on table design is much shorter but in the long run CSS driven layout is so much stronger. Now, Shane and I have gotten the rest of the office to ditch tables (for the most part) and stick with the right way of doing things.</description>
		<content:encoded><![CDATA[<p>I really like how you posted some arguments to the other side of the story. I went through the same deal as you did at work. Lucky for me I was in my intro to scripting class about the same time I started my internship. I was the only one who stuck to table-less layouts and everyone always joked around about how much longer it took me to slice down a site and build it in html / css. The learning curve on table design is much shorter but in the long run CSS driven layout is so much stronger. Now, Shane and I have gotten the rest of the office to ditch tables (for the most part) and stick with the right way of doing things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy</title>
		<link>http://endurefort.wordpress.com/2009/02/02/everything-floats-down-here/#comment-100</link>
		<dc:creator>Jimmy</dc:creator>
		<pubDate>Tue, 03 Feb 2009 16:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://endurefort.wordpress.com/?p=39#comment-100</guid>
		<description>Stephen King&#039;s: It? :) Which would fit with the &quot;evilness&quot; of youth (even in design) that could be recognized later in life.. I know I keep opening old projects and get a shiver or two from where I used to be. Anyway, I didn&#039;t know about the display: table option, I can&#039;t see why there would be a problem with using it since display: table is purely a rendering option and not part of semantic markup... it seems like it&#039;d be no different than choosing a red background or a yellow border. Of course, if the majority of your users or customers use IE7, then you&#039;ll have to have some sort of contingency layout for them, since it&#039;s only supported in IE8+</description>
		<content:encoded><![CDATA[<p>Stephen King&#8217;s: It? <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Which would fit with the &#8220;evilness&#8221; of youth (even in design) that could be recognized later in life.. I know I keep opening old projects and get a shiver or two from where I used to be. Anyway, I didn&#8217;t know about the display: table option, I can&#8217;t see why there would be a problem with using it since display: table is purely a rendering option and not part of semantic markup&#8230; it seems like it&#8217;d be no different than choosing a red background or a yellow border. Of course, if the majority of your users or customers use IE7, then you&#8217;ll have to have some sort of contingency layout for them, since it&#8217;s only supported in IE8+</p>
]]></content:encoded>
	</item>
</channel>
</rss>
