<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Final Cut Pro X features: catching up and superseding</title>
	<atom:link href="http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/</link>
	<description>Tell tales by rewriting reality - Alex Gollner&#039;s editing and media blog</description>
	<lastBuildDate>Wed, 19 Jun 2013 13:00:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: GroovyBrent</title>
		<link>http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/#comment-10361</link>
		<dc:creator><![CDATA[GroovyBrent]]></dc:creator>
		<pubDate>Sun, 08 Jul 2012 16:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://alex4d.wordpress.com/?p=3241#comment-10361</guid>
		<description><![CDATA[Really interesting way to look at things.  By comparing the development of iOS and OSX to FCPX, I think you&#039;ve been able to infer more of Apple&#039;s development strategy than I would have though.  Certainly the hindsight matches well - let&#039;s see what happens with the foresight!]]></description>
		<content:encoded><![CDATA[<p>Really interesting way to look at things.  By comparing the development of iOS and OSX to FCPX, I think you&#8217;ve been able to infer more of Apple&#8217;s development strategy than I would have though.  Certainly the hindsight matches well &#8211; let&#8217;s see what happens with the foresight!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dexter</title>
		<link>http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/#comment-10237</link>
		<dc:creator><![CDATA[Dexter]]></dc:creator>
		<pubDate>Wed, 27 Jun 2012 19:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://alex4d.wordpress.com/?p=3241#comment-10237</guid>
		<description><![CDATA[I wish Motion could receive a significant update, like 3d generated shapes and text. It needs something to pull AE users into the FCP/Motion world.]]></description>
		<content:encoded><![CDATA[<p>I wish Motion could receive a significant update, like 3d generated shapes and text. It needs something to pull AE users into the FCP/Motion world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rd</title>
		<link>http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/#comment-10219</link>
		<dc:creator><![CDATA[rd]]></dc:creator>
		<pubDate>Tue, 26 Jun 2012 02:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://alex4d.wordpress.com/?p=3241#comment-10219</guid>
		<description><![CDATA[Apple built version control into Lion filesystem and now
extending to the Cloud.  That is what will bring multi user workflow.
CoreData is just Object orientated DataBase Schema,
the data is actually stored in sqlite.  sqlite is not designed
to work across multi users, neither is CoreData while older EOF was designed with relational database in mind like Oracle.  real issue with CoreData is
that schema migration is really hard especially when you have
to design for future features into the database and go back
and forth with different schema support in perpetuity.

I think you are too optimistic about future update every year.
Once Apple catches up it might be two years like Aperture.]]></description>
		<content:encoded><![CDATA[<p>Apple built version control into Lion filesystem and now<br />
extending to the Cloud.  That is what will bring multi user workflow.<br />
CoreData is just Object orientated DataBase Schema,<br />
the data is actually stored in sqlite.  sqlite is not designed<br />
to work across multi users, neither is CoreData while older EOF was designed with relational database in mind like Oracle.  real issue with CoreData is<br />
that schema migration is really hard especially when you have<br />
to design for future features into the database and go back<br />
and forth with different schema support in perpetuity.</p>
<p>I think you are too optimistic about future update every year.<br />
Once Apple catches up it might be two years like Aperture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nima</title>
		<link>http://alex4d.wordpress.com/2012/06/25/fcpx-past-and-future/#comment-10215</link>
		<dc:creator><![CDATA[Nima]]></dc:creator>
		<pubDate>Mon, 25 Jun 2012 20:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://alex4d.wordpress.com/?p=3241#comment-10215</guid>
		<description><![CDATA[I agree with your assessment.  I deal with so many people these days that simply hate FCP X and are talking about switching from 7 to other apps.  The reality is that none of them have spent the time to really learn this new app.  Even when I look at smoke, the interface looks outdated to me.  I for one am happy to be on the x wagon.]]></description>
		<content:encoded><![CDATA[<p>I agree with your assessment.  I deal with so many people these days that simply hate FCP X and are talking about switching from 7 to other apps.  The reality is that none of them have spent the time to really learn this new app.  Even when I look at smoke, the interface looks outdated to me.  I for one am happy to be on the x wagon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
