<?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>Sat, 25 May 2013 11:38:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Nick Halstead's Blog: Boycott WordPress?]]></title>
      <guid>http://www.phpdeveloper.org/news/8312</guid>
      <link>http://www.phpdeveloper.org/news/8312</link>
      <description><![CDATA[<p>
With all of the <a href="http://www.gophp5.org">push to move</a> to PHP5 these days, some people are asking more questions of some of the most common PHP applications as to how they plan to proceed. <i>Nick Halstead</i> <a href="http://blog.assembleron.com/2007/07/22/boycott-wordpress/">asks his question</a> on his blog today - should the community boycott WordPress?
</p>
<blockquote>
Technology moves forward and PHP will long term lose its dominant position unless it gets everyone to move along with it. [...] Frankly I use WordPress because it has the best plugins but it is no coding wonder and Matt [Mullenweg]'s energies would be better placed helping to move it to PHP 5 only.
</blockquote>
<p>
The reference there is to <a href="http://photomatt.net/2007/07/13/on-php/">a post</a> from <i>Matt</i> (from the WordPress project) going after the community a bit for trying to force a move to PHP5 and that it's "not a big deal" like some are making it out to be. <i>Nick</i> feels that, if it's the case that <i>Matt</i> doesn't even see the move to PHP5 as a big deal, maybe WordPress shouldn't be the one of the blogging tools of choice. 
</p>]]></description>
      <pubDate>Mon, 23 Jul 2007 17:17:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Ed Finkler's Blog: What Matt Mullenweg doesn't know about PHP5, and how it hurts him and his users]]></title>
      <guid>http://www.phpdeveloper.org/news/8260</guid>
      <link>http://www.phpdeveloper.org/news/8260</link>
      <description><![CDATA[<p>
On the heels of <a href="http://photomatt.net/2007/07/13/on-php/">a rant</a> posted by <i>Matt Mullenweg</i> (of Wordpress), <i>Ed Finkler</i> has <a href="http://funkatron.com/index.php/site/comments/what-matt-mullenweg-doesnt-know-about-php5-and-how-it-hurts-him-and-his-use/#When:01:19:32Z">posted some of his own thoughts</a> and rebuttals to the points <i>Matt</i> made.
</p>
<p>
Among these points are comments about PHP5 features that "could be helping Wordpress users right now" including:
</p>
<ul>
<li>Parameterized SQL input to eliminate SQL injection attacks
<li>Filter extension to combat XSS, CSRF, etc. attacks
<li>Prepared statement/transaction support in PDO and MySQLi
<li>Improved OOP features and support (code quality, extensibility)
</ul>
<p>
<i>Ed</i> <a href="http://funkatron.com/index.php/site/comments/what-matt-mullenweg-doesnt-know-about-php5-and-how-it-hurts-him-and-his-use/#When:01:19:32Z">pushes that</a> it's not about the slow adoption of PHP5 in other places. Its about the slow adoption of it in Wordpress so far as it relates to <i>Matt</i>:
</p>
<blockquote>
The thing is, support of PHP5-only features in WP would give it better speed and security right now. And especially in the case of security, Matt's reliance on what users say they want is a critical error: users don't ask about security until well after it becomes a serious issue. Wordpress has one of the worst security records of any PHP application, so I'll go out on a limb and say that it's a problem now. Even if WP users aren't talking about it, WP's core dev team should have addressed this already.
</blockquote>]]></description>
      <pubDate>Mon, 16 Jul 2007 18:12:00 -0500</pubDate>
    </item>
  </channel>
</rss>
