<?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: On brand consistency and BHAGs</title>
	<atom:link href="http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Sat, 19 Jan 2013 00:09:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<item>
		<title>By: John Coonen</title>
		<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/comment-page-1/#comment-111204</link>
		<dc:creator>John Coonen</dc:creator>
		<pubDate>Wed, 21 Oct 2009 20:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1733#comment-111204</guid>
		<description><![CDATA[What Would Lloyd Benson Say: 

&quot;Adobe? I knew Google. Google was a friend of mine. Adobe, you&#039;re no Google.&quot; 

Agree, Adobe&#039;s a great, empowering tool. Adobe&#039;s here to help folks like Google and others create fundamental change.]]></description>
		<content:encoded><![CDATA[<p>What Would Lloyd Benson Say: </p>
<p>&#8220;Adobe? I knew Google. Google was a friend of mine. Adobe, you&#8217;re no Google.&#8221; </p>
<p>Agree, Adobe&#8217;s a great, empowering tool. Adobe&#8217;s here to help folks like Google and others create fundamental change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ankush Narula</title>
		<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/comment-page-1/#comment-110977</link>
		<dc:creator>Ankush Narula</dc:creator>
		<pubDate>Wed, 07 Oct 2009 13:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1733#comment-110977</guid>
		<description><![CDATA[a little devil&#039;s advocate here... I wouldn&#039;t entirely agree that Adobe hasn&#039;t tackled  any Inspiring BHAGs.  Flash and AIR both pre-date their HTML/CSS/SVG counterparts.  Flash certainly changed what was possible on a web page... And has driven creativity and innovation quite far.  If nothing else, Adobe has driven the vision of rich asynchronous web applications and subsequently or indirectly spurred innovations in web browser standards.  Let&#039;s also not dismiss PDF and it&#039;s impact on the move away from printing, faxing, and snail mail.  I think it&#039;s easy from a web infrastructure perspective todismiss presentation layer technologies an their impacts.  I mean for deeper tier technologist that architect communications and security protocols, the presentation layer is just another client.  Google Wave is communications infrastructure -  outside the scope of Adobe&#039;s core competency - the presentation layer.  But to dismss Adobe&#039;s successes in transforming the web&#039;s presentation layer or how people work would be harsh.  That said, I will concede that adobe&#039;s successes were probably not based initially on BHAGs.]]></description>
		<content:encoded><![CDATA[<p>a little devil&#8217;s advocate here&#8230; I wouldn&#8217;t entirely agree that Adobe hasn&#8217;t tackled  any Inspiring BHAGs.  Flash and AIR both pre-date their HTML/CSS/SVG counterparts.  Flash certainly changed what was possible on a web page&#8230; And has driven creativity and innovation quite far.  If nothing else, Adobe has driven the vision of rich asynchronous web applications and subsequently or indirectly spurred innovations in web browser standards.  Let&#8217;s also not dismiss PDF and it&#8217;s impact on the move away from printing, faxing, and snail mail.  I think it&#8217;s easy from a web infrastructure perspective todismiss presentation layer technologies an their impacts.  I mean for deeper tier technologist that architect communications and security protocols, the presentation layer is just another client.  Google Wave is communications infrastructure &#8211;  outside the scope of Adobe&#8217;s core competency &#8211; the presentation layer.  But to dismss Adobe&#8217;s successes in transforming the web&#8217;s presentation layer or how people work would be harsh.  That said, I will concede that adobe&#8217;s successes were probably not based initially on BHAGs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pelle</title>
		<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/comment-page-1/#comment-110792</link>
		<dc:creator>Pelle</dc:creator>
		<pubDate>Sat, 03 Oct 2009 14:11:55 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1733#comment-110792</guid>
		<description><![CDATA[Just a little funny sidenote - Adobe actually did launch &quot;Wave&quot; around a month after Google did - it&#039;s just that it&#039;s a different Wave - but still, &quot;Adobe Wave&quot; exists: http://labs.adobe.com/technologies/wave/]]></description>
		<content:encoded><![CDATA[<p>Just a little funny sidenote &#8211; Adobe actually did launch &#8220;Wave&#8221; around a month after Google did &#8211; it&#8217;s just that it&#8217;s a different Wave &#8211; but still, &#8220;Adobe Wave&#8221; exists: <a href="http://labs.adobe.com/technologies/wave/" rel="nofollow">http://labs.adobe.com/technologies/wave/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/comment-page-1/#comment-110764</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Sat, 03 Oct 2009 04:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1733#comment-110764</guid>
		<description><![CDATA[There&#039;s just something about Google. The way they can just lay out something new like that, over and over, in completely different parts of the internet ecosystem.

It&#039;s amazing, really.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s just something about Google. The way they can just lay out something new like that, over and over, in completely different parts of the internet ecosystem.</p>
<p>It&#8217;s amazing, really.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://factoryjoe.com/blog/2009/10/02/on-brand-consistency-and-bhags/comment-page-1/#comment-110729</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 02 Oct 2009 21:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1733#comment-110729</guid>
		<description><![CDATA[Great article.  You nailed it in terms of this not being Adobe&#039;s DNA.  And to me, Adobe *still* doesn&#039;t fully get the web and what to do there (one of the main reasons I left).  I think that is intertwined with that DNA, and with the tools and things they focus on.  It is also to some degree not fair, given that they tend to build &quot;tools&quot;, not say &quot;services&quot;.  Sure, they have a few services, but most people would be hard pressed to name even one I think.  So it&#039;s not really comparable to compare building something with AIR or Flash to an actual end user solution.

Ryan&#039;s beef that all this could have been done 5 years ago with Flash and such is true, but at the same note, it didn&#039;t get done.  I would say that is partly Adobe&#039;s fault in that they weren&#039;t able to show what Flex, AIR, etc. could do in a convincing enough way to get the visionary folks to use it, but it&#039;s also that there is a complicated overhead, not just with technology but with licensing, politics/corporate-ness, and all that that goes along with it.

Anyway, interesting stuff all around.]]></description>
		<content:encoded><![CDATA[<p>Great article.  You nailed it in terms of this not being Adobe&#8217;s DNA.  And to me, Adobe *still* doesn&#8217;t fully get the web and what to do there (one of the main reasons I left).  I think that is intertwined with that DNA, and with the tools and things they focus on.  It is also to some degree not fair, given that they tend to build &#8220;tools&#8221;, not say &#8220;services&#8221;.  Sure, they have a few services, but most people would be hard pressed to name even one I think.  So it&#8217;s not really comparable to compare building something with AIR or Flash to an actual end user solution.</p>
<p>Ryan&#8217;s beef that all this could have been done 5 years ago with Flash and such is true, but at the same note, it didn&#8217;t get done.  I would say that is partly Adobe&#8217;s fault in that they weren&#8217;t able to show what Flex, AIR, etc. could do in a convincing enough way to get the visionary folks to use it, but it&#8217;s also that there is a complicated overhead, not just with technology but with licensing, politics/corporate-ness, and all that that goes along with it.</p>
<p>Anyway, interesting stuff all around.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
