<?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: PHP - A Programmer&#8217;s Perspective</title>
	<atom:link href="http://www.prusak.com/how-did-we-get-here/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.prusak.com/how-did-we-get-here/</link>
	<description>Online Since 1996</description>
	<pubDate>Fri, 18 May 2012 02:19:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-7</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 18 Nov 2004 05:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-7</guid>
		<description>Actually, there is a product out there that will compile PHP scripts into windows executables.  I've never tested it, but it's out there.  Or, you could ship some scripts with the php executable and a batch file for putting it all together.    Your code would be all exposed that way, but that's not always a problem.

Or, on *nix/OSX, you can just include a bit of shell scripting at the top of your php doc and list php as a dependancy.  I run PHP scripts on lots of machines that don't even have web servers installed.

None of this is as ideal as a real, crossplatform, PHP compiler, but we may get there someday.  Until the, you can make it work if you're willing to get creative.</description>
		<content:encoded><![CDATA[<p>Actually, there is a product out there that will compile PHP scripts into windows executables.  I&#8217;ve never tested it, but it&#8217;s out there.  Or, you could ship some scripts with the php executable and a batch file for putting it all together.    Your code would be all exposed that way, but that&#8217;s not always a problem.</p>
<p>Or, on *nix/OSX, you can just include a bit of shell scripting at the top of your php doc and list php as a dependancy.  I run PHP scripts on lots of machines that don&#8217;t even have web servers installed.</p>
<p>None of this is as ideal as a real, crossplatform, PHP compiler, but we may get there someday.  Until the, you can make it work if you&#8217;re willing to get creative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manolo Gómez</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-6</link>
		<dc:creator>Manolo Gómez</dc:creator>
		<pubDate>Wed, 10 Nov 2004 05:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-6</guid>
		<description>Whoa, about time I see a good article like this. Congrats.
I agree completely in the definitions you give (truly, where are administrators?), and I've had many good experiences using PHP to solve computer science specific problems, like building a compiler, genetic algorithms, design patterns. Things like Object-relational mapping, workflow engines and business rules engines are hard to do in PHP (compared with Java for instance), but you can make them if you have in mind the quirks of PHP, being stateless, script language and such.

I only wish that someday, PHP could become a full fledged platform for standalone applications but keeping the web specific parts as easy as it is now.</description>
		<content:encoded><![CDATA[<p>Whoa, about time I see a good article like this. Congrats.<br />
I agree completely in the definitions you give (truly, where are administrators?), and I&#8217;ve had many good experiences using PHP to solve computer science specific problems, like building a compiler, genetic algorithms, design patterns. Things like Object-relational mapping, workflow engines and business rules engines are hard to do in PHP (compared with Java for instance), but you can make them if you have in mind the quirks of PHP, being stateless, script language and such.</p>
<p>I only wish that someday, PHP could become a full fledged platform for standalone applications but keeping the web specific parts as easy as it is now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ali khalili</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-5</link>
		<dc:creator>ali khalili</dc:creator>
		<pubDate>Tue, 09 Nov 2004 16:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-5</guid>
		<description>hello.Thanks for your good article!</description>
		<content:encoded><![CDATA[<p>hello.Thanks for your good article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JIm</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-4</link>
		<dc:creator>JIm</dc:creator>
		<pubDate>Tue, 09 Nov 2004 15:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-4</guid>
		<description>Well said. I agree with you entirely and have often had the same thought myself. I rarely read PHP articles (and almost skipped over yours) because I am so used to seeing articles with a million (often poorly written) detailed lines of code to solve a specific problem in a specific fashion. And, when I say specfic problem, I don't mean anything interesting like... Object Persistence, or, scalable file-upload solutions. I mean things like, guestbooks, email forms, and blogging engines. 

I look forward to reading your next article.</description>
		<content:encoded><![CDATA[<p>Well said. I agree with you entirely and have often had the same thought myself. I rarely read PHP articles (and almost skipped over yours) because I am so used to seeing articles with a million (often poorly written) detailed lines of code to solve a specific problem in a specific fashion. And, when I say specfic problem, I don&#8217;t mean anything interesting like&#8230; Object Persistence, or, scalable file-upload solutions. I mean things like, guestbooks, email forms, and blogging engines. </p>
<p>I look forward to reading your next article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BDKR</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-3</link>
		<dc:creator>BDKR</dc:creator>
		<pubDate>Tue, 09 Nov 2004 13:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-3</guid>
		<description>I agree with you by and large, but there is just one point where I'm a little confused. Why do you put administrators in with designers? These are two totally different animals.

&lt;em&gt;&lt;strong&gt;ophir&lt;/strong&gt;: I've added footnote #2 to address this question.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I agree with you by and large, but there is just one point where I&#8217;m a little confused. Why do you put administrators in with designers? These are two totally different animals.</p>
<p><em><strong>ophir</strong>: I&#8217;ve added footnote #2 to address this question.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.prusak.com/how-did-we-get-here/comment-page-1/#comment-2</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 04 Nov 2004 21:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.prusak.com/archives/2004-11-04/how-did-we-get-here/#comment-2</guid>
		<description>I agree with you.  I used to teach an afterschool class in general computing.  PHP is a great vehicle for teaching the fundamentals of programming, but the teacher must be careful to teach programming, not PHP.  I find, it's often beneficial to look at more than one programming language when teaching programming concepts.  I like languages with similar syntax (C, C++, Java, Javascript, PHP) because you don't have to spend much time explaining the language.  It seems to help, when demonstrating different concepts to show them in more than one language,  even if the students are only going to work with one language.  I find, it seems to help separate concept from application.</description>
		<content:encoded><![CDATA[<p>I agree with you.  I used to teach an afterschool class in general computing.  PHP is a great vehicle for teaching the fundamentals of programming, but the teacher must be careful to teach programming, not PHP.  I find, it&#8217;s often beneficial to look at more than one programming language when teaching programming concepts.  I like languages with similar syntax (C, C++, Java, Javascript, PHP) because you don&#8217;t have to spend much time explaining the language.  It seems to help, when demonstrating different concepts to show them in more than one language,  even if the students are only going to work with one language.  I find, it seems to help separate concept from application.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

