<?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: RIM doesn&#8217;t get the Web</title>
	<atom:link href="http://www.markbaker.ca/blog/2008/10/rim-doesnt-get-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markbaker.ca/blog/2008/10/rim-doesnt-get-the-web/</link>
	<description>Celebrating the power of the Web</description>
	<lastBuildDate>Fri, 26 Aug 2011 20:00:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: QCon London 2008 Presentation Video :: Steve Vinoski&#8217;s Blog</title>
		<link>http://www.markbaker.ca/blog/2008/10/rim-doesnt-get-the-web/comment-page-1/#comment-1401</link>
		<dc:creator>QCon London 2008 Presentation Video :: Steve Vinoski&#8217;s Blog</dc:creator>
		<pubDate>Thu, 09 Apr 2009 22:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/?p=1996#comment-1401</guid>
		<description>[...] somehow incorporate those wrappers into their code. Either way, there&#8217;s simply no chance of reusing existing agreements; instead, both sides require non-trivial [...]</description>
		<content:encoded><![CDATA[<p>[...] somehow incorporate those wrappers into their code. Either way, there&#8217;s simply no chance of reusing existing agreements; instead, both sides require non-trivial [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.markbaker.ca/blog/2008/10/rim-doesnt-get-the-web/comment-page-1/#comment-1371</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 23 Oct 2008 20:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/?p=1996#comment-1371</guid>
		<description>Thanks, David.  What do you know about what Apple&#039;s up to?  Obviously iPhone app development is wee bit proprietary, but I haven&#039;t seen them try to offload iPhone-specific protocols on publishers like RIM are doing.

Android&#039;s a mixed bag too.  They reinvented a lot of mature Java APIs, and v1.0 integrates the browser into the OS the same way that people were doing it 10 years ago, so no innovation there.  But on the other hand they are being good about using open protocols like Jabber, and that is reusing existing agreement.  I would prefer to seem the use more of the Web though.</description>
		<content:encoded><![CDATA[<p>Thanks, David.  What do you know about what Apple&#8217;s up to?  Obviously iPhone app development is wee bit proprietary, but I haven&#8217;t seen them try to offload iPhone-specific protocols on publishers like RIM are doing.</p>
<p>Android&#8217;s a mixed bag too.  They reinvented a lot of mature Java APIs, and v1.0 integrates the browser into the OS the same way that people were doing it 10 years ago, so no innovation there.  But on the other hand they are being good about using open protocols like Jabber, and that is reusing existing agreement.  I would prefer to seem the use more of the Web though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbt</title>
		<link>http://www.markbaker.ca/blog/2008/10/rim-doesnt-get-the-web/comment-page-1/#comment-1370</link>
		<dc:creator>dbt</dc:creator>
		<pubDate>Thu, 23 Oct 2008 19:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.markbaker.ca/blog/?p=1996#comment-1370</guid>
		<description>According to everything I&#039;ve seen, the guys in Cupertino will be instituting exactly the same restrictions.  More and better research please.

(For an alternative, see what the Android guys are doing with Jabber.)

(Full disclosure:  I own an iphone, but know people on the android team)</description>
		<content:encoded><![CDATA[<p>According to everything I&#8217;ve seen, the guys in Cupertino will be instituting exactly the same restrictions.  More and better research please.</p>
<p>(For an alternative, see what the Android guys are doing with Jabber.)</p>
<p>(Full disclosure:  I own an iphone, but know people on the android team)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

