<?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: Myths of Snow Leopard 2: 32-bit Support</title>
	<atom:link href="http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/</link>
	<description>Daniel Eran Dilger in San Francisco</description>
	<pubDate>Thu, 20 Nov 2008 11:08:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Road to Mac OS X 10.6 Snow Leopard: 64-Bits &#8212; RoughlyDrafted Magazine</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-11847</link>
		<dc:creator>Road to Mac OS X 10.6 Snow Leopard: 64-Bits &#8212; RoughlyDrafted Magazine</dc:creator>
		<pubDate>Sun, 31 Aug 2008 21:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-11847</guid>
		<description>[...] supplied a 64-bit version of libsystem, the system library handling most of its Unix APIs. This followed the LP64 model to allow broad compatibility with 64-bit versions of Linux and commercial Unix. It also delivered a [...]</description>
		<content:encoded><![CDATA[<p>[...] supplied a 64-bit version of libsystem, the system library handling most of its Unix APIs. This followed the LP64 model to allow broad compatibility with 64-bit versions of Linux and commercial Unix. It also delivered a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: metromacs blog &#187; Blog Archive &#187; Road to Mac OS X 10.6 Snow Leopard: 64-Bits</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-11644</link>
		<dc:creator>metromacs blog &#187; Blog Archive &#187; Road to Mac OS X 10.6 Snow Leopard: 64-Bits</dc:creator>
		<pubDate>Thu, 28 Aug 2008 12:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-11644</guid>
		<description>[...] a 64-bit version of libsystem, the system library handling most of its Unix APIs. This&#160;followed the LP64 model&#160;to allow broad compatibility with 64-bit versions of Linux and commercial Unix. It also [...]</description>
		<content:encoded><![CDATA[<p>[...] a 64-bit version of libsystem, the system library handling most of its Unix APIs. This&nbsp;followed the LP64 model&nbsp;to allow broad compatibility with 64-bit versions of Linux and commercial Unix. It also [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ulric</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-10070</link>
		<dc:creator>ulric</dc:creator>
		<pubDate>Fri, 27 Jun 2008 22:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-10070</guid>
		<description>@danieleran
That article on techtarget.com is poorly worded: Wow64 is not an "emulator". It is a 32-bit sub-system that forwards the Win32 API calls to the 64-bit API. The instructions are not emulated and run-time performance is not affected as the word suggests.

There is no mesurable lost in applications speed, whether games or business, which makes sense, since most common applications will be 32-bit for a long time.

Why did Microsoft make a separate 64-bit version Window SKU?  It was to make a clean break with the old driver models and some obsolete API, old shell extensions, etc.  The 64-bit version is more secure and fixes some holes.  It was to do exactly what people are asking them to do: make a clean break with some of the oldest things.  They also dropped all support for DOS and 16-bit windows application in Windows 64-bit.

It is precisly part of the plan that people will be gradually buying new machines with Vista 64-bit.  That's how you deal with a very large user base.

If windows 64-bit still ran all the 32-bit old drivers and old DOS apps, then you'd complain that Windows is held back by all the backward compatibility it needs to do.  If they breaks it, then you complain it isn't as backward compatible..

Leopard is not a true 64-bit operating system, the kernel is still 32-bit, that's how they "remain compatible".  

I'd also point out that Apple makes no 64-bit applications, none at all, including their FCP suite. I'm only aware of Houdini for OS X being 64-bit.  On Windows, all the majors CAD, multimedia, and video (Autodesk, Avid, Avid, Softimage, Maxxon Cinema 64, NewTek) are 64-bit.  Pretty much all the drivers you need including graphics drivers are there in 64-bit form.  64-bit was really made for these markets, and server-side.  It's ok if the consumer doesn't jump on 64-bit immediately.</description>
		<content:encoded><![CDATA[<p>@danieleran<br />
That article on techtarget.com is poorly worded: Wow64 is not an &#8220;emulator&#8221;. It is a 32-bit sub-system that forwards the Win32 API calls to the 64-bit API. The instructions are not emulated and run-time performance is not affected as the word suggests.</p>
<p>There is no mesurable lost in applications speed, whether games or business, which makes sense, since most common applications will be 32-bit for a long time.</p>
<p>Why did Microsoft make a separate 64-bit version Window SKU?  It was to make a clean break with the old driver models and some obsolete API, old shell extensions, etc.  The 64-bit version is more secure and fixes some holes.  It was to do exactly what people are asking them to do: make a clean break with some of the oldest things.  They also dropped all support for DOS and 16-bit windows application in Windows 64-bit.</p>
<p>It is precisly part of the plan that people will be gradually buying new machines with Vista 64-bit.  That&#8217;s how you deal with a very large user base.</p>
<p>If windows 64-bit still ran all the 32-bit old drivers and old DOS apps, then you&#8217;d complain that Windows is held back by all the backward compatibility it needs to do.  If they breaks it, then you complain it isn&#8217;t as backward compatible..</p>
<p>Leopard is not a true 64-bit operating system, the kernel is still 32-bit, that&#8217;s how they &#8220;remain compatible&#8221;.  </p>
<p>I&#8217;d also point out that Apple makes no 64-bit applications, none at all, including their FCP suite. I&#8217;m only aware of Houdini for OS X being 64-bit.  On Windows, all the majors CAD, multimedia, and video (Autodesk, Avid, Avid, Softimage, Maxxon Cinema 64, NewTek) are 64-bit.  Pretty much all the drivers you need including graphics drivers are there in 64-bit form.  64-bit was really made for these markets, and server-side.  It&#8217;s ok if the consumer doesn&#8217;t jump on 64-bit immediately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myths of Snow Leopard 1: PowerPC Support &#8212; RoughlyDrafted Magazine</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9924</link>
		<dc:creator>Myths of Snow Leopard 1: PowerPC Support &#8212; RoughlyDrafted Magazine</dc:creator>
		<pubDate>Tue, 24 Jun 2008 13:39:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9924</guid>
		<description>[...] have panicked that Snow Leopard will kill support for even 32-bit Intel Macs. That is addressed in Myths of Snow Leopard 2: 32-bit Support.  [Update: Warren Gish forwarded the following comment on PowerPC and 64-bit computing in Snow [...]</description>
		<content:encoded><![CDATA[<p>[...] have panicked that Snow Leopard will kill support for even 32-bit Intel Macs. That is addressed in Myths of Snow Leopard 2: 32-bit Support.  [Update: Warren Gish forwarded the following comment on PowerPC and 64-bit computing in Snow [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myths of Snow Leopard 5: No Carbon! &#8212; RoughlyDrafted Magazine</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9923</link>
		<dc:creator>Myths of Snow Leopard 5: No Carbon! &#8212; RoughlyDrafted Magazine</dc:creator>
		<pubDate>Tue, 24 Jun 2008 13:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9923</guid>
		<description>[...] Myths of Snow Leopard 2: 32-bit Support [...]</description>
		<content:encoded><![CDATA[<p>[...] Myths of Snow Leopard 2: 32-bit Support [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Felix</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9872</link>
		<dc:creator>Felix</dc:creator>
		<pubDate>Mon, 23 Jun 2008 21:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9872</guid>
		<description>Actually, there's at least a third app running on 64 bits on Leopard: httpd (Apache's daemon).</description>
		<content:encoded><![CDATA[<p>Actually, there&#8217;s at least a third app running on 64 bits on Leopard: httpd (Apache&#8217;s daemon).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephilei</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9570</link>
		<dc:creator>Ephilei</dc:creator>
		<pubDate>Wed, 18 Jun 2008 21:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9570</guid>
		<description>Chess?!

I thought 32bit only supported 4GB RAM, not the 32GB in the article</description>
		<content:encoded><![CDATA[<p>Chess?!</p>
<p>I thought 32bit only supported 4GB RAM, not the 32GB in the article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: neoanderthal</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9544</link>
		<dc:creator>neoanderthal</dc:creator>
		<pubDate>Wed, 18 Jun 2008 14:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9544</guid>
		<description>I understand what you're saying - and there's no arguing with the technical details of the 32-bit &#38; 64-bit implementation on windows. I will say, however, that I've not yet run into any application or game that would not run on Windows 64-bit. It doesn't do this in any way that is reminiscent of the 'classic' mode on PPC Mac OS X - you just run the program. From a standpoint of simply running applications, it *seems* seamless, regardless of what sort of chicanery is going on in the background.
It's all good and well to read someone else's theories as to the problems that may crop up, but i'm relating my personal, empirical day-to-day experience with CS3, Office, games like Quake Wars, Hellgate:London, DDO:Stormreach, Diablo 2, Psychonauts, KOTOR/KOTOR 2, etc.
It's not an elegant solution, to be sure. There's no way Windows could have a seamless 32/64 library, as too many installers mess around with DLLS, and that would definitely be a problem. This points to a superiority in design of OS X,  certainly. 
I am no fan of Windows, but I am a fan of real experience versus theoretical discussion.</description>
		<content:encoded><![CDATA[<p>I understand what you&#8217;re saying - and there&#8217;s no arguing with the technical details of the 32-bit &amp; 64-bit implementation on windows. I will say, however, that I&#8217;ve not yet run into any application or game that would not run on Windows 64-bit. It doesn&#8217;t do this in any way that is reminiscent of the &#8216;classic&#8217; mode on PPC Mac OS X - you just run the program. From a standpoint of simply running applications, it *seems* seamless, regardless of what sort of chicanery is going on in the background.<br />
It&#8217;s all good and well to read someone else&#8217;s theories as to the problems that may crop up, but i&#8217;m relating my personal, empirical day-to-day experience with CS3, Office, games like Quake Wars, Hellgate:London, DDO:Stormreach, Diablo 2, Psychonauts, KOTOR/KOTOR 2, etc.<br />
It&#8217;s not an elegant solution, to be sure. There&#8217;s no way Windows could have a seamless 32/64 library, as too many installers mess around with DLLS, and that would definitely be a problem. This points to a superiority in design of OS X,  certainly.<br />
I am no fan of Windows, but I am a fan of real experience versus theoretical discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myths of Snow Leopard 2: 32-bit Support &#124; Stan's List</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9522</link>
		<dc:creator>Myths of Snow Leopard 2: 32-bit Support &#124; Stan's List</dc:creator>
		<pubDate>Wed, 18 Jun 2008 04:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9522</guid>
		<description>[...] RoughlyDrafted has an excellent article on whether Snow Leopard will support PPC Macs or early 32-bit Intel Macs. In laying out the arguments, the magazine starts from what may seem an unrelated quote from Mary Jo Foley: [...]</description>
		<content:encoded><![CDATA[<p>[...] RoughlyDrafted has an excellent article on whether Snow Leopard will support PPC Macs or early 32-bit Intel Macs. In laying out the arguments, the magazine starts from what may seem an unrelated quote from Mary Jo Foley: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danieleran</title>
		<link>http://www.roughlydrafted.com/2008/06/17/myths-of-snow-leopard-2-32-bit-support/#comment-9510</link>
		<dc:creator>danieleran</dc:creator>
		<pubDate>Tue, 17 Jun 2008 22:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=1945#comment-9510</guid>
		<description>@ neoanderthal: Being able to run some or even most 32-bit apps on x64 Windows Server is not the same as being able to seamlessly run 32-bit apps on 64-bit Windows. 

This article explains in part why running standard apps on 64-bit Windows is frustrating and problematic:

"The x64 version of Windows is not capable of natively running 32-bit code. Because most applications are 32-bit, the x64 version of Windows makes use of an emulator known as WOW64 to allow 32-bit applications to run."

"One of the problems with running 32-bit code on a 64-bit operating system is that the OS must maintain complete code separation. Microsoft has created a new folder named \Windows\SysWOW64 that is used to store the 32-bit DLLs. In the 32-bit version of Windows, DLL files are normally stored in the \windows\system32 folder. However, the x64 version of Windows uses the \windows\system32 folder for 64-bit DLLs."

I dare you to rename your System32 folder on a regular PC. 64-bit Windows does just that. Boom. You just never know exactly when its going to flip out.

http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1218185,00.html</description>
		<content:encoded><![CDATA[<p>@ neoanderthal: Being able to run some or even most 32-bit apps on x64 Windows Server is not the same as being able to seamlessly run 32-bit apps on 64-bit Windows. </p>
<p>This article explains in part why running standard apps on 64-bit Windows is frustrating and problematic:</p>
<p>&#8220;The x64 version of Windows is not capable of natively running 32-bit code. Because most applications are 32-bit, the x64 version of Windows makes use of an emulator known as WOW64 to allow 32-bit applications to run.&#8221;</p>
<p>&#8220;One of the problems with running 32-bit code on a 64-bit operating system is that the OS must maintain complete code separation. Microsoft has created a new folder named \Windows\SysWOW64 that is used to store the 32-bit DLLs. In the 32-bit version of Windows, DLL files are normally stored in the \windows\system32 folder. However, the x64 version of Windows uses the \windows\system32 folder for 64-bit DLLs.&#8221;</p>
<p>I dare you to rename your System32 folder on a regular PC. 64-bit Windows does just that. Boom. You just never know exactly when its going to flip out.</p>
<p><a href="http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1218185,00.html" rel="nofollow">http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1218185,00.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
