<?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, 19 May 2013 23:16:05 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[O'Reilly: $lamp =~ /^Linux,\s*Apache,\s*MySQL,P(?:hp|ython|erl[56])$/]]></title>
      <guid>http://www.phpdeveloper.org/news/5464</guid>
      <link>http://www.phpdeveloper.org/news/5464</link>
      <description><![CDATA[<p>
On the O'Reilly PHP blog today, there's <a href="http://www.oreillynet.com/onlamp/blog/2006/05/lamp_linuxsapachesmysqlphpytho.html">a look</a> at what really makes up the LAMP package - does it matter if it's just Linux/Apache/MySQL/PHP, or is the concept the same if we start making substitutions.
</p>
<quote>
<i>
LAMP technologies traditionally include Linux, Apache, MySQL, and, by happy coincidence, one of three "P" languages: PHP, Python or Perl. Of course, this is changing a bit. Many folks have long preferred PostgreSQL over MySQL because prior to MySQL 4.1 (or 5, depending upon your point of view), MySQL was pretty much a sophisticated toy, but LAPP probably doesn't sound as cool. Others prefer Ruby to Python, PHP and Perl, but prior to Rails, many folks assumed that switching to Ruby wouldn't be a good career move.
</i>
</quote>
<p>
One of the main questions <a href="http://www.oreillynet.com/onlamp/blog/2006/05/lamp_linuxsapachesmysqlphpytho.html">he looks at</a>, though, is whether Perl6 will join the ranks of the "P languagaes" in LAMP. He gives some code examples to illustrate how it might cause some headaches for developers, but others that are more powerful than some of their other-language counterparts.
</p>]]></description>
      <pubDate>Mon, 29 May 2006 06:21:16 -0500</pubDate>
    </item>
  </channel>
</rss>
