<?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 01:33:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Michael Nitschinger: A Journey on Avoiding Nulls in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/19210</guid>
      <link>http://www.phpdeveloper.org/news/19210</link>
      <description><![CDATA[<p>
<i>Michael Nitschinger</i> has written up a post looking at <a href="http://nitschinger.at/A-Journey-on-Avoiding-Nulls-in-PHP">avoiding nulls in your applications</a> in favor of a better kind of value handling - the introduction of "<a href="http://code.google.com/p/guava-libraries/wiki/UsingAndAvoidingNullExplained">Optional</a>" handling.
</p>
<blockquote>
While every developer has kind of accepted their existence, they are suddenly there when we'd desperately need them to not show up. How often did you writeif($obj === null) in your PHP code? Can't there be a better, more elegant and fault-tolerant solution to the problem?
</blockquote>
<p>
His solution is to create a PHP version of this "Optional" functionality (via an abstract class) that allows some evaluation of the returned value from method calls on the object. Methods like "isPresent", "getOrElse", "of" and "fromNullable"  make it easier to work with null values instead of just the triple-equals checking. He includes not only the code for the classes you'll need to implement it but examples of it in use - an "Optional" abstract class and two child classes, "Present" and "Absent".
</p>]]></description>
      <pubDate>Wed, 20 Feb 2013 12:17:39 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Danne Lundqvist's Blog: Gartner report on PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/13831</guid>
      <link>http://www.phpdeveloper.org/news/13831</link>
      <description><![CDATA[<p>
As <i>Danne Lundqvist</i> mentions in <a href="http://www.dotvoid.com/2010/01/gartner-report-on-php/">a new post</a>, there's a new <a href="http://blogs.gartner.com/mark_driver/2009/12/03/php-past-present-and-future/">post on the Gartner.com site</a> about the past, present and future of the PHP language.
</p>
<p>From the Gartner post:</p>
<blockquote>
I just published a research note on PHP.  Clients can find it <a href="http://my.gartner.com/portal/server.pt?gr=dd&ref=shareSummary&resId=1241721">here</a>. The research note goes into *much* more detail but the overview is [in the rest of the post]. Keep in mind that this content is targeted at mainstream IT organizations. PHP has been a cornerstone technology on the Web for more than a decade. While its adoption among mainstream IT organizations has been limited in the past, many corporate application development (AD) projects are discovering the unique benefits of PHP.
</blockquote>
<p>
<i>Danne</i> highlights two quotes that were of particular interest in the report - one from the quote above about PHP being a cornerstone of many corporate web application development and the other talking about PHP's role not just in backend application development but also it being useful in front-end toolsets too.
</p>]]></description>
      <pubDate>Wed, 13 Jan 2010 09:53:21 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: emPHPower @ OSCON]]></title>
      <guid>http://www.phpdeveloper.org/news/10578</guid>
      <link>http://www.phpdeveloper.org/news/10578</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> has <a href="http://sebastian-bergmann.de/archives/802-emPHPower-OSCON.html">poted about</a> a new something that he'll also be doing at this year's <a href="http://conferences.oreilly.com/oscon">OSCON</a> - leading a discussion about the <a href="http://en.oreilly.com/oscon2008/public/schedule/detail/4742">emPHPower initiative</a>.
</p>
<blockquote>
As the PHP community grows however, it becomes harder and harder for people to come together from the various corners of the community. [...] That being said, maybe there is still something we could change for the better? PHP contributor Lukas Smith has formulated his vision for such an effort in the form of an organization that would serve as a mediator and catalyst between all the members of the PHP community under the code name emPHPower.
</blockquote>
<p>
The <a href="http://en.oreilly.com/oscon2008/public/schedule/detail/4742">session</a> will be happening on Monday the 21st from 7-8pm.
</p>]]></description>
      <pubDate>Thu, 10 Jul 2008 11:18:20 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Perl.com: Programming is Hard, Let's Go Scripting...]]></title>
      <guid>http://www.phpdeveloper.org/news/9274</guid>
      <link>http://www.phpdeveloper.org/news/9274</link>
      <description><![CDATA[<p>
<i>Christian Wenz</i> has <a href="http://www.hauser-wenz.de/s9y/index.php?/archives/259-Larry-Wall-on-PHP.html">pointed out</a> an older post from <i>Larry Wall</i> talking about <a href="http://www.perl.com/pub/a/2007/12/06/soto-11.html">the line between scripting and programming languages</a> (mentioning specifically PHP).
</p>
<p>From the article "<a href="http://www.perl.com/pub/a/2007/12/06/soto-11.html"Programming is Hard, Let's Go Scripting...</a>":
<blockquote>
I think, to most people, scripting is a lot like obscenity. I can't define it, but I'll know it when I see it. [...] If I had to pick one metaphor, it'd be easy onramps. And a slow lane. Maybe even with some optional fast lanes.
</blockquote>
<p>
<i>Larry</i> goes through tons of different older languages commenting on their viability in the online community including: Javascript, LISP, Pascal, Python, Ruby and PHP. He then looks at the present and what sorts of things are happening in languages these days. This list includes things like early binding/late binding, eager typology/lazy typology, limited structures/rich structures, class-based/prototype-based and transaction/reaction/dynamic scope.
</p>]]></description>
      <pubDate>Wed, 19 Dec 2007 09:36:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Ben Ramsey's Blog: PHP Unconference '07 and ZendCon IRC Channel]]></title>
      <guid>http://www.phpdeveloper.org/news/8527</guid>
      <link>http://www.phpdeveloper.org/news/8527</link>
      <description><![CDATA[<p>
<i>Ben Ramsey</i> has <a href="http://benramsey.com/archives/php-unconference-07-and-zendcon-irc-channel/">a reminder</a> for those attending this year's Zend/PHP Conference & Expo (or maybe an incentive for those not yet signed up?) about the <a href="http://www.zendcon.com/wiki/index.php?title=Uncon">Unconference</a> that will be happening in its own space where developers can come and present on their own topics.
</p>
<blockquote>
When was the last time an event challenged your assumptions, and made you think? The PHP Unconference is a way to bring people who have a shared interest in PHP together. It could be just to explore interest in a common theme or it could be to do work together to accomplish a goal. 
</blockquote>
<p>
This year's chairperson is <a href="http://www.surripui.net/">Patrick Reilly</a> and they've posted some <a href="http://www.zendcon.com/wiki/index.php?title=Principles">basic principles</a> presenters will need to follow as well as a <a href="http://www.zendcon.com/wiki/index.php?title=Topics">space on the wiki</a> for topic suggestions or ones you'd like to present on.
</p>
<p>
You can learn more about this year's conference from <a href="http://www.zendcon.com">the main conference website</a> and stop by the <a href="irc://irc.freenode.net/zendcon">zendcon</a> channel on the <a href="http://freenode.net/">Freenode IRC network</a> to meet other attendees.
</p>]]></description>
      <pubDate>Fri, 24 Aug 2007 08:43:00 -0500</pubDate>
    </item>
  </channel>
</rss>
