<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Daily Thought: Frontal Cranial Explosion</title>
	<atom:link href="http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/</link>
	<description>Programming and Life</description>
	<lastBuildDate>Tue, 29 Sep 2009 22:01:20 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeremy</title>
		<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/comment-page-1/#comment-999</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Tue, 30 Jan 2007 15:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/archives/daily-thought-frontal-cranial-explosion/#comment-999</guid>
		<description>I hate you.</description>
		<content:encoded><![CDATA[<p>I hate you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zaben</title>
		<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/comment-page-1/#comment-996</link>
		<dc:creator>Zaben</dc:creator>
		<pubDate>Tue, 30 Jan 2007 11:36:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/archives/daily-thought-frontal-cranial-explosion/#comment-996</guid>
		<description>PHP is not suitable for enterprise development</description>
		<content:encoded><![CDATA[<p>PHP is not suitable for enterprise development</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/comment-page-1/#comment-985</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Mon, 29 Jan 2007 14:17:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/archives/daily-thought-frontal-cranial-explosion/#comment-985</guid>
		<description>As an addendum:

I also believe that people should focus primarily on what they&#039;re comfortable with and can build their application in the fastest with the least amount of potential vulnerabilities. If you&#039;re the most qualified to work in your .NET Environment, so be it. If you can RTM faster in J2EE than Ruby on Rails, have at it.

My specialty may be PHP, but I consider myself to be a pretty &lt;em&gt;well-rounded&lt;/em&gt; developer. I know no Java and wouldn&#039;t touch Ruby with a ten foot pole, though. After some of the experiences I&#039;ve had over the past couple of years, at my present job and doing freelance work for other companies, I&#039;ll be the first to tell you that PHP certainly isn&#039;t for &lt;em&gt;everything&lt;/em&gt;. But, I&#039;ve had one too many experiences where it could&#039;ve been easier to push out a &lt;strong&gt;&lt;em&gt;Production-worthy Component&lt;/em&gt;&lt;/strong&gt; anywhere from five to ten times faster in PHP, yet the project stayed with its other infrastructure and ended up with, quite frankly, a half-assed solution. Case in point was when GU² Services was acquired by Probyn Marketing. I lost my job over that stupid crap, because my boss decided to infrastructure jump instead of sticking with what our developers knew and could handle the best.

It&#039;s all in using what you&#039;re comfortable with, of course. But, don&#039;t ever count out the underdog. And most certainly don&#039;t try to beat it down ...</description>
		<content:encoded><![CDATA[<p>As an addendum:</p>
<p>I also believe that people should focus primarily on what they&#8217;re comfortable with and can build their application in the fastest with the least amount of potential vulnerabilities. If you&#8217;re the most qualified to work in your .NET Environment, so be it. If you can RTM faster in J2EE than Ruby on Rails, have at it.</p>
<p>My specialty may be PHP, but I consider myself to be a pretty <em>well-rounded</em> developer. I know no Java and wouldn&#8217;t touch Ruby with a ten foot pole, though. After some of the experiences I&#8217;ve had over the past couple of years, at my present job and doing freelance work for other companies, I&#8217;ll be the first to tell you that PHP certainly isn&#8217;t for <em>everything</em>. But, I&#8217;ve had one too many experiences where it could&#8217;ve been easier to push out a <strong><em>Production-worthy Component</em></strong> anywhere from five to ten times faster in PHP, yet the project stayed with its other infrastructure and ended up with, quite frankly, a half-assed solution. Case in point was when GU² Services was acquired by Probyn Marketing. I lost my job over that stupid crap, because my boss decided to infrastructure jump instead of sticking with what our developers knew and could handle the best.</p>
<p>It&#8217;s all in using what you&#8217;re comfortable with, of course. But, don&#8217;t ever count out the underdog. And most certainly don&#8217;t try to beat it down &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/comment-page-1/#comment-984</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Mon, 29 Jan 2007 14:01:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/archives/daily-thought-frontal-cranial-explosion/#comment-984</guid>
		<description>Making me go through and approve your comment ... Loser. :P

Well, I wasn&#039;t talking about you so much. I can agree on the two points you mentioned, though. A lot of projects (the Engine especially) could benefit from real namespaces in PHP. I&#039;ve been watching the internals mailing list for a while now and keeping up specifically with PHP 6 development, and they&#039;ve sacrificed a lot of what would&#039;ve been really good functionality in favor of the &quot;KISS&quot; principle.

And I&#039;m not referring to larger already-established companies. If you&#039;ve already got your infrastructure built with another language, that&#039;s no skin off my back, and I hope it suits your needs quite nicely. Migration is not what I&#039;m looking for. I&#039;m looking for &lt;strong&gt;&lt;em&gt;new&lt;/em&gt;&lt;/strong&gt; adopters (like Yahoo!, as you mentioned) that can see what PHP has the potential to bring to the table. IBM has been doing a lot of work with PHP and even &lt;em&gt;Microsoft&lt;/em&gt; has formed a partnership with Zend. I think this should be enough to show people that PHP is a considerable player in Enterprise Development. There&#039;s a &lt;strong&gt;&lt;em&gt;lot&lt;/em&gt;&lt;/strong&gt; of things you can do in PHP. Granted, it&#039;s not the best for every situation, but oftentimes I find that a language is limited merely by the imagination of the person writing the code.</description>
		<content:encoded><![CDATA[<p>Making me go through and approve your comment &#8230; Loser. <img src='http://www.jeremyprivett.com/blog/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>Well, I wasn&#8217;t talking about you so much. I can agree on the two points you mentioned, though. A lot of projects (the Engine especially) could benefit from real namespaces in PHP. I&#8217;ve been watching the internals mailing list for a while now and keeping up specifically with PHP 6 development, and they&#8217;ve sacrificed a lot of what would&#8217;ve been really good functionality in favor of the &#8220;KISS&#8221; principle.</p>
<p>And I&#8217;m not referring to larger already-established companies. If you&#8217;ve already got your infrastructure built with another language, that&#8217;s no skin off my back, and I hope it suits your needs quite nicely. Migration is not what I&#8217;m looking for. I&#8217;m looking for <strong><em>new</em></strong> adopters (like Yahoo!, as you mentioned) that can see what PHP has the potential to bring to the table. IBM has been doing a lot of work with PHP and even <em>Microsoft</em> has formed a partnership with Zend. I think this should be enough to show people that PHP is a considerable player in Enterprise Development. There&#8217;s a <strong><em>lot</em></strong> of things you can do in PHP. Granted, it&#8217;s not the best for every situation, but oftentimes I find that a language is limited merely by the imagination of the person writing the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://www.jeremyprivett.com/blog/archives/daily-thought-frontal-cranial-explosion/comment-page-1/#comment-980</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Mon, 29 Jan 2007 02:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/archives/daily-thought-frontal-cranial-explosion/#comment-980</guid>
		<description>(Too lazy to log in)

I would have mentioned something in our convo along the lines of how they dump every function into a global namespace, and how its &quot;KISS&quot; philosophy holds the language back, but since you didn&#039;t want to discuss the subject further, I stopped. :p

At any rate, I won&#039;t bother getting into it, since your brain is probably very sore as it is.

...But just as a closer, the main reason it&#039;s probably not widely adopted is because large companies have already invested millions into their JSP/J2EE-powered web applications, and most Java web developers &lt;em&gt;hate&lt;/em&gt; PHP, so it&#039;d be too much work and cost too much money to migrate. Not to mention Java is understood to be more secure (PHP still has a few pesky buffer overflow flaws here and there), so it ends up being the language of choice. However, as shown by Yahoo being coded in PHP (#1 on Alexa), along with GameSpot and GameFAQs, it &lt;em&gt;can&lt;/em&gt; be used for large-scale web development, if effort is put into it.

*Stops now* :p</description>
		<content:encoded><![CDATA[<p>(Too lazy to log in)</p>
<p>I would have mentioned something in our convo along the lines of how they dump every function into a global namespace, and how its &#8220;KISS&#8221; philosophy holds the language back, but since you didn&#8217;t want to discuss the subject further, I stopped. :p</p>
<p>At any rate, I won&#8217;t bother getting into it, since your brain is probably very sore as it is.</p>
<p>&#8230;But just as a closer, the main reason it&#8217;s probably not widely adopted is because large companies have already invested millions into their JSP/J2EE-powered web applications, and most Java web developers <em>hate</em> PHP, so it&#8217;d be too much work and cost too much money to migrate. Not to mention Java is understood to be more secure (PHP still has a few pesky buffer overflow flaws here and there), so it ends up being the language of choice. However, as shown by Yahoo being coded in PHP (#1 on Alexa), along with GameSpot and GameFAQs, it <em>can</em> be used for large-scale web development, if effort is put into it.</p>
<p>*Stops now* :p</p>
]]></content:encoded>
	</item>
</channel>
</rss>

