<?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>Commentaires sur : FOSDEM wrap up</title>
	<atom:link href="http://blog.neteril.org/2010/03/13/fosdem-wrap-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.neteril.org/2010/03/13/fosdem-wrap-up/</link>
	<description>Random thoughts of Jérémie Laval</description>
	<lastBuildDate>Mon, 25 Jul 2011 10:32:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Par : Jérémie Laval</title>
		<link>http://blog.neteril.org/2010/03/13/fosdem-wrap-up/comment-page-1/#comment-453</link>
		<dc:creator>Jérémie Laval</dc:creator>
		<pubDate>Sun, 14 Mar 2010 23:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neteril.org/?p=856#comment-453</guid>
		<description>Mono-core user shouldn&#039;t technically see any difference. In practice, there is still some overhead introduced by the whole scheduler thing but since the pixel processing takes so much time it&#039;s barely noticeable.

Any kind of code, unsafe or not, works provided you take care of securing your shared state access if any.</description>
		<content:encoded><![CDATA[<p>Mono-core user shouldn&#8217;t technically see any difference. In practice, there is still some overhead introduced by the whole scheduler thing but since the pixel processing takes so much time it&#8217;s barely noticeable.</p>
<p>Any kind of code, unsafe or not, works provided you take care of securing your shared state access if any.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Par : Stifu</title>
		<link>http://blog.neteril.org/2010/03/13/fosdem-wrap-up/comment-page-1/#comment-451</link>
		<dc:creator>Stifu</dc:creator>
		<pubDate>Sat, 13 Mar 2010 13:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neteril.org/?p=856#comment-451</guid>
		<description>PS: and when I said &quot;sensible&quot;, I of course meant &quot;sensitive&quot;. :D</description>
		<content:encoded><![CDATA[<p>PS: and when I said &laquo;&nbsp;sensible&nbsp;&raquo;, I of course meant &laquo;&nbsp;sensitive&nbsp;&raquo;. <img src='http://blog.neteril.org/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Par : Stifu</title>
		<link>http://blog.neteril.org/2010/03/13/fosdem-wrap-up/comment-page-1/#comment-450</link>
		<dc:creator>Stifu</dc:creator>
		<pubDate>Sat, 13 Mar 2010 13:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neteril.org/?p=856#comment-450</guid>
		<description>That was interesting... Good job.

Off topic: being also French, I&#039;m sensible to English mispronunciations you&#039;ve made (your English is still definitely better than the average French guy, mind you). You may already be aware of some of them, but just in case, I thought you might want to take some mental notes of what follows...

Each = you pronounce it &quot;etch&quot;, it&#039;s more like &quot;itch&quot;
Whole = you shouldn&#039;t pronounce the W, it&#039;s more like &quot;hole&quot; (at first, I actually thought you were saying &quot;as a wall&quot; when describing the image processing)
Promise = the &quot;i&quot; part should the pronounced the same as in &quot;this&quot;, as opposed to &quot;bike&quot; (ie: &quot;prom-is&quot;, not &quot;prom-ahys&quot;)
Notice = same as above
API = Ey Pee Aye

Anyway, back on topic... I&#039;ll see if I can use ParallelFx in my own little app (I create Bitmaps pixel by pixel, so that sounds like a good candidate). Monocore users shouldn&#039;t notice any performance difference, right? And are ParallelFx and unsafe code supposed to work well together?</description>
		<content:encoded><![CDATA[<p>That was interesting&#8230; Good job.</p>
<p>Off topic: being also French, I&#8217;m sensible to English mispronunciations you&#8217;ve made (your English is still definitely better than the average French guy, mind you). You may already be aware of some of them, but just in case, I thought you might want to take some mental notes of what follows&#8230;</p>
<p>Each = you pronounce it &laquo;&nbsp;etch&nbsp;&raquo;, it&#8217;s more like &laquo;&nbsp;itch&nbsp;&raquo;<br />
Whole = you shouldn&#8217;t pronounce the W, it&#8217;s more like &laquo;&nbsp;hole&nbsp;&raquo; (at first, I actually thought you were saying &laquo;&nbsp;as a wall&nbsp;&raquo; when describing the image processing)<br />
Promise = the &laquo;&nbsp;i&nbsp;&raquo; part should the pronounced the same as in &laquo;&nbsp;this&nbsp;&raquo;, as opposed to &laquo;&nbsp;bike&nbsp;&raquo; (ie: &laquo;&nbsp;prom-is&nbsp;&raquo;, not &laquo;&nbsp;prom-ahys&nbsp;&raquo;)<br />
Notice = same as above<br />
API = Ey Pee Aye</p>
<p>Anyway, back on topic&#8230; I&#8217;ll see if I can use ParallelFx in my own little app (I create Bitmaps pixel by pixel, so that sounds like a good candidate). Monocore users shouldn&#8217;t notice any performance difference, right? And are ParallelFx and unsafe code supposed to work well together?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

