<?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: Finding the OS X Turbo Button</title>
	<atom:link href="http://mjtsai.com/blog/2008/02/28/finding-the-os-x-turbo-button/feed/" rel="self" type="application/rss+xml" />
	<link>http://mjtsai.com/blog/2008/02/28/finding-the-os-x-turbo-button/</link>
	<description></description>
	<pubDate>Thu, 08 Jan 2009 20:06:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: n[ate]vw</title>
		<link>http://mjtsai.com/blog/2008/02/28/finding-the-os-x-turbo-button/#comment-249087</link>
		<dc:creator>n[ate]vw</dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2008/02/28/finding-the-os-x-turbo-button/#comment-249087</guid>
		<description>Why do Firefox and Safari need to turn of coalesced updates in the first place? Apple provide guidelines (http://developer.apple.com/documentation/Performance/Conceptual/Drawing/Articles/FlushingContent.html) for avoiding performance problems in light of this. Are there architectural reasons these can't be followed?

[This really isn't the place to ask this, I know, but the comment thread is pretty far gone at the original article.]</description>
		<content:encoded><![CDATA[<p>Why do Firefox and Safari need to turn of coalesced updates in the first place? Apple provide guidelines (http://developer.apple.com/documentation/Performance/Conceptual/Drawing/Articles/FlushingContent.html) for avoiding performance problems in light of this. Are there architectural reasons these can't be followed?</p>
<p>[This really isn't the place to ask this, I know, but the comment thread is pretty far gone at the original article.]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
