<?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>Mon, 17 Jun 2013 23:57:21 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[RubySource.com: Confessions of a Converted PHP Developer: Ugly Code]]></title>
      <guid>http://www.phpdeveloper.org/news/16191</guid>
      <link>http://www.phpdeveloper.org/news/16191</link>
      <description><![CDATA[<p>
On RubySource.com there's a recent post with a bit of a confession from an ex-PHP developer who's moved over to Ruby about <a href="http://rubysource.com/confessions-of-a-converted-php-developer-ugly-code/">some of he is experiences</a> in making the shift and why he's a convert now.
</p>
<blockquote>
I've been a PHP developer for nearly a decade, and in January this year I started developing in Ruby. While initially a sceptic, I'm now a convert - and I'm here to share my experiences with you. [...]  I'd like to think of myself as a fairly good PHP developer, and the idea of moving to Rails was both scary and exciting. [...] In Ruby's defence, these are frustrations that are well made up for with the delights of finding out how easy other things are to do - and any learning process has its frustrations.
</blockquote>
<p>
He compares a bit of code that would take a list of email addresses and pull out the domain parts of each, grabbing only the unique ones. He includes some PHP code (using anonymous functions in PHP 5.3) to get the job done and compares it to the Ruby method that's a bit more fluid and readable. He talks about some of his frustrations during the learning process of creating code like this and includes his steps as he evolved through it.
</p>]]></description>
      <pubDate>Wed, 13 Apr 2011 13:12:02 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Alan Knowles' Blog: Licence to release PHP code?]]></title>
      <guid>http://www.phpdeveloper.org/news/9878</guid>
      <link>http://www.phpdeveloper.org/news/9878</link>
      <description><![CDATA[<p>
A little while back, <i>Alan Knowles</i> <a href="http://www.akbkhome.com/blog.php/View/159/Licence_to_release_PHP_code.html">wondered something</a> that I'm sure has crosses the mind of every PHP developer out there, especially when they came across a particularly bad chunk of code - some people should need to apply for a license before releasing their PHP code out into the wild.
</p> 
<blockquote>
Unlike most of the reviews you get, I was specifically looking at code quality [of the CMSs]. not fuzzy does it look nice!
</blockquote>
<p>
He looks at a whole list of them including: Tanslucis, Siteman, Pivot, jaf-cms, Guppy, Doop and CutePHP. Unfortunately, most of the news is bad - between badly structured code and mixes of HTML and PHP, there was almost nothing good in any of them.
</p>]]></description>
      <pubDate>Fri, 28 Mar 2008 11:10:37 -0500</pubDate>
    </item>
  </channel>
</rss>
