<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 11:54:09 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ibuildings Blog: The definition of evil]]></title>
      <guid>http://www.phpdeveloper.org/news/10820</guid>
      <link>http://www.phpdeveloper.org/news/10820</link>
      <description><![CDATA[<p>
On the Ibuildings blog there's a <a href="http://www.ibuildings.com/blog/archives/1211-The-definition-of-evil.html">new post</a> that looks at the "evils" of a crucial part of many web applications - caching.
</p>
<blockquote>
Recently a colleague stated that in theory, caching could be considered 'evil'. Now 'evil' is a very broad term which is used a lot in the IT community, but what does it really mean when we're talking about technical solutions? I asked around, but couldn't find a clear cut definition, so I went searching...
</blockquote>
<p>
In his search he came across a wide range of definitions, including one mentioning bad design or implying a lack of goals with a summarized meaning of "does harm to your aesthetic and engineering judgment". He applies this to caching and, because of it being a sort of counter-intuitive way to handle content (not just the pull and push), it could be considered slightly evil. Interesting interpretation...
</p>
<blockquote>
However, as anyone will tell you caching is a very necessary evil. [...] So while it does some minor harm to aesthetic and engineering judgment, the user gets a fast experience, which is really all that matters in the end.
</blockquote>]]></description>
      <pubDate>Wed, 13 Aug 2008 08:44:17 -0500</pubDate>
    </item>
  </channel>
</rss>
