<?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>Tue, 21 May 2013 08:45:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Florin Patan: Next big thing in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/19241</guid>
      <link>http://www.phpdeveloper.org/news/19241</link>
      <description><![CDATA[<p>
<i>Florin Patan</i> has posted about what he calls the <a href="http://florinpatan.ro/2013/02/11/next-big-thing-in-php/">next big thing in PHP</a> - his observations of the current state of the language/community and what could be coming down the road.
</p>
<blockquote>
What's the next big thing in PHP? Or more accurately, how do you get to wish/want for a next big thing in PHP? PHP currently is seen as a jack of all trades, master none by most of people outside of PHP world and it's starting to look the same way for people who are using it as well. How did we got there?
</blockquote>
<p>
He spends a lot of the post talking about the future of PHP, though - what could be coming along with a PHP 6 release. He suggests that, with the way things are going, PHP could not be around too much longer if something dosen't change. He also makes several suggestions to the core PHP developers about what they could do to help the situation including strong typed variables, a "smarter parser" and a poll for PHP.net asking the users what they want in the language.
</p>
<blockquote>
This should be the next big thing in PHP. Collaboration and better community interface for both worlds, users and devs. Help us help you on PHP6, help us making a better world for everyone using PHP.
</blockquote>]]></description>
      <pubDate>Wed, 27 Feb 2013 12:19:47 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Sephiroth.it: PHP5 - a big failure?]]></title>
      <guid>http://www.phpdeveloper.org/news/4858</guid>
      <link>http://www.phpdeveloper.org/news/4858</link>
      <description><![CDATA[New today from <i>Gabriele Farina</i> on Sephiroth.it, there's <a href="http://www.sephiroth.it/index.php?blogId=2006_02_16_weekly.html">a post</a> that asks the question, "Is PHP5 a big failure?"
<p>
<quote>
<i>
PHP 5 has been presented as a revolution, a lot of new features have been added and a lot of projects have been made. But only a small group of hosters seem interested in supporting PHP 5 on their web servers. It is not so useful to have a beautiful programming language to use if we can't apply it to production environments.
<p>
We MUST use PHP 5 to help it growing until it become the standard...
</i>
</quote>
<p>
PHP5 has seen a pretty slow adoption rate so far, but according to some statistics, its usage has been picking up lately - even among hosting providers.]]></description>
      <pubDate>Fri, 17 Feb 2006 06:44:26 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Big Nerd Ranch Blog: XML in PHP 5]]></title>
      <guid>http://www.phpdeveloper.org/news/4334</guid>
      <link>http://www.phpdeveloper.org/news/4334</link>
      <description><![CDATA[<i>David Sklar</i> has <a href="http://www.sklar.com/blog/archives/70-Big-Nerd-Blog.html">this pointer</a> on his blog today to <a href="http://weblog.bignerdranch.com/?p=8">a new post</a> on the Big Nerd Ranch blog today dealing with XML and PHP5.
<p>
<quote>
<i>
Now that PHP 5 is becoming more and more prevalent over its predecessors, some really good books that cover PHP need revisions. Nowhere is this more true than with XML-related topics, where PHP 5 has a completely different way of working with XML - and, in fact, the mechanisms from PHP 4 will no longer work.
<p>
In this article, we'll be looking at one way to build and parse an XML tree using the new methods in PHP 5.
</i>
</quote>
<p>
They <a href="http://weblog.bignerdranch.com/?p=8">look at a generic XML document</a> they'll use to test and move quickly into a way to create it using the DOM functionality in PHP. From there, they use a simple ten-line script to parse it and echo it back out...]]></description>
      <pubDate>Sat, 19 Nov 2005 05:26:38 -0600</pubDate>
    </item>
  </channel>
</rss>
