<?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: Intel</title>
	<atom:link href="http://nslog.com/2005/06/08/qotd_intel/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2005/06/08/qotd_intel</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: World Wide Wood</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15731</link>
		<dc:creator>World Wide Wood</dc:creator>
		<pubDate>Fri, 10 Jun 2005 15:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15731</guid>
		<description>&lt;strong&gt;Mac on Intel: Roundup and Reactions&lt;/strong&gt;

In case you&#039;ve been living under a rock for the past 24 hours, Apple has announced that they will be...
</description>
		<content:encoded><![CDATA[<p><strong>Mac on Intel: Roundup and Reactions</strong></p>
<p>In case you've been living under a rock for the past 24 hours, Apple has announced that they will be...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud Landry</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15730</link>
		<dc:creator>Bud Landry</dc:creator>
		<pubDate>Thu, 09 Jun 2005 19:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15730</guid>
		<description>The Xeon is probably on a dead branch of the Intel growth tree.  It is not Intel&#039;s future for 64 bit or multiple core, and certainly has its own history of struggles.



The P4 of the development kit is not the intel mac of the future, it is merely to assure clean stable code.  You might find its relatives more directly in a Mac Mini.</description>
		<content:encoded><![CDATA[<p>The Xeon is probably on a dead branch of the Intel growth tree.  It is not Intel's future for 64 bit or multiple core, and certainly has its own history of struggles.</p>
<p>The P4 of the development kit is not the intel mac of the future, it is merely to assure clean stable code.  You might find its relatives more directly in a Mac Mini.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrinkOnlyScotch</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15729</link>
		<dc:creator>DrinkOnlyScotch</dc:creator>
		<pubDate>Thu, 09 Jun 2005 18:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15729</guid>
		<description>I&#039;m quite excited about getting my hands on a wicked-fast Powerbook, I&#039;ll have to admit. But I am quite concerned about the PowerMac which, in truth, is more important to me and how productive I am.



I&#039;m curious why there doesn&#039;t seem to be much discussion regarding the 64-bit XEON MP, which seems to be much more comparable to the G5 than the P4. Apple has really marketing the PowerMac as a workstation since the G5 and OS X and I think the P4 is anything but a workstation-class processor, regardless of what HP and Dell think.</description>
		<content:encoded><![CDATA[<p>I'm quite excited about getting my hands on a wicked-fast Powerbook, I'll have to admit. But I am quite concerned about the PowerMac which, in truth, is more important to me and how productive I am.</p>
<p>I'm curious why there doesn't seem to be much discussion regarding the 64-bit XEON MP, which seems to be much more comparable to the G5 than the P4. Apple has really marketing the PowerMac as a workstation since the G5 and OS X and I think the P4 is anything but a workstation-class processor, regardless of what HP and Dell think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anunnaki</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15728</link>
		<dc:creator>Anunnaki</dc:creator>
		<pubDate>Thu, 09 Jun 2005 15:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15728</guid>
		<description>I am hurt to the bones over the emotional facts et al ..



But I have spent considerable time studying the upcoming Yonah and Conroe Chips, and what the Intel Roadmap has even further ahead.



Steve said, its was something he saw in intels future (looking at roadmaps together with pat?), so, if this and the lack of a suitable g5 powerbook has gotten him into this decision, i can understand.



Apple has been struggeling for CPUs for so long I almost forgot when they actually had NOT to ... 



I like Yonah I have to admit. Its not a really exceptionally geeky CPU (all really cool CPUs are dead), but its a good one.



We are NOT talking NetBurst architecture here in terms of Apple&#039;s move!</description>
		<content:encoded><![CDATA[<p>I am hurt to the bones over the emotional facts et al ..</p>
<p>But I have spent considerable time studying the upcoming Yonah and Conroe Chips, and what the Intel Roadmap has even further ahead.</p>
<p>Steve said, its was something he saw in intels future (looking at roadmaps together with pat?), so, if this and the lack of a suitable g5 powerbook has gotten him into this decision, i can understand.</p>
<p>Apple has been struggeling for CPUs for so long I almost forgot when they actually had NOT to ... </p>
<p>I like Yonah I have to admit. Its not a really exceptionally geeky CPU (all really cool CPUs are dead), but its a good one.</p>
<p>We are NOT talking NetBurst architecture here in terms of Apple's move!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Linville</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15727</link>
		<dc:creator>Aaron Linville</dc:creator>
		<pubDate>Thu, 09 Jun 2005 03:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15727</guid>
		<description>Initially I was a bit bummed about it. PPC instructions are more elegant than x86 (I don&#039;t think anyone will disagree), but x86 chips have a roadmap that has faster machines. After my initial shock, I have to say I am fine with the switch (though, I still feel a bit dirty for saying that, hopefully that&#039;ll pass). I went through the 68k to PPC migration and it was utterly painless. I&#039;m confident that the PPC to x86 migration will go just as well, if not better. Hopefully I can pick up some Dual G5s in the bargain bin. :-)



Oh, one thing I won&#039;t like is little endian. I hate debugging little endian memory.</description>
		<content:encoded><![CDATA[<p>Initially I was a bit bummed about it. PPC instructions are more elegant than x86 (I don't think anyone will disagree), but x86 chips have a roadmap that has faster machines. After my initial shock, I have to say I am fine with the switch (though, I still feel a bit dirty for saying that, hopefully that'll pass). I went through the 68k to PPC migration and it was utterly painless. I'm confident that the PPC to x86 migration will go just as well, if not better. Hopefully I can pick up some Dual G5s in the bargain bin. <img src='http://nslog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Oh, one thing I won't like is little endian. I hate debugging little endian memory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MrO</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15726</link>
		<dc:creator>MrO</dc:creator>
		<pubDate>Thu, 09 Jun 2005 01:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15726</guid>
		<description>Oops - bad karma for a double post here, but to address Zoefsnoep&#039;s question:



&lt;blockquote&gt;So when Intel reveals their next Pentium next year and Apple shoehorns it in a Mac, we will have a Mac that is &#039;hopefully&#039; as fast as a Dell running Windows using the same chip.&lt;/blockquote&gt;



I&#039;m quite confident that you&#039;ll end up with a Mac that&#039;s significantly faster than a Dell running on the same chip. Windows has a lot of cruft, their architecture and API&#039;s all contribute to a much slower software experience than could be had on the hardware it&#039;s all running on.



Back in ancient history during the Yellow Box days, when we ported our Cocoa (OPENSTEP) app over to Windows, the whole office was just floored when we found that our app, using a lot of the architectural goodness you&#039;ll see in OS X for Intel including double-buffered graphics and a &quot;window server&quot; absolutely demolished the native Windows equivalent in speed.



It wasn&#039;t just 50% faster. It was more like 5-6 times faster. Now, that sort of architectural difference might start to be minimized with Longhorn and it&#039;s Avalon windowing environment, but Windows developers are going to be spending years moving over to the new Windows stuff and the old cruft will persist.



I&#039;m going to go out on a limb here and state that a lot of the speed you see in Mac OS today has been bought through the toil of Apple first in optimizing its own code (think of the general speed ups over OSX releases) for what has always been a more performance-constrained PPC environment, and by developers leveraging that toil and adding their own :) 



One thing that we noticed back in the day when we moved from 68k to Intel, was that Intel&#039;s integer performance (versus 68k&#039;s and PPC&#039;s great floating point performance) is used to great effect in making the OS run fast. That work that Apple has done over the years to make each iteration of OS X faster than the previous one will very likely show up on the Intel side and act very favorably for the performance of even the first shipping Mac OS X86 PC. The fact that Apple has been quietly working on this all in parallel to OS X development is good reason to expect big things when the switch happens.</description>
		<content:encoded><![CDATA[<p>Oops - bad karma for a double post here, but to address Zoefsnoep's question:</p>
<blockquote><p>So when Intel reveals their next Pentium next year and Apple shoehorns it in a Mac, we will have a Mac that is 'hopefully' as fast as a Dell running Windows using the same chip.</p>
</blockquote>
<p>I'm quite confident that you'll end up with a Mac that's significantly faster than a Dell running on the same chip. Windows has a lot of cruft, their architecture and API's all contribute to a much slower software experience than could be had on the hardware it's all running on.</p>
<p>Back in ancient history during the Yellow Box days, when we ported our Cocoa (OPENSTEP) app over to Windows, the whole office was just floored when we found that our app, using a lot of the architectural goodness you'll see in OS X for Intel including double-buffered graphics and a "window server" absolutely demolished the native Windows equivalent in speed.</p>
<p>It wasn't just 50% faster. It was more like 5-6 times faster. Now, that sort of architectural difference might start to be minimized with Longhorn and it's Avalon windowing environment, but Windows developers are going to be spending years moving over to the new Windows stuff and the old cruft will persist.</p>
<p>I'm going to go out on a limb here and state that a lot of the speed you see in Mac OS today has been bought through the toil of Apple first in optimizing its own code (think of the general speed ups over OSX releases) for what has always been a more performance-constrained PPC environment, and by developers leveraging that toil and adding their own <img src='http://nslog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>One thing that we noticed back in the day when we moved from 68k to Intel, was that Intel's integer performance (versus 68k's and PPC's great floating point performance) is used to great effect in making the OS run fast. That work that Apple has done over the years to make each iteration of OS X faster than the previous one will very likely show up on the Intel side and act very favorably for the performance of even the first shipping Mac OS X86 PC. The fact that Apple has been quietly working on this all in parallel to OS X development is good reason to expect big things when the switch happens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MrO</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15725</link>
		<dc:creator>MrO</dc:creator>
		<pubDate>Thu, 09 Jun 2005 01:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15725</guid>
		<description>Daniel: just a minor correction - NeXT OS was available for Moto 68k, Intel X86, Sparc, and HP-PA RISC systems. 4 way compilation of our apps (both custom and commercial) was via checkbox just as with the upcoming Mac OS, and it worked absolutely seamlessly. Being cheap, I never equipped the office with PA-RISC systems, but we released across all 4 and never ran into an issue with any of them - it all compiled the first time, and went through beta and into release without any architecture issues at all.



-M</description>
		<content:encoded><![CDATA[<p>Daniel: just a minor correction - NeXT OS was available for Moto 68k, Intel X86, Sparc, and HP-PA RISC systems. 4 way compilation of our apps (both custom and commercial) was via checkbox just as with the upcoming Mac OS, and it worked absolutely seamlessly. Being cheap, I never equipped the office with PA-RISC systems, but we released across all 4 and never ran into an issue with any of them - it all compiled the first time, and went through beta and into release without any architecture issues at all.</p>
<p>-M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zoefsnoep</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15724</link>
		<dc:creator>Zoefsnoep</dc:creator>
		<pubDate>Wed, 08 Jun 2005 23:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15724</guid>
		<description>I personally don&#039;t quite understand the move...



So when Intel reveals their next Pentium next year and Apple shoehorns it in a Mac, we will have a Mac that is &#039;hopefully&#039; as fast as a Dell running Windows using the same chip. But the Dell will, probably, still be cheaper (industrial design, rest of components, mass production, etc).

So we will end up with a machine, that is, at best, as fast as the fastest Windows PC but more expensive. Better looking of course.



Or, Apple could use the motherboarddesign of some PC manufacturer and try to build Macs really cheap. But we will end up with BIOS (According to Apple&#039;s documentation the IntelMac does not use OpenFirmware...).



Hopefully they will keep the option of running some version of the MacOS on legacy Intel/AMD hardware, and use it in the future.



Or maybe release a yellowbox environment for win32, so developers can deploy their x86 code on another userbase as well.</description>
		<content:encoded><![CDATA[<p>I personally don't quite understand the move...</p>
<p>So when Intel reveals their next Pentium next year and Apple shoehorns it in a Mac, we will have a Mac that is 'hopefully' as fast as a Dell running Windows using the same chip. But the Dell will, probably, still be cheaper (industrial design, rest of components, mass production, etc).</p>
<p>So we will end up with a machine, that is, at best, as fast as the fastest Windows PC but more expensive. Better looking of course.</p>
<p>Or, Apple could use the motherboarddesign of some PC manufacturer and try to build Macs really cheap. But we will end up with BIOS (According to Apple's documentation the IntelMac does not use OpenFirmware...).</p>
<p>Hopefully they will keep the option of running some version of the MacOS on legacy Intel/AMD hardware, and use it in the future.</p>
<p>Or maybe release a yellowbox environment for win32, so developers can deploy their x86 code on another userbase as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralph Scheuer</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15723</link>
		<dc:creator>Ralph Scheuer</dc:creator>
		<pubDate>Wed, 08 Jun 2005 22:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15723</guid>
		<description>@shredstar: have you ever wondered that the exact opposite about PPC vs. Intel has been stated by many MacHeads a gazillion times before? BTW, on a &quot;given the same GHz&quot; basis, I still believe the current G5 lineup leaves the P4 in the dust, bigtime. OTOH, if you are referring to the Centrino vs. the G4, you are right.</description>
		<content:encoded><![CDATA[<p>@shredstar: have you ever wondered that the exact opposite about PPC vs. Intel has been stated by many MacHeads a gazillion times before? BTW, on a "given the same GHz" basis, I still believe the current G5 lineup leaves the P4 in the dust, bigtime. OTOH, if you are referring to the Centrino vs. the G4, you are right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shredstar</title>
		<link>http://nslog.com/2005/06/08/qotd_intel#comment-15722</link>
		<dc:creator>shredstar</dc:creator>
		<pubDate>Wed, 08 Jun 2005 22:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/06/08/qotd_intel/#comment-15722</guid>
		<description>The x86 instruction set truly is horrible, but almost nobody works at the machine-code/assembly level. Apple just can&#039;t compete with Intel&#039;s huge engineering resources devoted to cranking out faster chips.



Of all the things I&#039;ve heard, these seem the most important:

- To do a movie version of itunes, and to support H.264 HDTV format, Apple really needs the CPU power.

- People love Apple for reasons other than the PowerPC instruction set.

- Given the same Ghz, PowerPC is slower than Intel.

- Given the same Ghz, PowerPC is hotter than Intel.

- Given the same Ghz, PowerPC is bigger than Intel.

- Each of these can be addressed, but only by making the product more expensive.



Insofar as the only important thing is what the enduser experiences on his monitor, Steve Jobs made a good decision.   Without switching to Intel, Apple was set to lose the $1000 Apple Laptop vs. $1000 WinTel Laptop competition bigtime.</description>
		<content:encoded><![CDATA[<p>The x86 instruction set truly is horrible, but almost nobody works at the machine-code/assembly level. Apple just can't compete with Intel's huge engineering resources devoted to cranking out faster chips.</p>
<p>Of all the things I've heard, these seem the most important:</p>
<p>- To do a movie version of itunes, and to support H.264 HDTV format, Apple really needs the CPU power.</p>
<p>- People love Apple for reasons other than the PowerPC instruction set.</p>
<p>- Given the same Ghz, PowerPC is slower than Intel.</p>
<p>- Given the same Ghz, PowerPC is hotter than Intel.</p>
<p>- Given the same Ghz, PowerPC is bigger than Intel.</p>
<p>- Each of these can be addressed, but only by making the product more expensive.</p>
<p>Insofar as the only important thing is what the enduser experiences on his monitor, Steve Jobs made a good decision.   Without switching to Intel, Apple was set to lose the $1000 Apple Laptop vs. $1000 WinTel Laptop competition bigtime.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

