<?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: &#8230;.Mac Geeks Are Excited about Leopard</title>
	<atom:link href="http://fourreasonswhy.com/2007/10/26/mac-geeks-are-excited-about-leopard/feed/" rel="self" type="application/rss+xml" />
	<link>http://fourreasonswhy.com/2007/10/26/mac-geeks-are-excited-about-leopard/</link>
	<description>A Blog Focused on Lists</description>
	<pubDate>Thu, 28 Aug 2008 14:34:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Apples&#8217;s - and Microsoft&#8217;s - Big Day : Mark Evans</title>
		<link>http://fourreasonswhy.com/2007/10/26/mac-geeks-are-excited-about-leopard/#comment-310</link>
		<dc:creator>Apples&#8217;s - and Microsoft&#8217;s - Big Day : Mark Evans</dc:creator>
		<pubDate>Fri, 26 Oct 2007 11:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://fourreasonswhy.com/2007/10/26/mac-geeks-are-excited-about-leopard/#comment-310</guid>
		<description>[...] As a relatively new Apple user, I wasn&#8217;t really as cognizant of the marketing bonanza surrounding about Tiger or Panther, although I&#8217;m sure they it was a big deal for Mac users. But with Mac being used by people and Apple the belle of the ball, it&#8217;s easy to see why Leopard is such a big deal. (Note: For a different look at why people are so excited about Leopard, check out Four Reasons Why). [...]</description>
		<content:encoded><![CDATA[<p>[...] As a relatively new Apple user, I wasn&#8217;t really as cognizant of the marketing bonanza surrounding about Tiger or Panther, although I&#8217;m sure they it was a big deal for Mac users. But with Mac being used by people and Apple the belle of the ball, it&#8217;s easy to see why Leopard is such a big deal. (Note: For a different look at why people are so excited about Leopard, check out Four Reasons Why). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
