<?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>Thu, 23 May 2013 09:06:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Learn Computer: Is LAMP Pack Still Strong?]]></title>
      <guid>http://www.phpdeveloper.org/news/19393</guid>
      <link>http://www.phpdeveloper.org/news/19393</link>
      <description><![CDATA[<p>
On the "Learn Computer" site there's a <a href="http://www.learncomputer.com/is-lamp-pack-still-strong/">recent post</a> that wonders if the web development standard of the LAMP (Linux, Apache, MySQL and PHP) stack is "still strong" and will still stand up with new technologies.
</p>
<blockquote>
This year in tech (like almost every other year) has been filled with buzzwords. Many of them this year, however, are based around big data processing and web content: NoSQL, Hadoop, BigTable - the list goes on. With all the fuss around these new technologies, one might be tempted into thinking that these are the technologies of the future, and that from now on our servers and websites will be built upon, leaving technologies like LAMP in the dust. 
</blockquote>
<p>
They talk about some of the things the LAMP stack <i>doesn't</i> do well like difficulties with scalability on both the web server and database side. There's also mention of the things that it does do well, like getting things up and running quickly and with a solid structure. 
</p>
<blockquote>
That being the case, the LAMP stack is still going very strong, and it's definitely still extremely viable in small and medium-sized deployments; there are no signs of it waning in that regard, and I'd expect it to be a standard deployment for many companies and organizations for quite some time to come.
</blockquote>]]></description>
      <pubDate>Mon, 01 Apr 2013 12:55:09 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[CIO.com: PHP's Enterprise Strengths and Weaknesses, Take 2]]></title>
      <guid>http://www.phpdeveloper.org/news/9815</guid>
      <link>http://www.phpdeveloper.org/news/9815</link>
      <description><![CDATA[<p>
As is pointed out both by <a href="http://blog.calevans.com/2008/03/17/cio-magazine-take-2/">Cal Evans</a> and the <a href="http://devzone.zend.com/article/3274-CIO-Magazine-Publishes-Second-PHP-Article">Zend Developer Zone</a>, there's been another article posted due to the response from the (now infamous) CIO <a href="http://www.cio.com/article/176250">article</a> - <a href="http://www.cio.com/article/197152/PHP_s_Enterprise_Strengths_and_Weaknesses_Take_">"PHP's Enterprise Strengths and Weaknesses, Take 2"</a> (by Zend's <i>John Coggeshall</i>).
</p>
<blockquote>
So, in the digital toolbox of the developer, where has PHP been designed to work best? And where is it, perhaps, not the best tool for the job? [...] While other languages can surely be used to solve The Web Problem, in this article I explain why PHP is the premier solution for server-side Web scripting.
</blockquote>
<p>
<i>John</i> talks about how PHP was written for the web, how it approaches and handles web requests, the security of the language and some of the major software packages that are being used in PHP development today (like the Zend Framework, PHPUnit and PECL extensions).
</p>]]></description>
      <pubDate>Tue, 18 Mar 2008 11:19:37 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[International PHP Magazine: Poll Question: Major Strengths of Sympony Over its Competitors Are?]]></title>
      <guid>http://www.phpdeveloper.org/news/7013</guid>
      <link>http://www.phpdeveloper.org/news/7013</link>
      <description><![CDATA[<p>
The International PHP Magazine conducted <a href="http://www.php-mag.net/magphpde/magphpde_news/psecom,id,26726,nodeid,5.html">a poll</a> this past week that asked visitors to vote on which of the options was the biggest strength that the Symfony framework had over the competition.
</p>
<p>
Of the four options given, the one that came out on top was that the project is still under active development and was being added to all the time. Coming in second place was an appreciation for the level of documentation that the project offers.
</p>
<p>
Be sure to get your votes in on <a href="http://www.php-mag.net/magphpde/magphpde_news/psecom,id,26727,nodeid,5.html">this week's poll</a> that takes a step back and asks visitors to pick which of the options is their favorite framework. Options include WACT, CakePHP, Prado, Phrame, and others. Head over and <a href="http://www.php-mag.net/magphpde/magphpde_news/psecom,id,26727,nodeid,5.html">cast your vote</a> today.
</p>]]></description>
      <pubDate>Tue, 02 Jan 2007 13:39:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Mike Bernat's Blog: PHP Cookies vs Sessions - The Breakdown]]></title>
      <guid>http://www.phpdeveloper.org/news/6902</guid>
      <link>http://www.phpdeveloper.org/news/6902</link>
      <description><![CDATA[<p>
In a <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">recent post</a> to his blog, <i>Mike Bernat</i> gets down to basics with one of the key pieces of functionality in PHP data persistence - cookies vs. sessions.
</p>
<blockquote>
Knowing the basics of cookies and sessions is essential to any successful PHP programmer. It is useful to store pieces information on the users computer for later use. Things like when they last visited, language of choice, age, etc. Cookies and Sessions are the perfect solution to our needs.
</blockquote>
<p>
He <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">talks about both</a>, including demonstration code to clarify some points and a chart at the end to compare their features, strengths, and weaknesses.
</p>]]></description>
      <pubDate>Thu, 14 Dec 2006 16:58:00 -0600</pubDate>
    </item>
  </channel>
</rss>
