<?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: ⇥ Breaking into the PHP market</title>
	<atom:link href="http://blog.tabini.ca/2009/10/breaking-into-the-php-market/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tabini.ca/2009/10/breaking-into-the-php-market/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=breaking-into-the-php-market</link>
	<description>Stumbling on since 1997</description>
	<lastBuildDate>Fri, 07 Oct 2011 08:06:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Arbi Arzoumani</title>
		<link>http://blog.tabini.ca/2009/10/breaking-into-the-php-market/comment-page-1/#comment-492</link>
		<dc:creator>Arbi Arzoumani</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=180#comment-492</guid>
		<description>Good article! To say 4.5 million users is kind of vague without breaking down the meaning of who is a &#039;user&#039;. I would even go further than what Marco has suggested in terms of Community members and breakdown that down into 3 more groups. From my experience these are the people that matter to a company trying to cater to the PHP market:

(A) PHP App User: Uses applications written in PHP and has no direct exposure to the code
(B) PHP App Developer: Maintains and develop with plain PHP or apps/frameworks
(C) PHP App Engineer: Frameworks/CMS/applications in general
(D) PHP Core Engineer: PHP 5/6

Group (A) &gt; (B) &gt; (C) &gt; (D). There would be some people who are in all 4 groups, but  I say the 4.5 million is right if you consider PHP App Users (A). As Marco pointed out, most people who fall under the (A) category might not even know that the app they are using was written in PHP (i.e. Drupal admins/artists/managers/content providers). Why should they care? It works and they don&#039;t have to maintain it, but, they are the ones who will pay you to use your app. All you have to do is Maintain, support &amp; improve the app with your Engineers who rely on the Core Engineers that make the whole thing possible in the first place. 

Groups (B), (C) and (D) seek IT knowledge and some will even pay for it by going to a conference, subscribing to a magazine or buying a book. Now, knowledge is a tricky thing to sell and some might even argue that it should be free. There&#039;s a very fine line there. There&#039;s also the problem of the very short expiry date of any kind of knowledge in the IT world. For example, the average shelf-life of an IT book is 6 months! Knowledge on Technology is hard to sell. Your audience is small, gets bored easily and is always hungry so you better keep their attention with lots of interesting knowledge and show them sharks with laser beams mounted on their heads. Ok, maybe not laser beams, but you get the idea.

So, pick the group you want to sell to wisely young grasshopper. Now, if you&#039;ll excuse me, I have to go and calibrate some pulse rifles.

