<?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 08:10:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Nikita Popov: Are PHP developers functophobic?]]></title>
      <guid>http://www.phpdeveloper.org/news/18352</guid>
      <link>http://www.phpdeveloper.org/news/18352</link>
      <description><![CDATA[<p>
In his most recent post <i>Nikita Popov</i> asks if <a href="http://nikic.github.com/2012/08/10/Are-PHP-developers-functophobic.html">PHP developers are functophobic</a> - that, in some of his experience, they don't like to use functions.
</p>
<blockquote>
Now, that was overly general, so let me clarify: PHP developers who have reached a certain degree of sophistication basically stop using plain functions - instead everything goes all classes and methods. At least that's the observation I made when looking at various open-source libraries and frameworks. The only type of function you'll find in any of the "high-quality" libs are anonymous functions. But that's pretty much it.
</blockquote>
<p>
He shares concern that this "anti-function" approach can cause some bad practices to come up, specifically when developers try to force things into OOP that don't need to be there. He suggests that "helper functions" are a perfect example of individual functions that might not need to go in a class. He notes that, unlike in other languages (like Python), PHP development tends to follow the "one class, one file" route. He wonders if a shift from this method and more to a "module" approach (a more "compact" method) could be a good thing.
</p>]]></description>
      <pubDate>Mon, 13 Aug 2012 12:58:25 -0500</pubDate>
    </item>
  </channel>
</rss>
