<?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: Safari 4: Three Steps Forward, One Step Back</title>
	<atom:link href="http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/</link>
	<description>Bridging the Apple Community and Keeping Tabs on the Rumor Mill.</description>
	<lastBuildDate>Wed, 17 Mar 2010 21:00:40 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Wheadon</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3244</link>
		<dc:creator>Mark Wheadon</dc:creator>
		<pubDate>Fri, 13 Mar 2009 09:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3244</guid>
		<description>If, like me, you find you need to back out of Safari 4 beta and go back to 3.2.1, then here&#039;s how:

http://www.markwheadon.com/blog/2009/02/how-to-back-out-of-safari-4beta/

Cheers,

Mark</description>
		<content:encoded><![CDATA[<p>If, like me, you find you need to back out of Safari 4 beta and go back to 3.2.1, then here&#8217;s how:</p>
<p><a href="http://www.markwheadon.com/blog/2009/02/how-to-back-out-of-safari-4beta/" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.markwheadon.com/blog/2009/02/how-to-back-out-of-safari-4beta/?referer=');">http://www.markwheadon.com/blog/2009/02/how-to-back-out-of-safari-4beta/</a></p>
<p>Cheers,</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3213</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Sat, 28 Feb 2009 00:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3213</guid>
		<description>There are a few plugins that I would like to see come to safari 4. I was concerned about not having Firebug as well until i came across the Develop menu which includes something called &quot;Show Web Inspector&quot;. This does pretty much everything firebug does and more.

You have to turn this on in your preferences and it is awesome. Check it out.

The best thing about Safari 4 so far for me has been how snappy web pages load. I am definitely going to give Safari a try for a while.</description>
		<content:encoded><![CDATA[<p>There are a few plugins that I would like to see come to safari 4. I was concerned about not having Firebug as well until i came across the Develop menu which includes something called &#8220;Show Web Inspector&#8221;. This does pretty much everything firebug does and more.</p>
<p>You have to turn this on in your preferences and it is awesome. Check it out.</p>
<p>The best thing about Safari 4 so far for me has been how snappy web pages load. I am definitely going to give Safari a try for a while.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous Coward</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3207</link>
		<dc:creator>Anonymous Coward</dc:creator>
		<pubDate>Wed, 25 Feb 2009 21:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3207</guid>
		<description>Oh man, that was awesome. I just sprayed all over my MBP from my nose. The best part was when Michael said: &quot;I don’t think Apple cares about ‘Safari’ market share at this point. All they are really interested in is making sure WebKit continues to gain adoption. This insures the proliferation of web standards, which is, in the end, what Apple is really pushing.&quot;

As if Apple cares about ANYTHING besides market share and profitability. Don&#039;t delude yourself into thinking they are more concerned about pushing Webkit or OSS or any other holy-cause-of-the-week for its own sake. THEY ARE A PUBLICLY TRADED COMPANY. The bottom line is the ONLY line. Wise up.</description>
		<content:encoded><![CDATA[<p>Oh man, that was awesome. I just sprayed all over my MBP from my nose. The best part was when Michael said: &#8220;I don’t think Apple cares about ‘Safari’ market share at this point. All they are really interested in is making sure WebKit continues to gain adoption. This insures the proliferation of web standards, which is, in the end, what Apple is really pushing.&#8221;</p>
<p>As if Apple cares about ANYTHING besides market share and profitability. Don&#8217;t delude yourself into thinking they are more concerned about pushing Webkit or OSS or any other holy-cause-of-the-week for its own sake. THEY ARE A PUBLICLY TRADED COMPANY. The bottom line is the ONLY line. Wise up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aviv</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3206</link>
		<dc:creator>Aviv</dc:creator>
		<pubDate>Wed, 25 Feb 2009 18:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3206</guid>
		<description>@Michael: 100% agreed. The blue loading bar was driving me nuts, didn&#039;t mind the tabs on top so much so I left them. But, I turned the blue-loading bar back on. Major oversight on Apple&#039;s part.</description>
		<content:encoded><![CDATA[<p>@Michael: 100% agreed. The blue loading bar was driving me nuts, didn&#8217;t mind the tabs on top so much so I left them. But, I turned the blue-loading bar back on. Major oversight on Apple&#8217;s part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3203</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 25 Feb 2009 17:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3203</guid>
		<description>Simplicity is what makes Safari the browser it is. Plug-ins be damned. I don&#039;t think Apple cares about &#039;Safari&#039; market share at this point. All they are really interested in is making sure WebKit continues to gain adoption. This insures the proliferation of web standards, which is, in the end, what Apple is really pushing.

Personally don&#039;t care for any of the new user-oriented visual features in Safari 4 and I thank god Apple left them as hidden switchable preferences. The performance enhancements and search functions however, are very much welcomed.</description>
		<content:encoded><![CDATA[<p>Simplicity is what makes Safari the browser it is. Plug-ins be damned. I don&#8217;t think Apple cares about &#8216;Safari&#8217; market share at this point. All they are really interested in is making sure WebKit continues to gain adoption. This insures the proliferation of web standards, which is, in the end, what Apple is really pushing.</p>
<p>Personally don&#8217;t care for any of the new user-oriented visual features in Safari 4 and I thank god Apple left them as hidden switchable preferences. The performance enhancements and search functions however, are very much welcomed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aviv</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3200</link>
		<dc:creator>Aviv</dc:creator>
		<pubDate>Wed, 25 Feb 2009 03:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3200</guid>
		<description>@hmurchison: True. But I think Opera made some mistakes in the past when it was a commercial product and for the most part, Chrome made the &quot;tabs and the bookmarks&quot; publicly known... At least recently. But, you&#039;re right, Opera had it first.</description>
		<content:encoded><![CDATA[<p>@hmurchison: True. But I think Opera made some mistakes in the past when it was a commercial product and for the most part, Chrome made the &#8220;tabs and the bookmarks&#8221; publicly known&#8230; At least recently. But, you&#8217;re right, Opera had it first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hmurchison</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3199</link>
		<dc:creator>hmurchison</dc:creator>
		<pubDate>Wed, 25 Feb 2009 02:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3199</guid>
		<description>Actually Apple did not rip the idea for Top Sites from Google.  Opera had a thumbnail landing page for your most visited sites way before Google Chrome was even known about.</description>
		<content:encoded><![CDATA[<p>Actually Apple did not rip the idea for Top Sites from Google.  Opera had a thumbnail landing page for your most visited sites way before Google Chrome was even known about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aviv</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3198</link>
		<dc:creator>Aviv</dc:creator>
		<pubDate>Tue, 24 Feb 2009 23:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3198</guid>
		<description>I also am not particularly keen on the fact that the entire LOADING BAR was removed in favor of a loading.gif on the right of the URL. Talk about a split second moment confusion during what should be a natural interaction with a tactile button. I think if Apple wants to have as little &quot;options&quot; as they can, then the entire blue loading bar needs to come back within the URL bar.</description>
		<content:encoded><![CDATA[<p>I also am not particularly keen on the fact that the entire LOADING BAR was removed in favor of a loading.gif on the right of the URL. Talk about a split second moment confusion during what should be a natural interaction with a tactile button. I think if Apple wants to have as little &#8220;options&#8221; as they can, then the entire blue loading bar needs to come back within the URL bar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aviv</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3197</link>
		<dc:creator>Aviv</dc:creator>
		<pubDate>Tue, 24 Feb 2009 23:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3197</guid>
		<description>@Scott: Well, I take your opinions into account, however, I think you&#039;re wrong when you say that even if Safari offered me the plugins, I would use both browsers. That&#039;s not correct... You see, Firefox is also very shaky on OS X. And the UI bonks out periodically, the tabs take a while to load up, and the rendering engine is just MUCH slower than what&#039;s now being called &quot;Nitro.&quot;

In fact, there&#039;s a tutorial here on how drastically ( http://snipurl.com/cl38h ) speed up Firefox, but it still lags behind Safari in terms of speed. 

The bottom line is that Firefox&#039;s stability and compatibility with web-apps is greater than Safari&#039;s. For example, go into the editor in any Wordpress admin area and try and crop/resize an image in the visual editor, now go try the same thing in Safari.... This is a small example of how Safari&#039;s quirks can throw a wrench into any deep web application productivity or browsing session.

I will give it to FF for their new UI which tries to be more consistent across platforms. However, the bottom line remains that Apple needs to open up a bit here. It&#039;s not just that they preach open web standards, this is a WEB BROWSER, they need to be setting an example, not running it like a niche IM application.</description>
		<content:encoded><![CDATA[<p>@Scott: Well, I take your opinions into account, however, I think you&#8217;re wrong when you say that even if Safari offered me the plugins, I would use both browsers. That&#8217;s not correct&#8230; You see, Firefox is also very shaky on OS X. And the UI bonks out periodically, the tabs take a while to load up, and the rendering engine is just MUCH slower than what&#8217;s now being called &#8220;Nitro.&#8221;</p>
<p>In fact, there&#8217;s a tutorial here on how drastically ( <a href="http://snipurl.com/cl38h" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/snipurl.com/cl38h?referer=');">http://snipurl.com/cl38h</a> ) speed up Firefox, but it still lags behind Safari in terms of speed. </p>
<p>The bottom line is that Firefox&#8217;s stability and compatibility with web-apps is greater than Safari&#8217;s. For example, go into the editor in any Wordpress admin area and try and crop/resize an image in the visual editor, now go try the same thing in Safari&#8230;. This is a small example of how Safari&#8217;s quirks can throw a wrench into any deep web application productivity or browsing session.</p>
<p>I will give it to FF for their new UI which tries to be more consistent across platforms. However, the bottom line remains that Apple needs to open up a bit here. It&#8217;s not just that they preach open web standards, this is a WEB BROWSER, they need to be setting an example, not running it like a niche IM application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Paterson</title>
		<link>http://www.macblogz.com/2009/02/24/safari-4-three-steps-forward-one-step-back/comment-page-1/#comment-3196</link>
		<dc:creator>Scott Paterson</dc:creator>
		<pubDate>Tue, 24 Feb 2009 23:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.macblogz.com/?p=1370#comment-3196</guid>
		<description>Accept most of the points you raise here, however I think the argument about lack of plugin architecture for Safari is a moot point for 90%+ of Mac users. Yes web designers and power users will have need for the widgets that can be added to browsers like Firefox but in practice most users will be happily oblivious of the use of these tools. As usual Apple are out to target the majority and not the minority, they want the experience to be seamless, reliable and consistent for all. Not allowing users to plugin potentially flaky third party addons is one way of attempting to ensure this.

If you need plugins as you say continue to run both browsers ( in reality you would probably do this even IF Safari allowed them ).</description>
		<content:encoded><![CDATA[<p>Accept most of the points you raise here, however I think the argument about lack of plugin architecture for Safari is a moot point for 90%+ of Mac users. Yes web designers and power users will have need for the widgets that can be added to browsers like Firefox but in practice most users will be happily oblivious of the use of these tools. As usual Apple are out to target the majority and not the minority, they want the experience to be seamless, reliable and consistent for all. Not allowing users to plugin potentially flaky third party addons is one way of attempting to ensure this.</p>
<p>If you need plugins as you say continue to run both browsers ( in reality you would probably do this even IF Safari allowed them ).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
