<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Salesforce.com: A New Microsoft?</title>
	<atom:link href="http://reverendted.wordpress.com/2008/06/25/salesforcecom-a-new-microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://reverendted.wordpress.com/2008/06/25/salesforcecom-a-new-microsoft/</link>
	<description>Also known as "Open Source Advocacy with Reverend Ted"</description>
	<lastBuildDate>Wed, 06 Jan 2010 01:41:09 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ted Haeger</title>
		<link>http://reverendted.wordpress.com/2008/06/25/salesforcecom-a-new-microsoft/#comment-59852</link>
		<dc:creator>Ted Haeger</dc:creator>
		<pubDate>Sat, 28 Jun 2008 16:07:14 +0000</pubDate>
		<guid isPermaLink="false">http://reverendted.wordpress.com/?p=553#comment-59852</guid>
		<description>@Ben Kepes:
You have my wholehearted agreement. Right now, Salesforce.com is indeed playing for all the marbles. Viable, &lt;i&gt;open&lt;/i&gt; contenders could certainly disrupt the play Salesforce is attempting.
I started this post long before Google AppEngine was announced, and I did not adapt the content in light of the advent of  AppEngine. Google&#039;s entry into platform space certainly validates the potential market, and may even counter Salesforce to an extent. While AppEngine is still an incomplete offering, it may help show SaaS entrepreneurs that there are options to investigate.
Thanks for your comment,
--Ted</description>
		<content:encoded><![CDATA[<p>@Ben Kepes:<br />
You have my wholehearted agreement. Right now, Salesforce.com is indeed playing for all the marbles. Viable, <i>open</i> contenders could certainly disrupt the play Salesforce is attempting.<br />
I started this post long before Google AppEngine was announced, and I did not adapt the content in light of the advent of  AppEngine. Google&#8217;s entry into platform space certainly validates the potential market, and may even counter Salesforce to an extent. While AppEngine is still an incomplete offering, it may help show SaaS entrepreneurs that there are options to investigate.<br />
Thanks for your comment,<br />
&#8211;Ted</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Kepes</title>
		<link>http://reverendted.wordpress.com/2008/06/25/salesforcecom-a-new-microsoft/#comment-59847</link>
		<dc:creator>Ben Kepes</dc:creator>
		<pubDate>Sat, 28 Jun 2008 03:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://reverendted.wordpress.com/?p=553#comment-59847</guid>
		<description>Great post - and yes it raises many questions about whether there is room for more than one MegaPaaS player. I believe there is - and more and more openess is the way of the future so users can mix and match different discrete offerings from different players. To a certain extent salesforce is going down a high risk/high reward strategy - if it wins, it wins bigtime, but if another PaaS player manages to eat a significant proportion of their lunch they could be in trouble...</description>
		<content:encoded><![CDATA[<p>Great post &#8211; and yes it raises many questions about whether there is room for more than one MegaPaaS player. I believe there is &#8211; and more and more openess is the way of the future so users can mix and match different discrete offerings from different players. To a certain extent salesforce is going down a high risk/high reward strategy &#8211; if it wins, it wins bigtime, but if another PaaS player manages to eat a significant proportion of their lunch they could be in trouble&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
