<?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: Upgrading Safari on the Mac - Apple Aesthetics collide with Usability</title>
	<atom:link href="http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/</link>
	<description>FileMaker Web Publishing and Consulting Blog</description>
	<pubDate>Tue, 06 Jan 2009 04:17:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Paul Turnbull</title>
		<link>http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-23</link>
		<dc:creator>Paul Turnbull</dc:creator>
		<pubDate>Sun, 16 Sep 2007 16:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-23</guid>
		<description>It has always been the case with OS X that if you move Apple's own applications from their default locations Apple's updaters will not work. It is one of the more irritating offshoots of Apple's control obsession. :)</description>
		<content:encoded><![CDATA[<p>It has always been the case with OS X that if you move Apple&#8217;s own applications from their default locations Apple&#8217;s updaters will not work. It is one of the more irritating offshoots of Apple&#8217;s control obsession. <img src='http://fmwebschool.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary King</title>
		<link>http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-21</link>
		<dc:creator>Gary King</dc:creator>
		<pubDate>Sun, 09 Sep 2007 19:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-21</guid>
		<description>Actually, I would imagine that Safari and iLife are using modified versions of the installer because they both are packages that require that the original application be in the /Applications/ folder and so what they are using are different from what most other applications have. They probably just never bothered to include a specific message for your specific issue; I ran into this problem with iLife in the past.</description>
		<content:encoded><![CDATA[<p>Actually, I would imagine that Safari and iLife are using modified versions of the installer because they both are packages that require that the original application be in the /Applications/ folder and so what they are using are different from what most other applications have. They probably just never bothered to include a specific message for your specific issue; I ran into this problem with iLife in the past.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Petrov</title>
		<link>http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-20</link>
		<dc:creator>Michael Petrov</dc:creator>
		<pubDate>Sun, 09 Sep 2007 16:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-20</guid>
		<description>Beta is not an excuse in this case - after all the Apple standard installer is certainly not in beta and I am sure Safari is not the first product that depends on an older version to be installed. Therefore the engineers not putting enough time in the installer are actually stopping people from working with their beta and finding the bugs within the core software.</description>
		<content:encoded><![CDATA[<p>Beta is not an excuse in this case - after all the Apple standard installer is certainly not in beta and I am sure Safari is not the first product that depends on an older version to be installed. Therefore the engineers not putting enough time in the installer are actually stopping people from working with their beta and finding the bugs within the core software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary King</title>
		<link>http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-19</link>
		<dc:creator>Gary King</dc:creator>
		<pubDate>Sat, 08 Sep 2007 02:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://fmwebschool.com/blog/2007/09/06/upgrading-safari-on-the-mac-apple-aesthetics-collide-with-usability/#comment-19</guid>
		<description>This is why it's still in beta ;)</description>
		<content:encoded><![CDATA[<p>This is why it&#8217;s still in beta <img src='http://fmwebschool.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
