<?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: Bam! MacBook Pro Core 2 Duo Arrives!</title>
	<atom:link href="http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/</link>
	<description>Everything You Ever Wanted Us To Tell You About Darn Near Anything</description>
	<lastBuildDate>Mon, 14 Sep 2009 22:00:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: bukweet</title>
		<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/comment-page-1/#comment-20</link>
		<dc:creator>bukweet</dc:creator>
		<pubDate>Wed, 25 Oct 2006 21:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwethink.com/?p=22#comment-20</guid>
		<description>You *may* see a benefit, or you may not.
A disadvantage of 64-bit architectures is that, relative to 32-bit architectures, the same data occupies slightly more space in memory (due to swollen pointers and possibly other types and alignment padding). This increases the memory requirements of a given process and can have implications for efficient processor cache utilization.

But, at the present, all of this may be academic. As mentioned, pumping up the ram in a laptop is currently very costly. Also, most commercial software is currently built as 32-bit code, not 64-bit code. These factors will undoubtedly change in the future, but for the present, beware the &quot;64-bit hype&quot; reality distortion field.</description>
		<content:encoded><![CDATA[<p>You *may* see a benefit, or you may not.<br />
A disadvantage of 64-bit architectures is that, relative to 32-bit architectures, the same data occupies slightly more space in memory (due to swollen pointers and possibly other types and alignment padding). This increases the memory requirements of a given process and can have implications for efficient processor cache utilization.</p>
<p>But, at the present, all of this may be academic. As mentioned, pumping up the ram in a laptop is currently very costly. Also, most commercial software is currently built as 32-bit code, not 64-bit code. These factors will undoubtedly change in the future, but for the present, beware the &#8220;64-bit hype&#8221; reality distortion field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/comment-page-1/#comment-18</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Wed, 25 Oct 2006 14:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwethink.com/?p=22#comment-18</guid>
		<description>x86-64 code is generally faster than x86-32 code because more registers become available when running in 64 bit mode.  The memory controller on the MBP motherboard only allows 3GB of ram max, but it would be extremely pricey to put more than 4GB in a laptop right now anyway.  Because of the register issue, though, you&#039;ll still see benefit from using a 64-bit CPU even with only 2 GB of ram.</description>
		<content:encoded><![CDATA[<p>x86-64 code is generally faster than x86-32 code because more registers become available when running in 64 bit mode.  The memory controller on the MBP motherboard only allows 3GB of ram max, but it would be extremely pricey to put more than 4GB in a laptop right now anyway.  Because of the register issue, though, you&#8217;ll still see benefit from using a 64-bit CPU even with only 2 GB of ram.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bukweet</title>
		<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/comment-page-1/#comment-17</link>
		<dc:creator>bukweet</dc:creator>
		<pubDate>Tue, 24 Oct 2006 17:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwethink.com/?p=22#comment-17</guid>
		<description>While the Duo 2 is a 64-bit cpu, its supporting chipset (Napa) is 32-bit, therefore the Duo 2 runs as a 32-bit cpu. The Duo 2 won&#039;t open up to 64-bits until April 2007 with the release of the Santa Rosa chipset.

But ummm is correct:  apps will have to be re-written to take advantage of the 64-bit capability.

While 64-bit architectures indisputably make working with huge data sets in applications such as digital video, scientific computing, and large databases easier, there has been considerable debate as to whether they or their 32-bit compatibility modes will be faster than comparably-priced 32-bit systems for other tasks.

Check out:
http://en.wikipedia.org/wiki/64_bit#32_vs_64_bit</description>
		<content:encoded><![CDATA[<p>While the Duo 2 is a 64-bit cpu, its supporting chipset (Napa) is 32-bit, therefore the Duo 2 runs as a 32-bit cpu. The Duo 2 won&#8217;t open up to 64-bits until April 2007 with the release of the Santa Rosa chipset.</p>
<p>But ummm is correct:  apps will have to be re-written to take advantage of the 64-bit capability.</p>
<p>While 64-bit architectures indisputably make working with huge data sets in applications such as digital video, scientific computing, and large databases easier, there has been considerable debate as to whether they or their 32-bit compatibility modes will be faster than comparably-priced 32-bit systems for other tasks.</p>
<p>Check out:<br />
<a href="http://en.wikipedia.org/wiki/64_bit#32_vs_64_bit" rel="nofollow">http://en.wikipedia.org/wiki/64_bit#32_vs_64_bit</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ummm</title>
		<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/comment-page-1/#comment-16</link>
		<dc:creator>ummm</dc:creator>
		<pubDate>Tue, 24 Oct 2006 16:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwethink.com/?p=22#comment-16</guid>
		<description>It&#039;s already 64 bit compatible(with OSX). You&#039;re not talking Windows or AMD. Besides...how many apps take advantage of it yet?</description>
		<content:encoded><![CDATA[<p>It&#8217;s already 64 bit compatible(with OSX). You&#8217;re not talking Windows or AMD. Besides&#8230;how many apps take advantage of it yet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: speed seeker</title>
		<link>http://www.whatwethink.com/2006/10/24/bam-macbook-pro-core-2-duo-arrives/comment-page-1/#comment-15</link>
		<dc:creator>speed seeker</dc:creator>
		<pubDate>Tue, 24 Oct 2006 15:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatwethink.com/?p=22#comment-15</guid>
		<description>WHY has no one noticed that this is not a 64 bit upgrade? Useless in the next operating system upgrade 10.5. Bacically obsolete out off the box!!!</description>
		<content:encoded><![CDATA[<p>WHY has no one noticed that this is not a 64 bit upgrade? Useless in the next operating system upgrade 10.5. Bacically obsolete out off the box!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

