<?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: Silent updates: Good, Bad, or Safe?</title>
	<atom:link href="http://almaer.com/blog/silent-updates-good-bad-or-safe/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/silent-updates-good-bad-or-safe</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Tue, 03 Jan 2012 22:08:49 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wendy Ragiste</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39353</link>
		<dc:creator>Wendy Ragiste</dc:creator>
		<pubDate>Wed, 06 Aug 2008 21:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39353</guid>
		<description>Solution - everything works perfectly first time, is never hacked and never becomes obsolete. Simple, eh?</description>
		<content:encoded><![CDATA[<p>Solution &#8211; everything works perfectly first time, is never hacked and never becomes obsolete. Simple, eh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Meyer</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39335</link>
		<dc:creator>Justin Meyer</dc:creator>
		<pubDate>Sat, 02 Aug 2008 15:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39335</guid>
		<description>I think the Browser has taught us that automatic upgrades are necessary.  Imagine if IE 6 was automatically upgraded by IE 7.  

There will always be people who want to turn off updates, visit websites with JavaScript turned off, etc.  However, these people are typically more technical to begin with.  

I think it is the developers responsibility to act as a strong parent for the 95% of people who click &quot;OK&quot; without ever reading what the message says.</description>
		<content:encoded><![CDATA[<p>I think the Browser has taught us that automatic upgrades are necessary.  Imagine if IE 6 was automatically upgraded by IE 7.  </p>
<p>There will always be people who want to turn off updates, visit websites with JavaScript turned off, etc.  However, these people are typically more technical to begin with.  </p>
<p>I think it is the developers responsibility to act as a strong parent for the 95% of people who click &#8220;OK&#8221; without ever reading what the message says.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dion</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39334</link>
		<dc:creator>dion</dc:creator>
		<pubDate>Sat, 02 Aug 2008 02:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39334</guid>
		<description>Thanks for the comments guys. I think that the browser has taught us that automatic upgrades are OK. However, when there are big changes, you still see responsible websites letting you take a sneak peak (e.g. the new Yahoo! Mail, the new Facebook, etc).

Luckily, to try different versions, it can be as simple as trying a new URL and setting cookies.

So, it seems to come down to minor vs. major changes. For minor ones, I want the developers to make the change.

Imagine if you were on a website that had a XSS error and the developer couldn&#039;t change it, and instead the user was asked &quot;are you sure you want to go to a new webpage?&quot;</description>
		<content:encoded><![CDATA[<p>Thanks for the comments guys. I think that the browser has taught us that automatic upgrades are OK. However, when there are big changes, you still see responsible websites letting you take a sneak peak (e.g. the new Yahoo! Mail, the new Facebook, etc).</p>
<p>Luckily, to try different versions, it can be as simple as trying a new URL and setting cookies.</p>
<p>So, it seems to come down to minor vs. major changes. For minor ones, I want the developers to make the change.</p>
<p>Imagine if you were on a website that had a XSS error and the developer couldn&#8217;t change it, and instead the user was asked &#8220;are you sure you want to go to a new webpage?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Lightbody</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39332</link>
		<dc:creator>Patrick Lightbody</dc:creator>
		<pubDate>Fri, 01 Aug 2008 18:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39332</guid>
		<description>Silent upgrades are my ideal choice for sure. I really don&#039;t care unless it&#039;s a BIG change. I&#039;m definitely not worried about security. I&#039;m not even worried about instability, since the developer will likely know to roll out a subsequent update to fix any bugs from the last update, so it should just work itself out without me even noticing it.

At Jive I insisted they spend time on an automatic upgrade process. It&#039;s not automatic, but it&#039;s still way better than most enterprise software. They wrote a blog entry about it a while back &lt;a href=&quot;http://www.jivesoftware.com/community/blogs/clearspace/2007/07/19/the-benefits-of-an-upgrade-framework&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; and InfoQ wrote one on the topic &lt;a href=&quot;http://www.infoq.com/news/upgrade-frameworks&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. It&#039;s kind of surprising how few companies &quot;get it&quot; when it comes to making users lives easier. Even Plaxo has a shitty upgrade experience on the Mac.</description>
		<content:encoded><![CDATA[<p>Silent upgrades are my ideal choice for sure. I really don&#8217;t care unless it&#8217;s a BIG change. I&#8217;m definitely not worried about security. I&#8217;m not even worried about instability, since the developer will likely know to roll out a subsequent update to fix any bugs from the last update, so it should just work itself out without me even noticing it.</p>
<p>At Jive I insisted they spend time on an automatic upgrade process. It&#8217;s not automatic, but it&#8217;s still way better than most enterprise software. They wrote a blog entry about it a while back <a href="http://www.jivesoftware.com/community/blogs/clearspace/2007/07/19/the-benefits-of-an-upgrade-framework" rel="nofollow">here</a> and InfoQ wrote one on the topic <a href="http://www.infoq.com/news/upgrade-frameworks" rel="nofollow">here</a>. It&#8217;s kind of surprising how few companies &#8220;get it&#8221; when it comes to making users lives easier. Even Plaxo has a shitty upgrade experience on the Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vezquex</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39331</link>
		<dc:creator>Vezquex</dc:creator>
		<pubDate>Fri, 01 Aug 2008 17:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39331</guid>
		<description>Not quite, Ross. Browser caches don&#039;t always update.</description>
		<content:encoded><![CDATA[<p>Not quite, Ross. Browser caches don&#8217;t always update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Boucher</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39330</link>
		<dc:creator>Ross Boucher</dc:creator>
		<pubDate>Fri, 01 Aug 2008 17:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39330</guid>
		<description>One advantage of the trend towards web applications is not having to worry about this kind of thing.  The app provider updates for you, whenever they&#039;re ready; everybody immediately gets the new version.  The only potential downside here is something changing that you don&#039;t like -- there&#039;s no going back.</description>
		<content:encoded><![CDATA[<p>One advantage of the trend towards web applications is not having to worry about this kind of thing.  The app provider updates for you, whenever they&#8217;re ready; everybody immediately gets the new version.  The only potential downside here is something changing that you don&#8217;t like &#8212; there&#8217;s no going back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Miller</title>
		<link>http://almaer.com/blog/silent-updates-good-bad-or-safe/comment-page-1#comment-39329</link>
		<dc:creator>Alex Miller</dc:creator>
		<pubDate>Fri, 01 Aug 2008 17:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/silent-updates-good-bad-or-safe#comment-39329</guid>
		<description>AppFresh?  http://metaquark.de/appfresh/</description>
		<content:encoded><![CDATA[<p>AppFresh?  <a href="http://metaquark.de/appfresh/" rel="nofollow">http://metaquark.de/appfresh/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

