<?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: Apple Open Sources Snow Leopard&#8217;s Grand Central Dispatch</title>
	<atom:link href="http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/</link>
	<description>Daniel Eran Dilger in San Francisco</description>
	<lastBuildDate>Sun, 05 Feb 2012 17:03:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: FreeBSD adds support for Snow Leopard&#8217;s Grand Central Dispatch &#8212; RoughlyDrafted Magazine</title>
		<link>http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/comment-page-1/#comment-21728</link>
		<dc:creator>FreeBSD adds support for Snow Leopard&#8217;s Grand Central Dispatch &#8212; RoughlyDrafted Magazine</dc:creator>
		<pubDate>Fri, 16 Oct 2009 21:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3778#comment-21728</guid>
		<description>[...] adds support for Snow Leopard&#8217;s Grand Central Dispatch . Apple publicly announced plans to release its GCD technology as open source last month; the FreeBSD team demonstrated its early [...]</description>
		<content:encoded><![CDATA[<p>[...] adds support for Snow Leopard&#8217;s Grand Central Dispatch . Apple publicly announced plans to release its GCD technology as open source last month; the FreeBSD team demonstrated its early [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raymond</title>
		<link>http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/comment-page-1/#comment-20685</link>
		<dc:creator>Raymond</dc:creator>
		<pubDate>Mon, 14 Sep 2009 08:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3778#comment-20685</guid>
		<description>This makes sense if you consider than the open source community would probably try to make their own clone of GCD, which would be similar but incompatible. Better the API was widely adopted and used, than Apple being isolated in this regard.</description>
		<content:encoded><![CDATA[<p>This makes sense if you consider than the open source community would probably try to make their own clone of GCD, which would be similar but incompatible. Better the API was widely adopted and used, than Apple being isolated in this regard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: feroze</title>
		<link>http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/comment-page-1/#comment-20633</link>
		<dc:creator>feroze</dc:creator>
		<pubDate>Sat, 12 Sep 2009 18:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3778#comment-20633</guid>
		<description>Maybe I am missing something, but how is this different that the concept of pooling threads, and scheduling work to them when needed? This has been around in a lot of OS&#039;s, eg: &lt;a href=&quot;http://msdn.microsoft.com/en-us/magazine/cc163327.aspx&quot; rel=&quot;nofollow&quot;&gt;Windows&lt;/a&gt; as well as in Unix and other environments.

[The concept of a thread pool is not new, which is why Apple refers to GCD as being an instance of one. What is unique is the implementation, and that Apple has made it accessible to its developers. 

As Apple explains, &quot;GCD combines an easy-to-use programming model with highly-efficient system services to radically simplify the code needed to make best use of multiple processors. The technologies in GCD improve the performance, efficiency, and responsiveness of Snow Leopard out of the box, and will deliver even greater benefits as more developers adopt them.

&quot;The central insight of GCD is shifting the responsibility for managing threads and their execution from applications to the operating system. As a result, programmers can write less code to deal with concurrent operations in their applications, and the system can perform more efficiently on single-processor machines, large multiprocessor servers, and everything in between. Without a pervasive approach such as GCD, even the best-written application cannot deliver the best possible performance, because it doesn’t have full insight into everything else happening in the system.&quot;

&lt;a href=&quot;http://developer.apple.com/mac/articles/cocoa/introblocksgcd.html&quot; rel=&quot;nofollow&quot;&gt;Introducing Blocks and Grand Central Dispatch&lt;/a&gt;

Also look at John Siracusa&#039;s overview at &lt;a href=&quot;http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars/12&quot; rel=&quot;nofollow&quot;&gt;Ars Technica&lt;/a&gt;: 

&quot;Those with some multithreaded programming experience may be unimpressed with the GCD. So Apple made a thread pool. Big deal. They&#039;ve been around forever. But the angels are in the details. Yes, the implementation of queues and threads has an elegant simplicity, and baking it into the lowest levels of the OS really helps to lower the perceived barrier to entry, but it&#039;s the API built around blocks that makes Grand Central Dispatch so attractive to developers. Just as Time Machine was &quot;the first backup system people will actually use,&quot; Grand Central Dispatch is poised to finally spread the heretofore dark art of asynchronous application design to all Mac OS X developers. I can&#039;t wait.&quot; 

- Dan]</description>
		<content:encoded><![CDATA[<p>Maybe I am missing something, but how is this different that the concept of pooling threads, and scheduling work to them when needed? This has been around in a lot of OS&#8217;s, eg: <a href="http://msdn.microsoft.com/en-us/magazine/cc163327.aspx" rel="nofollow">Windows</a> as well as in Unix and other environments.</p>
<p>[The concept of a thread pool is not new, which is why Apple refers to GCD as being an instance of one. What is unique is the implementation, and that Apple has made it accessible to its developers. </p>
<p>As Apple explains, "GCD combines an easy-to-use programming model with highly-efficient system services to radically simplify the code needed to make best use of multiple processors. The technologies in GCD improve the performance, efficiency, and responsiveness of Snow Leopard out of the box, and will deliver even greater benefits as more developers adopt them.</p>
<p>"The central insight of GCD is shifting the responsibility for managing threads and their execution from applications to the operating system. As a result, programmers can write less code to deal with concurrent operations in their applications, and the system can perform more efficiently on single-processor machines, large multiprocessor servers, and everything in between. Without a pervasive approach such as GCD, even the best-written application cannot deliver the best possible performance, because it doesn’t have full insight into everything else happening in the system."</p>
<p><a href="http://developer.apple.com/mac/articles/cocoa/introblocksgcd.html" rel="nofollow">Introducing Blocks and Grand Central Dispatch</a></p>
<p>Also look at John Siracusa's overview at <a href="http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars/12" rel="nofollow">Ars Technica</a>: </p>
<p>"Those with some multithreaded programming experience may be unimpressed with the GCD. So Apple made a thread pool. Big deal. They've been around forever. But the angels are in the details. Yes, the implementation of queues and threads has an elegant simplicity, and baking it into the lowest levels of the OS really helps to lower the perceived barrier to entry, but it's the API built around blocks that makes Grand Central Dispatch so attractive to developers. Just as Time Machine was "the first backup system people will actually use," Grand Central Dispatch is poised to finally spread the heretofore dark art of asynchronous application design to all Mac OS X developers. I can't wait." </p>
<p>- Dan]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berend Schotanus</title>
		<link>http://www.roughlydrafted.com/2009/09/12/apple-open-sources-snow-leopards-grand-central-dispatch/comment-page-1/#comment-20625</link>
		<dc:creator>Berend Schotanus</dc:creator>
		<pubDate>Sat, 12 Sep 2009 09:02:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3778#comment-20625</guid>
		<description>Interesting!

I love the concept of GCD. It allows different processes to act independently and interact with each other and to make a decentralized approach to what the computer is doing. This is a fundamentally different approach than the &quot;central truth&quot; paradigm that most of the computer industry is using. For this reason it is absolutely impossible that Microsoft would adapt GCD, there is no way it would fit into their way of thinking.

I am amazed about Apples policy to what they do and do not open for third parties. They are absolutely secretive about the regular business chit-chat that everybody wants to know. But when it comes to the big clues about how things really work it is just openly available. And nobody seems to care...</description>
		<content:encoded><![CDATA[<p>Interesting!</p>
<p>I love the concept of GCD. It allows different processes to act independently and interact with each other and to make a decentralized approach to what the computer is doing. This is a fundamentally different approach than the &#8220;central truth&#8221; paradigm that most of the computer industry is using. For this reason it is absolutely impossible that Microsoft would adapt GCD, there is no way it would fit into their way of thinking.</p>
<p>I am amazed about Apples policy to what they do and do not open for third parties. They are absolutely secretive about the regular business chit-chat that everybody wants to know. But when it comes to the big clues about how things really work it is just openly available. And nobody seems to care&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

