<?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: The Jetpack Debate</title>
	<atom:link href="http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/feed/" rel="self" type="application/rss+xml" />
	<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/</link>
	<description>Robert Accettura&#039;s Personal Blog on Web Development and Tech</description>
	<lastBuildDate>Thu, 09 Feb 2012 09:10:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Simon</title>
		<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/comment-page-1/#comment-849701</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 11 Jan 2010 20:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://robert.accettura.com/?p=3416#comment-849701</guid>
		<description>@Robert: a good comparison - certainly, JetPack should be able to do anything GreaseMonkey can, and probably more cleanly given the availability of JQuery syntax. I think it&#039;s niche is a little higher than that, though - like I said before, it also compares well with IE8&#039;s Accelerators, which allow very simple extensions to browser behaviour. JetPack is more capable than those too, but that&#039;s till the space I see it in - good for writing simple browser hacks, not well suited to anything really sophisticated.</description>
		<content:encoded><![CDATA[<p>@Robert: a good comparison &#8211; certainly, JetPack should be able to do anything GreaseMonkey can, and probably more cleanly given the availability of JQuery syntax. I think it&#8217;s niche is a little higher than that, though &#8211; like I said before, it also compares well with IE8&#8242;s Accelerators, which allow very simple extensions to browser behaviour. JetPack is more capable than those too, but that&#8217;s till the space I see it in &#8211; good for writing simple browser hacks, not well suited to anything really sophisticated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/comment-page-1/#comment-849023</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Mon, 11 Jan 2010 02:49:56 +0000</pubDate>
		<guid isPermaLink="false">http://robert.accettura.com/?p=3416#comment-849023</guid>
		<description>@Majken &quot;Lucy&quot; Connor: It does, but I think to a lesser degree.  I&#039;m not sure if I&#039;d attribute it to market-hype flooding the iPhone ecosystem to a greater degree, or something else.

@Simon: I view Jetpack as more complementary (similar to Greasemonkey) because of pretty much that.</description>
		<content:encoded><![CDATA[<p>@Majken &#8220;Lucy&#8221; Connor: It does, but I think to a lesser degree.  I&#8217;m not sure if I&#8217;d attribute it to market-hype flooding the iPhone ecosystem to a greater degree, or something else.</p>
<p>@Simon: I view Jetpack as more complementary (similar to Greasemonkey) because of pretty much that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/comment-page-1/#comment-849020</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 11 Jan 2010 02:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://robert.accettura.com/?p=3416#comment-849020</guid>
		<description>This reminds me a bit of Valgrind, which also provides facilities for building program analysis tools.  There are similar frameworks out there that make it really easy to write a really simple analysis tool.  In Valgrind simple tools require a bit more effort.  But really simple tools are boring, it&#039;s the complicated/powerful ones that are interesting.  And that&#039;s where Valgrind shines in comparison to these other frameworks.

IMHO, the ability to write a really simple tool (or Jetpack) in 5 lines is overrated.</description>
		<content:encoded><![CDATA[<p>This reminds me a bit of Valgrind, which also provides facilities for building program analysis tools.  There are similar frameworks out there that make it really easy to write a really simple analysis tool.  In Valgrind simple tools require a bit more effort.  But really simple tools are boring, it&#8217;s the complicated/powerful ones that are interesting.  And that&#8217;s where Valgrind shines in comparison to these other frameworks.</p>
<p>IMHO, the ability to write a really simple tool (or Jetpack) in 5 lines is overrated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/comment-page-1/#comment-849004</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 11 Jan 2010 01:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://robert.accettura.com/?p=3416#comment-849004</guid>
		<description>Yes, one thing someone else commented on is that the Jetpack extensions can only use features that have been exposed to it through APIs like jetpack.slideBar, whereas regular extensions can do practically anything. That may be a good security model, but would seem crippling to many of the extensions currently available.

That said, I&#039;ve played with it a bit, and one thing is does* seem good for is simple &#039;helper&#039; scripts. One of IE8&#039;s nicer features is what they call Accelerators, letting you do things like select an address from a page, right-click, &quot;map with live search&quot; to show that address on a map. Or select some foreign-language text, right-click, &quot;translate with live search&quot; to get an English translation. 

I think of them as &quot;micro extensions&quot; - a very simple addon, not requiring any sophisticated UI, and ideally, something that can be coded in a dozen lines or less. That seems to be a good match for the Jetpack model...</description>
		<content:encoded><![CDATA[<p>Yes, one thing someone else commented on is that the Jetpack extensions can only use features that have been exposed to it through APIs like jetpack.slideBar, whereas regular extensions can do practically anything. That may be a good security model, but would seem crippling to many of the extensions currently available.</p>
<p>That said, I&#8217;ve played with it a bit, and one thing is does* seem good for is simple &#8216;helper&#8217; scripts. One of IE8&#8242;s nicer features is what they call Accelerators, letting you do things like select an address from a page, right-click, &#8220;map with live search&#8221; to show that address on a map. Or select some foreign-language text, right-click, &#8220;translate with live search&#8221; to get an English translation. </p>
<p>I think of them as &#8220;micro extensions&#8221; &#8211; a very simple addon, not requiring any sophisticated UI, and ideally, something that can be coded in a dozen lines or less. That seems to be a good match for the Jetpack model&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Majken "Lucy" Connor</title>
		<link>http://robert.accettura.com/blog/2010/01/10/the-jetpack-debate/comment-page-1/#comment-848998</link>
		<dc:creator>Majken "Lucy" Connor</dc:creator>
		<pubDate>Mon, 11 Jan 2010 01:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://robert.accettura.com/?p=3416#comment-848998</guid>
		<description>&quot;There are indeed some great apps and I say that as an iPhone user myself, but for each great application there are 1,000 that aren’t worth the price (which is often free).&quot;

I&#039;m not sure how this statement doesn&#039;t also apply to AMO...</description>
		<content:encoded><![CDATA[<p>&#8220;There are indeed some great apps and I say that as an iPhone user myself, but for each great application there are 1,000 that aren’t worth the price (which is often free).&#8221;</p>
<p>I&#8217;m not sure how this statement doesn&#8217;t also apply to AMO&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

