<?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: Running CPU Intensive JavaScript Computations in a Web Browser</title>
	<atom:link href="http://www.julienlecomte.net/blog/2007/10/28/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.julienlecomte.net/blog/2007/10/28/</link>
	<description>Web Development and Operating System Programming</description>
	<pubDate>Sun, 06 Jul 2008 19:11:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Andrew Dupont</title>
		<link>http://www.julienlecomte.net/blog/2007/10/28/#comment-579</link>
		<dc:creator>Andrew Dupont</dc:creator>
		<pubDate>Tue, 30 Oct 2007 04:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.julienlecomte.net/blog/2007/10/25/running-cpu-intensive-javascript-computations-in-a-web-browser/#comment-579</guid>
		<description>Great write-up.

I've seen (and used) this pattern in the comparison tests for the CSS selector functions in JavaScript libraries (e.g., &lt;a href="http://mootools.net/slickspeed/" rel="nofollow"&gt;Mootools' Slickspeed&lt;/a&gt;). Without dividing the tests into batches and scheduling them with setTimeout, you'd hang the browser almost immediately and make the benchmarks meaningless.</description>
		<content:encoded><![CDATA[<p>Great write-up.</p>
<p>I&#8217;ve seen (and used) this pattern in the comparison tests for the CSS selector functions in JavaScript libraries (e.g., <a href="http://mootools.net/slickspeed/" rel="nofollow">Mootools&#8217; Slickspeed</a>). Without dividing the tests into batches and scheduling them with setTimeout, you&#8217;d hang the browser almost immediately and make the benchmarks meaningless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .eternal &#187; Long running JavaScript tasks</title>
		<link>http://www.julienlecomte.net/blog/2007/10/28/#comment-576</link>
		<dc:creator>.eternal &#187; Long running JavaScript tasks</dc:creator>
		<pubDate>Mon, 29 Oct 2007 07:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.julienlecomte.net/blog/2007/10/25/running-cpu-intensive-javascript-computations-in-a-web-browser/#comment-576</guid>
		<description>[...] was a recent post on Ajaxian concerning a pattern for running CPU intensive JavaScript tasks by Julien Lecomte. The technique is not new (which was not his point in the first place) and [...]</description>
		<content:encoded><![CDATA[<p>[...] was a recent post on Ajaxian concerning a pattern for running CPU intensive JavaScript tasks by Julien Lecomte. The technique is not new (which was not his point in the first place) and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Zielke</title>
		<link>http://www.julienlecomte.net/blog/2007/10/28/#comment-573</link>
		<dc:creator>Ryan Zielke</dc:creator>
		<pubDate>Sun, 28 Oct 2007 13:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.julienlecomte.net/blog/2007/10/25/running-cpu-intensive-javascript-computations-in-a-web-browser/#comment-573</guid>
		<description>Does this pattern have a name?</description>
		<content:encoded><![CDATA[<p>Does this pattern have a name?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Javascript News &#187; Blog Archive &#187; Running CPU Intensive JavaScript Computations in a Web Browser</title>
		<link>http://www.julienlecomte.net/blog/2007/10/28/#comment-571</link>
		<dc:creator>Javascript News &#187; Blog Archive &#187; Running CPU Intensive JavaScript Computations in a Web Browser</dc:creator>
		<pubDate>Fri, 26 Oct 2007 18:10:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.julienlecomte.net/blog/2007/10/25/running-cpu-intensive-javascript-computations-in-a-web-browser/#comment-571</guid>
		<description>[...] Lecomte has written up the pattern where you use setTimeout() to keep yielding control back to the main thread so that it can handle [...]</description>
		<content:encoded><![CDATA[<p>[...] Lecomte has written up the pattern where you use setTimeout() to keep yielding control back to the main thread so that it can handle [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajax Girl &#187; Blog Archive &#187; Running CPU Intensive JavaScript Computations in a Web Browser</title>
		<link>http://www.julienlecomte.net/blog/2007/10/28/#comment-569</link>
		<dc:creator>Ajax Girl &#187; Blog Archive &#187; Running CPU Intensive JavaScript Computations in a Web Browser</dc:creator>
		<pubDate>Fri, 26 Oct 2007 14:34:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.julienlecomte.net/blog/2007/10/25/running-cpu-intensive-javascript-computations-in-a-web-browser/#comment-569</guid>
		<description>[...] Lecomte has written up the pattern where you use setTimeout() to keep yielding control back to the main thread so that it can handle [...]</description>
		<content:encoded><![CDATA[<p>[...] Lecomte has written up the pattern where you use setTimeout() to keep yielding control back to the main thread so that it can handle [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
