<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wordpress Matt looking to dump Yahoo search because of &#8220;shaky foundation&#8221;</title>
	<link>http://www.makeyougohmm.com/20060527/3366/</link>
	<description>Technology, music, video, art, news, reviews and muse on the web</description>
	<pubDate>Mon, 15 Mar 2010 23:34:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: TDavid</title>
		<link>http://www.makeyougohmm.com/20060527/3366/#comment-106235</link>
		<author>TDavid</author>
		<pubDate>Sun, 28 May 2006 02:39:21 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060527/3366/#comment-106235</guid>
		<description>Google hasn't released many developer tools that I'm aware of with scaling problems, Oskar. Care to cite some specific examples? I will agree -- and have written here several times in the past -- that non-developer Google products/services have gotten off to a rocky start in the last year or so particularly. Big difference telling developers: hey, use this in your products/services vs. netizens descending on a beta release that doesn't scale.

With that said, and as mentioned in the piece above, I haven't experienced any Yahoo developer tool API scaling issues firsthand, so I'm apt to agree with your last sentence on this one. Throwing this out there to see what other developers have experienced.</description>
		<content:encoded><![CDATA[<p>Google hasn&#8217;t released many developer tools that I&#8217;m aware of with scaling problems, Oskar. Care to cite some specific examples? I will agree &#8212; and have written here several times in the past &#8212; that non-developer Google products/services have gotten off to a rocky start in the last year or so particularly. Big difference telling developers: hey, use this in your products/services vs. netizens descending on a beta release that doesn&#8217;t scale.</p>
<p>With that said, and as mentioned in the piece above, I haven&#8217;t experienced any Yahoo developer tool API scaling issues firsthand, so I&#8217;m apt to agree with your last sentence on this one. Throwing this out there to see what other developers have experienced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oskar Syahbana</title>
		<link>http://www.makeyougohmm.com/20060527/3366/#comment-106203</link>
		<author>Oskar Syahbana</author>
		<pubDate>Sun, 28 May 2006 01:32:44 +0000</pubDate>
		<guid>http://www.makeyougohmm.com/20060527/3366/#comment-106203</guid>
		<description>Talking about scale...
I think the other company that starts with a G is always releasing products that are not built-to-scale lately (remember analytic, or pages?, or writely? When on earth are they going to release it not invitation-based only?).

Probably there's a little hiccup on their network. You know stuff happens.</description>
		<content:encoded><![CDATA[<p>Talking about scale&#8230;<br />
I think the other company that starts with a G is always releasing products that are not built-to-scale lately (remember analytic, or pages?, or writely? When on earth are they going to release it not invitation-based only?).</p>
<p>Probably there&#8217;s a little hiccup on their network. You know stuff happens.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
