<?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"
	>
<channel>
	<title>Comments on: Rethinking Apollo</title>
	<atom:link href="http://72.249.21.88/nonintersecting/?year=2007&#038;monthnum=05&#038;day=19&#038;name=rethinking-apollo&#038;feed=feed" rel="self" type="application/rss+xml" />
	<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/</link>
	<description>Life and Technology (non-intersecting)</description>
	<pubDate>Fri, 05 Dec 2008 02:55:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Clark Updike</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10746</link>
		<dc:creator>Clark Updike</dc:creator>
		<pubDate>Tue, 29 May 2007 19:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10746</guid>
		<description>I'm curious why Eclipse RCP didn't make the cut for intranet biz apps.  The following reasons don't apply AFAICT (except maybe spotty html rendinging--not sure on that one): 

"Java is a pain to develop towards-especially GUI apps, has spotty HTML rendering ability, and a non-native look and feel."  

Possibly the only reason would be getting up the RCP learning curve, but I know of nothing that indicates it would be any worse than Apollo.  And I have seen some impressive productivity by non-experts compared to development with web technologies.</description>
		<content:encoded><![CDATA[<p>I&#8217;m curious why Eclipse RCP didn&#8217;t make the cut for intranet biz apps.  The following reasons don&#8217;t apply AFAICT (except maybe spotty html rendinging&#8211;not sure on that one): </p>
<p>&#8220;Java is a pain to develop towards-especially GUI apps, has spotty HTML rendering ability, and a non-native look and feel.&#8221;  </p>
<p>Possibly the only reason would be getting up the RCP learning curve, but I know of nothing that indicates it would be any worse than Apollo.  And I have seen some impressive productivity by non-experts compared to development with web technologies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10732</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 23 May 2007 17:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10732</guid>
		<description>My biggest concern with Apollo is the breadth of deployment of the runtime.

However, I suspect that Adobe will have a solution for that.

I wouldnt be surprised if Flash 10 had the Apollo runtime built in. Flash 9 has good penetration, so I would be happy with that scenario.

http://www.adobe.com/products/player_census/flashplayer/version_penetration.html</description>
		<content:encoded><![CDATA[<p>My biggest concern with Apollo is the breadth of deployment of the runtime.</p>
<p>However, I suspect that Adobe will have a solution for that.</p>
<p>I wouldnt be surprised if Flash 10 had the Apollo runtime built in. Flash 9 has good penetration, so I would be happy with that scenario.</p>
<p><a href="http://www.adobe.com/products/player_census/flashplayer/version_penetration.html" rel="nofollow">http://www.adobe.com/products/player_census/flashplayer/version_penetration.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JD on EP</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10731</link>
		<dc:creator>JD on EP</dc:creator>
		<pubDate>Wed, 23 May 2007 15:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10731</guid>
		<description>&lt;strong&gt;Silverlight understanding...&lt;/strong&gt;

Silverlight understanding: BBC has an article here describing the late-May view of Microsoft's push into browser plugins. They pick up that the big win is in enabling .NET shops to do those Flash-y types of sites they've seen, but I think they get it...</description>
		<content:encoded><![CDATA[<p><strong>Silverlight understanding&#8230;</strong></p>
<p>Silverlight understanding: BBC has an article here describing the late-May view of Microsoft&#8217;s push into browser plugins. They pick up that the big win is in enabling .NET shops to do those Flash-y types of sites they&#8217;ve seen, but I think they get it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Francis</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10729</link>
		<dc:creator>Simon Francis</dc:creator>
		<pubDate>Wed, 23 May 2007 00:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10729</guid>
		<description>The benefits of Apollo go beyond off line ability. The real advantage is access to your computer. 

Something like a web browser for example can't put icons in the notification area next to the clock. An Apollo RSS reader could use native notifications to tell the user when new feeds are available.

An even bigger advantage is true cross platform development. Imagine writing a program that can target Windows, Linux, Mac OSX (via Apollo), and the web browser (via Flash).  The same code base can run directly in the browser on Flash or on the desktop using Apollo. 

Imagine writing an mp3 player - when I'm at work I want to be able to listen to streaming music, but when I'm at home I want to listen to both streaming music and my own collection. It would be a huge security hole if Javascript or Flash in the browser could access the files on my desktop, but a stand alone desktop application running on the Apollo runtime has no such weakness. So the developers of this mp3 player can use the same code and write an mp3 player that works in the browser as well on the desktop with additional functionality like access to the filesystem, and non-rectangular or transparent windows. See www.finetune.com.</description>
		<content:encoded><![CDATA[<p>The benefits of Apollo go beyond off line ability. The real advantage is access to your computer. </p>
<p>Something like a web browser for example can&#8217;t put icons in the notification area next to the clock. An Apollo RSS reader could use native notifications to tell the user when new feeds are available.</p>
<p>An even bigger advantage is true cross platform development. Imagine writing a program that can target Windows, Linux, Mac OSX (via Apollo), and the web browser (via Flash).  The same code base can run directly in the browser on Flash or on the desktop using Apollo. </p>
<p>Imagine writing an mp3 player - when I&#8217;m at work I want to be able to listen to streaming music, but when I&#8217;m at home I want to listen to both streaming music and my own collection. It would be a huge security hole if Javascript or Flash in the browser could access the files on my desktop, but a stand alone desktop application running on the Apollo runtime has no such weakness. So the developers of this mp3 player can use the same code and write an mp3 player that works in the browser as well on the desktop with additional functionality like access to the filesystem, and non-rectangular or transparent windows. See <a href="http://www.finetune.com" rel="nofollow">http://www.finetune.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill de hÃ“ra</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10727</link>
		<dc:creator>Bill de hÃ“ra</dc:creator>
		<pubDate>Tue, 22 May 2007 19:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10727</guid>
		<description>&lt;strong&gt;Behind the stonewall...&lt;/strong&gt;

Pete Lacey: "I would develop Apollo applications if, and only if, my application was deployed inside the firewall and I had a set-in-stone requirement that could not be met by a browser-based app. But, again, thatâ€™s just me. YMMV." For......</description>
		<content:encoded><![CDATA[<p><strong>Behind the stonewall&#8230;</strong></p>
<p>Pete Lacey: &#8220;I would develop Apollo applications if, and only if, my application was deployed inside the firewall and I had a set-in-stone requirement that could not be met by a browser-based app. But, again, thatâ€™s just me. YMMV.&#8221; For&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Mead</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10726</link>
		<dc:creator>Jerry Mead</dc:creator>
		<pubDate>Tue, 22 May 2007 19:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10726</guid>
		<description>"Ryan: Adobe Evangelist"

Ah ... kind of explains why a Zeepe-ish link sent to to Ryan on his ZDNet blog:

  http://www.zeepe.com/zeepeinfo/scottgu.asp

fell into such a deep dark hole.</description>
		<content:encoded><![CDATA[<p>&#8220;Ryan: Adobe Evangelist&#8221;</p>
<p>Ah &#8230; kind of explains why a Zeepe-ish link sent to to Ryan on his ZDNet blog:</p>
<p>  <a href="http://www.zeepe.com/zeepeinfo/scottgu.asp" rel="nofollow">http://www.zeepe.com/zeepeinfo/scottgu.asp</a></p>
<p>fell into such a deep dark hole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent Szyster</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10725</link>
		<dc:creator>Laurent Szyster</dc:creator>
		<pubDate>Tue, 22 May 2007 11:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10725</guid>
		<description>"(...) built with nothing more than HTML, CSS, Javascript, (...)"

You mean, just like a web browser application?

"(...) and a few easy to understand, Apollo specific commands (...)"

Not quite. Because it will depend on Adobe's proprietary runtime environment.

Given how Adobe Acrobat Reader morphed from a utility into a bug-laden monster, I'll stay with web standards, thank you!

And if somebody ask a standalone executable decoupled from the browser, there's a stable and open source XUL runner, free as in free beer *and* free speech.</description>
		<content:encoded><![CDATA[<p>&#8220;(&#8230;) built with nothing more than HTML, CSS, Javascript, (&#8230;)&#8221;</p>
<p>You mean, just like a web browser application?</p>
<p>&#8220;(&#8230;) and a few easy to understand, Apollo specific commands (&#8230;)&#8221;</p>
<p>Not quite. Because it will depend on Adobe&#8217;s proprietary runtime environment.</p>
<p>Given how Adobe Acrobat Reader morphed from a utility into a bug-laden monster, I&#8217;ll stay with web standards, thank you!</p>
<p>And if somebody ask a standalone executable decoupled from the browser, there&#8217;s a stable and open source XUL runner, free as in free beer *and* free speech.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10724</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Tue, 22 May 2007 08:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10724</guid>
		<description>Ru kidding me?  "The dynamic languages are far from guaranteed to be installed on any particular machineâ€”especially Windows machines"

How many machines is Apollo installed on now?

L&#38;F is given far too much weight...if it truly mattered, then web apps wouldn't look vastly different then for ex say Office.  Tell me what L&#38;F reminds you of Facebook?</description>
		<content:encoded><![CDATA[<p>Ru kidding me?  &#8220;The dynamic languages are far from guaranteed to be installed on any particular machineâ€”especially Windows machines&#8221;</p>
<p>How many machines is Apollo installed on now?</p>
<p>L&amp;F is given far too much weight&#8230;if it truly mattered, then web apps wouldn&#8217;t look vastly different then for ex say Office.  Tell me what L&amp;F reminds you of Facebook?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arcadian Visions &#187; Blog Archive &#187; Apollo&#8217;s Platform Appeal</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10723</link>
		<dc:creator>Arcadian Visions &#187; Blog Archive &#187; Apollo&#8217;s Platform Appeal</dc:creator>
		<pubDate>Tue, 22 May 2007 05:36:57 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10723</guid>
		<description>[...] Pete Lacey provides a fair analysis of Adobe&#8217;s Apollo. It&#8217;s a helpful post since it&#8217;s not really trying to strongly influence opinion about Apollo either way, even if it may inflame advocates of some of the technologies given somewhat gruff treatment. All told, the analysis sounds fine to me, but the development story still leaves me cold. If this is a packaged browser designed to normalize a web-based platform, are the critics morally, as well as technically, wrong for calling it a browser extension? I&#8217;m just not seeing it yet, I suppose. Ease of deployment is a worthy feature, but the Apollo deployment mechanism doesn&#8217;t seem easier than navigating to a URL in a browser. So, if it&#8217;s less easily deployed than a traditional browser-based app, it has to offer some combination of a better development story or better technology. [...]</description>
		<content:encoded><![CDATA[<p>[...] Pete Lacey provides a fair analysis of Adobe&#8217;s Apollo. It&#8217;s a helpful post since it&#8217;s not really trying to strongly influence opinion about Apollo either way, even if it may inflame advocates of some of the technologies given somewhat gruff treatment. All told, the analysis sounds fine to me, but the development story still leaves me cold. If this is a packaged browser designed to normalize a web-based platform, are the critics morally, as well as technically, wrong for calling it a browser extension? I&#8217;m just not seeing it yet, I suppose. Ease of deployment is a worthy feature, but the Apollo deployment mechanism doesn&#8217;t seem easier than navigating to a URL in a browser. So, if it&#8217;s less easily deployed than a traditional browser-based app, it has to offer some combination of a better development story or better technology. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Stewart</title>
		<link>http://72.249.21.88/nonintersecting/2007/05/19/rethinking-apollo/#comment-10722</link>
		<dc:creator>Ryan Stewart</dc:creator>
		<pubDate>Mon, 21 May 2007 04:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://wanderingbarque.com/nonintersecting/2007/05/19/rethinking-apollo/#comment-10722</guid>
		<description>This is a very cool writeup Pete, and it's good to see more people "get it". 

=Ryan
Adobe Evangelist</description>
		<content:encoded><![CDATA[<p>This is a very cool writeup Pete, and it&#8217;s good to see more people &#8220;get it&#8221;. </p>
<p>=Ryan<br />
Adobe Evangelist</p>
]]></content:encoded>
	</item>
</channel>
</rss>