- A</description>
		<content:encoded><![CDATA[<p>Good article! To say 4.5 million users is kind of vague without breaking down the meaning of who is a &#8216;user&#8217;. I would even go further than what Marco has suggested in terms of Community members and breakdown that down into 3 more groups. From my experience these are the people that matter to a company trying to cater to the PHP market:</p>
<p>(A) PHP App User: Uses applications written in PHP and has no direct exposure to the code<br />
(B) PHP App Developer: Maintains and develop with plain PHP or apps/frameworks<br />
(C) PHP App Engineer: Frameworks/CMS/applications in general<br />
(D) PHP Core Engineer: PHP 5/6</p>
<p>Group (A) &gt; (B) &gt; (C) &gt; (D). There would be some people who are in all 4 groups, but  I say the 4.5 million is right if you consider PHP App Users (A). As Marco pointed out, most people who fall under the (A) category might not even know that the app they are using was written in PHP (i.e. Drupal admins/artists/managers/content providers). Why should they care? It works and they don&#8217;t have to maintain it, but, they are the ones who will pay you to use your app. All you have to do is Maintain, support &amp; improve the app with your Engineers who rely on the Core Engineers that make the whole thing possible in the first place. </p>
<p>Groups (B), (C) and (D) seek IT knowledge and some will even pay for it by going to a conference, subscribing to a magazine or buying a book. Now, knowledge is a tricky thing to sell and some might even argue that it should be free. There&#8217;s a very fine line there. There&#8217;s also the problem of the very short expiry date of any kind of knowledge in the IT world. For example, the average shelf-life of an IT book is 6 months! Knowledge on Technology is hard to sell. Your audience is small, gets bored easily and is always hungry so you better keep their attention with lots of interesting knowledge and show them sharks with laser beams mounted on their heads. Ok, maybe not laser beams, but you get the idea.</p>
<p>So, pick the group you want to sell to wisely young grasshopper. Now, if you&#8217;ll excuse me, I have to go and calibrate some pulse rifles.</p>
<p>- A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cal Evans</title>
		<link>http://blog.tabini.ca/2009/10/breaking-into-the-php-market/comment-page-1/#comment-491</link>
		<dc:creator>Cal Evans</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=180#comment-491</guid>
		<description>Marco,

This is a good post.  As I sit here at ZendCon and think back over what I&#039;ve seen this week, one of your points strikes a chord with me. I do appreciate Zend, Microsoft and IBM coming together to create the new simple cloud API. (the url escapes me at the moment...forgive me, it&#039;s early)  I would however, like to have seen more of the PHP community involved in this project. As you stated, no one framework has enough penetration to make it THE framework so I would have liked to see Zend reach out to the other two major frameworks and invite their participation in the project.

It would have been nice if Microsoft, who seems to have a clue these days, stepped up and insisted that there be more than just Zend Framework represented before they would get involved.  This would both help the project enjoy wider  acceptance and it would help cement their role as a thought leader in the PHP community and not just the community bartender. (Not that I&#039;m complaining about their role as community bartender)  :)

Beyond that, I think your estimate of PHP developers is much more accurate than the 4.5 million number. In their defense, Zend did not use the &lt;a href=&quot;http://dangerouslogic.com/office_lexicon.html#pidooma&quot; rel=&quot;nofollow&quot;&gt;PIDOMA&lt;/a&gt; methodology to arrive at that number, they got it from the Evans Data Corp (No relation) who published it this past spring. 

Thanks for the thought provoking post.

=C=</description>
		<content:encoded><![CDATA[<p>Marco,</p>
<p>This is a good post.  As I sit here at ZendCon and think back over what I&#8217;ve seen this week, one of your points strikes a chord with me. I do appreciate Zend, Microsoft and IBM coming together to create the new simple cloud API. (the url escapes me at the moment&#8230;forgive me, it&#8217;s early)  I would however, like to have seen more of the PHP community involved in this project. As you stated, no one framework has enough penetration to make it THE framework so I would have liked to see Zend reach out to the other two major frameworks and invite their participation in the project.</p>
<p>It would have been nice if Microsoft, who seems to have a clue these days, stepped up and insisted that there be more than just Zend Framework represented before they would get involved.  This would both help the project enjoy wider  acceptance and it would help cement their role as a thought leader in the PHP community and not just the community bartender. (Not that I&#8217;m complaining about their role as community bartender)  <img src='http://blog.tabini.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Beyond that, I think your estimate of PHP developers is much more accurate than the 4.5 million number. In their defense, Zend did not use the <a href="http://dangerouslogic.com/office_lexicon.html#pidooma" rel="nofollow">PIDOMA</a> methodology to arrive at that number, they got it from the Evans Data Corp (No relation) who published it this past spring. </p>
<p>Thanks for the thought provoking post.</p>
<p>=C=</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Tabini</title>
		<link>http://blog.tabini.ca/2009/10/breaking-into-the-php-market/comment-page-1/#comment-490</link>
		<dc:creator>Marco Tabini</dc:creator>
		<pubDate>Thu, 22 Oct 2009 13:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=180#comment-490</guid>
		<description>Thanks Ivo—fixed.</description>
		<content:encoded><![CDATA[<p>Thanks Ivo—fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivo</title>
		<link>http://blog.tabini.ca/2009/10/breaking-into-the-php-market/comment-page-1/#comment-489</link>
		<dc:creator>Ivo</dc:creator>
		<pubDate>Thu, 22 Oct 2009 13:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tabini.ca/?p=180#comment-489</guid>
		<description>very nice piece! There&#039;s a section missing after &#039;most core developers already think...&#039;; please elaborate what they think :)</description>
		<content:encoded><![CDATA[<p>very nice piece! There&#8217;s a section missing after &#8216;most core developers already think&#8230;&#8217;; please elaborate what they think <img src='http://blog.tabini.ca/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

