<?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: QotD: New Finder in 10.5</title>
	<atom:link href="http://nslog.com/2005/10/22/qotd_new_finder_in_105/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2005/10/22/qotd_new_finder_in_105</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<lastBuildDate>Wed, 23 May 2012 23:05:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Geoff</title>
		<link>http://nslog.com/2005/10/22/qotd_new_finder_in_105#comment-17168</link>
		<dc:creator>Geoff</dc:creator>
		<pubDate>Mon, 24 Oct 2005 14:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/22/qotd_new_finder_in_105/#comment-17168</guid>
		<description>As a long time CLI freak I was never a fan of Windows Explorer.  After making the switch to OSX in 2004 I never really had a problem getting used to Finder.  I like it, even.  Yes, yes, I can see that it definitely could use some major improvements in responsiveness along with major other obvious additions-- but  as it is I use Finder where I never could stand using Explorer.
</description>
		<content:encoded><![CDATA[<p>As a long time CLI freak I was never a fan of Windows Explorer.  After making the switch to OSX in 2004 I never really had a problem getting used to Finder.  I like it, even.  Yes, yes, I can see that it definitely could use some major improvements in responsiveness along with major other obvious additions-- but  as it is I use Finder where I never could stand using Explorer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud Landry</title>
		<link>http://nslog.com/2005/10/22/qotd_new_finder_in_105#comment-17167</link>
		<dc:creator>Bud Landry</dc:creator>
		<pubDate>Sun, 23 Oct 2005 16:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/22/qotd_new_finder_in_105/#comment-17167</guid>
		<description>I think something more evolutionary than revolutionary is in store; some of the rumor sites treat it in a chicken little sky is falling way.  It will probably just provide an easier way to add metadata at most, and be very similar to what is already is available between iTunes and Spotlight interfaces.  It will make more habits than it will break.  (look at all the classic habits that were pulled back into OS X, although some user notions probably needed to change).</description>
		<content:encoded><![CDATA[<p>I think something more evolutionary than revolutionary is in store; some of the rumor sites treat it in a chicken little sky is falling way.  It will probably just provide an easier way to add metadata at most, and be very similar to what is already is available between iTunes and Spotlight interfaces.  It will make more habits than it will break.  (look at all the classic habits that were pulled back into OS X, although some user notions probably needed to change).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesper</title>
		<link>http://nslog.com/2005/10/22/qotd_new_finder_in_105#comment-17166</link>
		<dc:creator>Jesper</dc:creator>
		<pubDate>Sun, 23 Oct 2005 13:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/22/qotd_new_finder_in_105/#comment-17166</guid>
		<description>I fully expect the Finder in Leopard to be slicker, faster and make Julienne Fries.

I&#039;m a programmer. I know that it might involve more/less threads, or a redesign or reworking of the architecture. I also know that if it were to be rewritten in Cocoa, chunks of it might actually be *slower*, since most of the underlying file system calls are made in pure C, and Cocoa design tends to end up wrapping things in classes and methods. (However, this might be a totally wrong thing to say, since those intermediary classes might be optimized out.)

Like Wil Shipley said on the Intel switch: &quot;As long as Apple picks the fastest chips, they could be tortilla chips for all we care.&quot; and similarly, at the end of the day, I couldn&#039;t care less what they end up using as long as it turns out to be better. (And if it&#039;s not better, that&#039;s not because of Carbon or Cocoa but because of misplaced priorities.)</description>
		<content:encoded><![CDATA[<p>I fully expect the Finder in Leopard to be slicker, faster and make Julienne Fries.</p>
<p>I'm a programmer. I know that it might involve more/less threads, or a redesign or reworking of the architecture. I also know that if it were to be rewritten in Cocoa, chunks of it might actually be *slower*, since most of the underlying file system calls are made in pure C, and Cocoa design tends to end up wrapping things in classes and methods. (However, this might be a totally wrong thing to say, since those intermediary classes might be optimized out.)</p>
<p>Like Wil Shipley said on the Intel switch: "As long as Apple picks the fastest chips, they could be tortilla chips for all we care." and similarly, at the end of the day, I couldn't care less what they end up using as long as it turns out to be better. (And if it's not better, that's not because of Carbon or Cocoa but because of misplaced priorities.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

