<?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 CSS-Layout Adoption Dilemma</title>
	<atom:link href="http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/</link>
	<description>A continuing account of my life...</description>
	<lastBuildDate>Wed, 21 Apr 2010 15:08:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Murray Todd Williams</title>
		<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/comment-page-1/#comment-14746</link>
		<dc:creator>Murray Todd Williams</dc:creator>
		<pubDate>Sun, 10 Aug 2008 20:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/#comment-14746</guid>
		<description>With all due respect, Steven, no, HTML source for websites that use CSS layout do not look like they used tables. You do &lt;i&gt;not&lt;/i&gt; see near-infinitely-nested TR and TD tags carving everything up. (You can see a dizzying array of DIV tags, but that&#039;s another matter.)</description>
		<content:encoded><![CDATA[<p>With all due respect, Steven, no, HTML source for websites that use CSS layout do not look like they used tables. You do <i>not</i> see near-infinitely-nested TR and TD tags carving everything up. (You can see a dizzying array of DIV tags, but that&#8217;s another matter.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Sanders</title>
		<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/comment-page-1/#comment-8017</link>
		<dc:creator>Steven Sanders</dc:creator>
		<pubDate>Fri, 04 Jan 2008 22:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/#comment-8017</guid>
		<description>When you elect to view the source of a website, you may not necessarily be viewing the code that was originally written.  Many website designers that use php or asp as their code of choice, may be using css.

The problem with viewing the source of a php or asp page is that alot of the code is executed server side and the page source on the client side is what is written by the server side execution.

I&#039;m not sure if I&#039;m really explaining this very well.  Just know, that when I code a website styled heavily with css, instead of using tables and such, if I were to view the public page source instead of the original code, it looks as though it was done using tables, etc.</description>
		<content:encoded><![CDATA[<p>When you elect to view the source of a website, you may not necessarily be viewing the code that was originally written.  Many website designers that use php or asp as their code of choice, may be using css.</p>
<p>The problem with viewing the source of a php or asp page is that alot of the code is executed server side and the page source on the client side is what is written by the server side execution.</p>
<p>I&#8217;m not sure if I&#8217;m really explaining this very well.  Just know, that when I code a website styled heavily with css, instead of using tables and such, if I were to view the public page source instead of the original code, it looks as though it was done using tables, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/comment-page-1/#comment-1141</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Wed, 30 Aug 2006 15:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/#comment-1141</guid>
		<description>Though I agree that evolution is a great thing for the web, I must state that depending on your development environment, you may or may not have the time to use css for developing large numbers of sites. The reason many developers are shying away from css is that it takes far longer to plan and implement css into a site.

I personally LOVE css and am experimenting with it all the time but have not found it to be practical for developing a site for clients at a break-neck pace. And believe me, many clients don&#039;t care HOW you do a site, they care about when.

I think that the web is actually going through a period of over-simplification with respect to design and layout. We were bombed in the late 90&#039;s through just last year when I noticed that sites became cleaner and more readable.
I believe that CSS is the vehicle that is driving this movement. The clean layouts, readable text and simple access to more information with a single click are examples of useability that have been widely ignored for the sake of &quot;pretty&quot; designs. 

So, I think that the underlying fact is that developers are more than likely diving in to the &quot;CSS in 10 Minutes&quot; books all over the world. But until these books move from casual (dare I say this?) bathroom reading to their office, we may have to wait for the trend to catch on.</description>
		<content:encoded><![CDATA[<p>Though I agree that evolution is a great thing for the web, I must state that depending on your development environment, you may or may not have the time to use css for developing large numbers of sites. The reason many developers are shying away from css is that it takes far longer to plan and implement css into a site.</p>
<p>I personally LOVE css and am experimenting with it all the time but have not found it to be practical for developing a site for clients at a break-neck pace. And believe me, many clients don&#8217;t care HOW you do a site, they care about when.</p>
<p>I think that the web is actually going through a period of over-simplification with respect to design and layout. We were bombed in the late 90&#8242;s through just last year when I noticed that sites became cleaner and more readable.<br />
I believe that CSS is the vehicle that is driving this movement. The clean layouts, readable text and simple access to more information with a single click are examples of useability that have been widely ignored for the sake of &#8220;pretty&#8221; designs. </p>
<p>So, I think that the underlying fact is that developers are more than likely diving in to the &#8220;CSS in 10 Minutes&#8221; books all over the world. But until these books move from casual (dare I say this?) bathroom reading to their office, we may have to wait for the trend to catch on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Murray Todd Williams</title>
		<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/comment-page-1/#comment-758</link>
		<dc:creator>Murray Todd Williams</dc:creator>
		<pubDate>Sun, 23 Jul 2006 16:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/#comment-758</guid>
		<description>LaTeX? Of course. I wrote my masters thesis in it. If you&#039;re in the mood to read something unintelligible with lots of math equations in it, go to the old Statistics articles on my &lt;a href=&quot;/writing/index.html#stats&quot; rel=&quot;nofollow&quot;&gt;writing page&lt;/a&gt; and read through a bit.

Actually, I also used LaTeX sometimes (back in those days when I remembered how to use it) to format my fiction writing because the finished layout &lt;em&gt;is&lt;/em&gt; quite nice and clean-looking.

Back to your main point: I agree with you completely. In many ways the whole HTML/CSS web evolution has been unfortunate and complicated. I guess that&#039;s the tradeoff we get for having an Open Specification and generally free Internet instead of the vision that companies like AOL and Prodigy and MSN and Compuserve originally had, where the interface would be completely proprietary and companies would pay a fair amount of money for their service (what we think of now as a website) to be available to customers.

No, the web was an accidental evolution where the original HTML encoding &lt;em&gt;wasn&#039;t meant&lt;/em&gt; to involve fancy layout, and instead it was intended to be the next version of &lt;a href=&quot;http://en.wikipedia.org/wiki/Gopher_protocol&quot; target=&quot;_blank&quot; ref=&quot;nofollow&quot; rel=&quot;nofollow&quot;&gt;Gopher&lt;/a&gt;. We&#039;ve weathered the days of proprietary HTML tags in the old Netscape/IE wars, the hyped-up and mostly failed Java Applet revolution, Microsoft&#039;s stupid VBScript...

It&#039;s an imperfect world. But separation of content (HTML) and layout (CSS) &lt;em&gt;is&lt;/em&gt; good form, leads you to better&#8212;and more easily maintained sites, helps web crawlers understand your content in a non-visual context, and even makes it easier for blind people to use tools to access the web. And I still say it&#039;s &quot;good for you&quot; in the same way that learning how to hold a watercolor brush or curling your fingers just right when playing the piano is good for you: if you want to excel at the medium, it&#039;s worth going through a bit of pain to learn to master it properly. (Translation: Eat Your Broccoli!)</description>
		<content:encoded><![CDATA[<p>LaTeX? Of course. I wrote my masters thesis in it. If you&#8217;re in the mood to read something unintelligible with lots of math equations in it, go to the old Statistics articles on my <a href="/writing/index.html#stats" rel="nofollow">writing page</a> and read through a bit.</p>
<p>Actually, I also used LaTeX sometimes (back in those days when I remembered how to use it) to format my fiction writing because the finished layout <em>is</em> quite nice and clean-looking.</p>
<p>Back to your main point: I agree with you completely. In many ways the whole HTML/CSS web evolution has been unfortunate and complicated. I guess that&#8217;s the tradeoff we get for having an Open Specification and generally free Internet instead of the vision that companies like AOL and Prodigy and MSN and Compuserve originally had, where the interface would be completely proprietary and companies would pay a fair amount of money for their service (what we think of now as a website) to be available to customers.</p>
<p>No, the web was an accidental evolution where the original HTML encoding <em>wasn&#8217;t meant</em> to involve fancy layout, and instead it was intended to be the next version of <a href="http://en.wikipedia.org/wiki/Gopher_protocol" target="_blank" ref="nofollow" rel="nofollow">Gopher</a>. We&#8217;ve weathered the days of proprietary HTML tags in the old Netscape/IE wars, the hyped-up and mostly failed Java Applet revolution, Microsoft&#8217;s stupid VBScript&#8230;</p>
<p>It&#8217;s an imperfect world. But separation of content (HTML) and layout (CSS) <em>is</em> good form, leads you to better&mdash;and more easily maintained sites, helps web crawlers understand your content in a non-visual context, and even makes it easier for blind people to use tools to access the web. And I still say it&#8217;s &#8220;good for you&#8221; in the same way that learning how to hold a watercolor brush or curling your fingers just right when playing the piano is good for you: if you want to excel at the medium, it&#8217;s worth going through a bit of pain to learn to master it properly. (Translation: Eat Your Broccoli!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/comment-page-1/#comment-755</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Sun, 23 Jul 2006 06:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.murraywilliams.com/2006/07/22/the-css-layout-adoption-dilemma/#comment-755</guid>
		<description>I think it perhaps says something about CSS its self that it&#039;s been around for a while now, yet is still not as widely adopted as one would think.  As you say, many of us prefer to design and tinker in a visual environment by moving things about and seeing how they look and feel.  This enables you to create on the fly as it were.  From my purely amateur perspective, with CSS it seems to me you have to create everything in a raw and ugly way then go back an add a lot of arcane codes after the fact to get it to look the way you want.  It just seems counter intuitive.  CSS standards may be for our own good, but working with them does seem to stifle the creativity at times.

Also man, WordStar dot codes? Dude, please tell me you&#039;re also an expert in LaTex, because that would just make you the geek king of layout and formatting.</description>
		<content:encoded><![CDATA[<p>I think it perhaps says something about CSS its self that it&#8217;s been around for a while now, yet is still not as widely adopted as one would think.  As you say, many of us prefer to design and tinker in a visual environment by moving things about and seeing how they look and feel.  This enables you to create on the fly as it were.  From my purely amateur perspective, with CSS it seems to me you have to create everything in a raw and ugly way then go back an add a lot of arcane codes after the fact to get it to look the way you want.  It just seems counter intuitive.  CSS standards may be for our own good, but working with them does seem to stifle the creativity at times.</p>
<p>Also man, WordStar dot codes? Dude, please tell me you&#8217;re also an expert in LaTex, because that would just make you the geek king of layout and formatting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
