<?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 lessons of CSS frameworks</title>
	<atom:link href="http://ajaxian.com/archives/the-lessons-of-css-frameworks/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/the-lessons-of-css-frameworks</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: jpiperkerr</title>
		<link>http://ajaxian.com/archives/the-lessons-of-css-frameworks/comment-page-1#comment-266824</link>
		<dc:creator>jpiperkerr</dc:creator>
		<pubDate>Thu, 21 Aug 2008 12:45:48 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4143#comment-266824</guid>
		<description>I don&#039;t see the performance issues being that great. If the framework is minified, compressed, and cached the added load over the wire is reasonable and isolated to the initial load. Combining this with optimized stylesheets for common landing pages for your site and delayed loading of site wide styles it is possible to hide potential usability performance issues behind a page that is completely rendered from the user&#039;s perspective. Also with a well thought out CSS framework it is possible to reduce the number of declarations in your site styles, and this can offset the added load over the wire added by a CSS framework.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see the performance issues being that great. If the framework is minified, compressed, and cached the added load over the wire is reasonable and isolated to the initial load. Combining this with optimized stylesheets for common landing pages for your site and delayed loading of site wide styles it is possible to hide potential usability performance issues behind a page that is completely rendered from the user&#8217;s perspective. Also with a well thought out CSS framework it is possible to reduce the number of declarations in your site styles, and this can offset the added load over the wire added by a CSS framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mancjew</title>
		<link>http://ajaxian.com/archives/the-lessons-of-css-frameworks/comment-page-1#comment-266815</link>
		<dc:creator>mancjew</dc:creator>
		<pubDate>Thu, 21 Aug 2008 00:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4143#comment-266815</guid>
		<description>I think these frameworks came out of lessons learnt from building a large site that has multiple column layouts in different section of the site.

These are probably quite useful for intranets where they can trade off some off the performance issues.</description>
		<content:encoded><![CDATA[<p>I think these frameworks came out of lessons learnt from building a large site that has multiple column layouts in different section of the site.</p>
<p>These are probably quite useful for intranets where they can trade off some off the performance issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LeoHorie</title>
		<link>http://ajaxian.com/archives/the-lessons-of-css-frameworks/comment-page-1#comment-266813</link>
		<dc:creator>LeoHorie</dc:creator>
		<pubDate>Wed, 20 Aug 2008 22:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4143#comment-266813</guid>
		<description>They&#039;re great for prototyping, but not so great for high traffic sites like the Google front page.</description>
		<content:encoded><![CDATA[<p>They&#8217;re great for prototyping, but not so great for high traffic sites like the Google front page.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

