<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Solving the evolving File Format problem</title>
	<link>http://ansemond.com/blog/?p=90</link>
	<description>Find It! Keep It! developer's blog</description>
	<pubDate>Wed, 19 Jun 2013 16:32:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Andy Matuschak</title>
		<link>http://ansemond.com/blog/?p=90#comment-10781</link>
		<pubDate>Thu, 16 Aug 2007 18:15:05 +0000</pubDate>
		<guid>http://ansemond.com/blog/?p=90#comment-10781</guid>
					<description>See, I like this solution because it means I don't have to do any work. The only thing is that one of the huge wins of automatic updates is that you don't really have to worry about your userbase using old versions of the software, which saves you time doing things like this.

Another thought: the appcast could conceivably store flags on versions that the developer is aware will have compatibility issues.</description>
		<content:encoded><![CDATA[<p>See, I like this solution because it means I don&#8217;t have to do any work. The only thing is that one of the huge wins of automatic updates is that you don&#8217;t really have to worry about your userbase using old versions of the software, which saves you time doing things like this.</p>
<p>Another thought: the appcast could conceivably store flags on versions that the developer is aware will have compatibility issues.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
