<?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: Will Code For Food</title>
	<atom:link href="http://www.foodpr0n.com/2009/05/03/will-code-for-food/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.foodpr0n.com/2009/05/03/will-code-for-food/</link>
	<description>Fewer photos. Less adjectives. Food is love.</description>
	<lastBuildDate>Fri, 17 May 2013 16:57:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stefanie</title>
		<link>http://www.foodpr0n.com/2009/05/03/will-code-for-food/comment-page-1/#comment-59</link>
		<dc:creator>Stefanie</dc:creator>
		<pubDate>Wed, 06 May 2009 20:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.foodpr0n.com/?p=414#comment-59</guid>
		<description><![CDATA[Totally agree with you.
I especially HATE those Flash intros. those never work on smartphones either.  so if I needed their address in a hurry, I just end up getting frustrated.

I&#039;m with you.]]></description>
		<content:encoded><![CDATA[<p>Totally agree with you.<br />
I especially HATE those Flash intros. those never work on smartphones either.  so if I needed their address in a hurry, I just end up getting frustrated.</p>
<p>I&#8217;m with you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Endy</title>
		<link>http://www.foodpr0n.com/2009/05/03/will-code-for-food/comment-page-1/#comment-53</link>
		<dc:creator>Endy</dc:creator>
		<pubDate>Wed, 06 May 2009 01:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.foodpr0n.com/?p=414#comment-53</guid>
		<description><![CDATA[Rick, 

I think a big part of the problem is that restaurants don&#039;t _care_ about having a current -- or any -- website.  (They may be justified -- I suspect people like you, me, and Jen are in the minority of restaurantgoers.)  And so firms that sell cookie-cutter website designs have swooped in knowing there&#039;s easy money to be made; restaurants are more than happy to outsource this sort of thing the same way they outsource their garbage disposal or linen.

it&#039;s all the more sad because, as Jen said, it would be cheaper and so much more effective to have a 1-page site with contact info, hours, and directions -- no upkeep necessary and dead easy to develop with NO FLASH.  A win for everyone.

it seems all hope is NOT lost though as I&#039;m noticing quite a few local restauranteurs setting up (and updating!) Twitter feeds.  Certainly Twitter is a big fad these days, but increased technology-restaurant &quot;fusion&quot; can only help matters.]]></description>
		<content:encoded><![CDATA[<p>Rick, </p>
<p>I think a big part of the problem is that restaurants don&#8217;t _care_ about having a current &#8212; or any &#8212; website.  (They may be justified &#8212; I suspect people like you, me, and Jen are in the minority of restaurantgoers.)  And so firms that sell cookie-cutter website designs have swooped in knowing there&#8217;s easy money to be made; restaurants are more than happy to outsource this sort of thing the same way they outsource their garbage disposal or linen.</p>
<p>it&#8217;s all the more sad because, as Jen said, it would be cheaper and so much more effective to have a 1-page site with contact info, hours, and directions &#8212; no upkeep necessary and dead easy to develop with NO FLASH.  A win for everyone.</p>
<p>it seems all hope is NOT lost though as I&#8217;m noticing quite a few local restauranteurs setting up (and updating!) Twitter feeds.  Certainly Twitter is a big fad these days, but increased technology-restaurant &#8220;fusion&#8221; can only help matters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Mason</title>
		<link>http://www.foodpr0n.com/2009/05/03/will-code-for-food/comment-page-1/#comment-51</link>
		<dc:creator>Rick Mason</dc:creator>
		<pubDate>Tue, 05 May 2009 20:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.foodpr0n.com/?p=414#comment-51</guid>
		<description><![CDATA[Couldn&#039;t agree with you more. The state of restaurant websites is horrible. There should be a restaurant website standard developed that everyone can adhere to in terms of presenting the important information. And what&#039;s more, I really dislike the various services that host dozens of resto websites. I find they just make things worse. I bet the reason many websites are poorly maintained is because these very networks most likely provide crappy tools for management of content.

The site and admin need to be dead simple. But also, the restaurant needs to make it someone&#039;s responsibility to keep the site current.]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree with you more. The state of restaurant websites is horrible. There should be a restaurant website standard developed that everyone can adhere to in terms of presenting the important information. And what&#8217;s more, I really dislike the various services that host dozens of resto websites. I find they just make things worse. I bet the reason many websites are poorly maintained is because these very networks most likely provide crappy tools for management of content.</p>
<p>The site and admin need to be dead simple. But also, the restaurant needs to make it someone&#8217;s responsibility to keep the site current.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
