<?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>Sun, 07 Sep 2008 15:37:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Jacob Santos's Blog: Zend Studio Neon]]></title>
      <guid>http://www.phpdeveloper.org/news/9256</guid>
      <link>http://www.phpdeveloper.org/news/9256</link>
      <description><![CDATA[<p>
<i>Jacob Santos</i> has <a href="http://www.santosj.name/php/zend-studio-neon/">posted a list</a> of things that he both likes and dislikes about one of Zend's beta offerings - <a href="http://www.zend.com/en/products/studio/eclipse/">Zend Neon</a>.
</p>
<blockquote>
I've been using Zend Studio Neon for the past three weeks and I have to say, for something that is free (beta software) it is quite good. Compared to using VS 2005, Zend Studio Neon has its advantages, since Visual Studio doesn't handle PHP well. Zend Studio Neon also has areas that I didn't like.
</blockquote>
<p>
His likes included the fact that it's not Eclipse (technically) and that it supports PHPUnit and PHPDocumentor out of the box. Dislikes included the fact that it might not be free in the future and that it lacks FTP support.
</p>]]></description>
      <pubDate>Mon, 17 Dec 2007 12:52:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Brian Moon's Blog: My Editor of Choice]]></title>
      <guid>http://www.phpdeveloper.org/news/8818</guid>
      <link>http://www.phpdeveloper.org/news/8818</link>
      <description><![CDATA[<p>
<i>Brian Moon</i> has <a href="http://doughboy.wordpress.com/2007/10/10/my-editor-of-choice/">posted today</a> about his editor fo choice for PHP work - <a href="http://www.jedit.org/">jEdit</a> and some of the benefits he thinks it has for other developers.
</p>
<blockquote>
I keep trying all the latest and greatest editors out there.  I fought with Eclipse and have tried the newer more PHP centric offerings built on Eclipse.  I recently tried out Komodo Edit for a week.  I had tried the Komodo IDE when it came out for Mac a while back.  But, I just keep coming back to jEdit.
</blockquote>
<p>
He's <a href="http://doughboy.wordpress.com/2007/10/10/my-editor-of-choice/">broken it down</a> into two (well, really three) different sections - the likes and dislikes followed by things that he "doesn't care about but you might" (including Subversion and CVS support).
</p>]]></description>
      <pubDate>Wed, 10 Oct 2007 11:40:18 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[I/O Reader: 15 Cool Things & 12 Things to Dislike About PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/8484</guid>
      <link>http://www.phpdeveloper.org/news/8484</link>
      <description><![CDATA[<p>
On the <a href="http://ioreader.com/">I/O Reader blog</a>, there's two different posts that take two sides of the spectrum when it comes to what to like and dislike about PHP, both lists of features of the the language:
</p>
<ul>
<li><a href="http://ioreader.com/2007/08/17/11-cool-things-about-php-that-most-people-overlook/">15 Cool Things About PHP That Most People Overlook</a> - a list including the Reflection API, the Standard PHP Library, type hinting and the "magic" functions.
<li><a href="http://ioreader.com/2007/08/19/12-things-you-should-dislike-about-php/">12 Things You Should Dislike About PHP</a> - this list includes things like naming conventions, that _tostring doesn't work as (he) expected, magic quotes and register globals and safe mode
</ul>
<p>
Both have their valid points and it's interesting to see how many of the points made in the first article he goes back on and mentions specific instances where it doesn't work as expected. Some of the comparisons seem a bit like he's comparing PHP to his experience in another language and not objectively on PHP's features alone.
</p>]]></description>
      <pubDate>Mon, 20 Aug 2007 08:32:00 -0500</pubDate>
    </item>
  </channel>
</rss>
