<?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: Closed APIs Suck:  An Open Letter to Salesforce</title>
	<atom:link href="http://kurt.karmalab.org/2007/11/23/closed-apis-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/</link>
	<description>Schrade.Blog</description>
	<lastBuildDate>Fri, 09 Jul 2010 06:07:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric Burke</title>
		<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/comment-page-1/#comment-157</link>
		<dc:creator>Eric Burke</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-157</guid>
		<description>Well said. A API seems like a horrible thing to cripple for the lower-end versions of a product. I had a similar situation with StarTeam several years ago. They did give us an API, but the JavaDocs were incomplete and they refused to provide source code to the API&#039;s public interfaces and classes. This made it quite difficult to use. It&#039;s not like we asked for source to internal implementation details.</description>
		<content:encoded><![CDATA[<p>Well said. A API seems like a horrible thing to cripple for the lower-end versions of a product. I had a similar situation with StarTeam several years ago. They did give us an API, but the JavaDocs were incomplete and they refused to provide source code to the API&#8217;s public interfaces and classes. This made it quite difficult to use. It&#8217;s not like we asked for source to internal implementation details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luigi Montanez</title>
		<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/comment-page-1/#comment-158</link>
		<dc:creator>Luigi Montanez</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-158</guid>
		<description>I would talk with your account executive. I work in a shop that integrates Rails apps with Salesforce (our clients are all on Enterprise though), and our account executives have always been reasonable when it comes to addressing the artificial limitations that Salesforce puts on their editions.</description>
		<content:encoded><![CDATA[<p>I would talk with your account executive. I work in a shop that integrates Rails apps with Salesforce (our clients are all on Enterprise though), and our account executives have always been reasonable when it comes to addressing the artificial limitations that Salesforce puts on their editions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Karr</title>
		<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/comment-page-1/#comment-159</link>
		<dc:creator>Douglas Karr</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-159</guid>
		<description>I&#039;ve worked in-depth with the SF API as well as a number of others and agree with you 100%.  The irony is that a UI requires so much more hardware, code, and support, than an API.  Yet, companies continue to treat APIs like a &#039;feature&#039; rather than what they should be - a minimal requirement.

I recently left a company that charged thousands for its API.  The Integration Team had 2 people and the support team had a few dozen.  It really made me scratch my head (still does!)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve worked in-depth with the SF API as well as a number of others and agree with you 100%.  The irony is that a UI requires so much more hardware, code, and support, than an API.  Yet, companies continue to treat APIs like a &#8216;feature&#8217; rather than what they should be &#8211; a minimal requirement.</p>
<p>I recently left a company that charged thousands for its API.  The Integration Team had 2 people and the support team had a few dozen.  It really made me scratch my head (still does!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Schinkel</title>
		<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/comment-page-1/#comment-160</link>
		<dc:creator>Mike Schinkel</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-160</guid>
		<description>The subject of this blog post was the entire reason I started the &quot;ThoughtsOnSalesforce.com&quot; blog.

Salesforce.com is filled with people especially at the C-level who only ever think about &quot;What&#039;s in it for ME?&quot; and to them, every customer touchpoint is a point at which they can attempt to grab some money off the table instead of realizing how giving some things away can provide a much larger benefit. Sad, because if they were more longsighted they could have become the Microsoft killer; as is I predict they will be little more than a footnote in time.

After over a year with my Salesforce.com-related blog, however, I just got so fed up with Salesforce.com that I sold the blog and moved to SugarCRM, and haven&#039;t looked back.</description>
		<content:encoded><![CDATA[<p>The subject of this blog post was the entire reason I started the &#8220;ThoughtsOnSalesforce.com&#8221; blog.</p>
<p>Salesforce.com is filled with people especially at the C-level who only ever think about &#8220;What&#8217;s in it for ME?&#8221; and to them, every customer touchpoint is a point at which they can attempt to grab some money off the table instead of realizing how giving some things away can provide a much larger benefit. Sad, because if they were more longsighted they could have become the Microsoft killer; as is I predict they will be little more than a footnote in time.</p>
<p>After over a year with my Salesforce.com-related blog, however, I just got so fed up with Salesforce.com that I sold the blog and moved to SugarCRM, and haven&#8217;t looked back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David D</title>
		<link>http://kurt.karmalab.org/2007/11/23/closed-apis-suck/comment-page-1/#comment-161</link>
		<dc:creator>David D</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:{a.guid}#comment-161</guid>
		<description>I&#039;m so miserable about this (lack of availability of API outside of Enterprise).    Have read Mike&#039;s blog and agree.  I have a killer app but unwilling to build it if I can only sell it to my customers who are willing to &quot;upgrade&quot; their Salesforce account to get it.

Not sure how firmly the heels are dug in, and I understand having to add value to justify Enterprise pricing ...but big opening for competitors.

SugarCRM (whatever that is) ... here I come....</description>
		<content:encoded><![CDATA[<p>I&#8217;m so miserable about this (lack of availability of API outside of Enterprise).    Have read Mike&#8217;s blog and agree.  I have a killer app but unwilling to build it if I can only sell it to my customers who are willing to &#8220;upgrade&#8221; their Salesforce account to get it.</p>
<p>Not sure how firmly the heels are dug in, and I understand having to add value to justify Enterprise pricing &#8230;but big opening for competitors.</p>
<p>SugarCRM (whatever that is) &#8230; here I come&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
