<?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: Lighttd: Put your webserver on a diet</title>
	<atom:link href="http://hauntedshell.com/2008/10/13/lighttd-put-your-webserver-on-a-diet/feed/" rel="self" type="application/rss+xml" />
	<link>http://hauntedshell.com/2008/10/13/lighttd-put-your-webserver-on-a-diet/</link>
	<description>Just another Hauntedshell.com weblog</description>
	<lastBuildDate>Fri, 06 Apr 2012 12:06:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Kwame</title>
		<link>http://hauntedshell.com/2008/10/13/lighttd-put-your-webserver-on-a-diet/comment-page-1/#comment-28</link>
		<dc:creator>Kwame</dc:creator>
		<pubDate>Wed, 15 Oct 2008 21:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauntedshell.com/?p=88#comment-28</guid>
		<description>True, true. For a production box, I&#039;d probably stick to Apache. Right now though, I need something lightweight for development.</description>
		<content:encoded><![CDATA[<p>True, true. For a production box, I&#8217;d probably stick to Apache. Right now though, I need something lightweight for development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://hauntedshell.com/2008/10/13/lighttd-put-your-webserver-on-a-diet/comment-page-1/#comment-27</link>
		<dc:creator>George</dc:creator>
		<pubDate>Wed, 15 Oct 2008 03:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.hauntedshell.com/?p=88#comment-27</guid>
		<description>All fair and good when you&#039;re running your own stuff for your own (or limited public) use. But when you&#039;re doing shared hosting stuff, such &quot;smart&quot; solutions could at best be offered as an extra option for the few nerds onboard, while offering the &quot;standard&quot; solutions for everyone else.

WordPress (and most other CMSes) will tell you that you&#039;ll be ok with any webserver software (even IIS). And sure, you&#039;ll be ok... till you&#039;re not. Often all it needs is some basic conf changes, but don&#039;t expect Aunt Becky to figure that out.

That&#039;s why successful (web)apps, which start lean, mean and clean, often become bloated in the long-run, as they strive to accommodate that cool &#039;lil  feature from everyone and their cats.

Here I&#039;m thinking WordPress, now almost hitting 2MB, from about 300kb just about 2 years ago when I came to love it.

It&#039;s a big &quot;Success Trap&quot; out there.</description>
		<content:encoded><![CDATA[<p>All fair and good when you&#8217;re running your own stuff for your own (or limited public) use. But when you&#8217;re doing shared hosting stuff, such &#8220;smart&#8221; solutions could at best be offered as an extra option for the few nerds onboard, while offering the &#8220;standard&#8221; solutions for everyone else.</p>
<p>WordPress (and most other CMSes) will tell you that you&#8217;ll be ok with any webserver software (even IIS). And sure, you&#8217;ll be ok&#8230; till you&#8217;re not. Often all it needs is some basic conf changes, but don&#8217;t expect Aunt Becky to figure that out.</p>
<p>That&#8217;s why successful (web)apps, which start lean, mean and clean, often become bloated in the long-run, as they strive to accommodate that cool &#8216;lil  feature from everyone and their cats.</p>
<p>Here I&#8217;m thinking WordPress, now almost hitting 2MB, from about 300kb just about 2 years ago when I came to love it.</p>
<p>It&#8217;s a big &#8220;Success Trap&#8221; out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

