<story><title>“This presentation can’t be opened because it’s too old”</title><url>https://plus.google.com/+StefanUrbanek/posts/LKkGeEoPUzA</url></story><parent_chain><item><author>jakejake</author><text>The author might consider using Microsoft products because they are obsessive about providing backwards compatibility.  That&amp;#x27;s one of the positive things about Microsoft products.  The downside is that they have to deal with a lot of old baggage as a result.&lt;p&gt;Apple, on the other hand is almost the opposite.  They&amp;#x27;re obsessive about upgrading everyone and leaving the past behind.  That&amp;#x27;s great because they&amp;#x27;re free to make bold and innovative changes.  The downside of course is that you and your files sometimes get left behind.&lt;p&gt;Both are valid strategies in my opinion and appeal to different customers.  If you feel like backwards compatibility is a really important feature then whether you want to admit it or not, you probably would be happy as a Microsoft customer.</text></item></parent_chain><comment><author>tolmasky</author><text>The most important point here is that if you are aware of the problem and provide an incredibly lame dialog to deal with it, then you should have just provided the solution. Clearly Apple has all the necessary tools in their possession to fix this problem: they own the source to both Keynote &amp;#x27;09 and the latest Keynote. Why not either 1) make a small conversion utility and provide a direct link to it in the dialog (still lazy but at least actionable), or 2) include said utility as part of the latest Keynote so you don&amp;#x27;t have to show a dialog? We&amp;#x27;re not talking &amp;quot;backwards compatibility philosophy&amp;quot; here, we&amp;#x27;re talking user experience 101 (something Apple used to hold in the highest regard). This is particularly important given the context of the software: certain file formats are expected to stick around way longer than others. In particular, with presentation software there are loads of class slides sitting on the internet that probably will never be updated, which means you are often putting the onus on someone who didn&amp;#x27;t make the file to go and convert it. Compare this to, say, Final Cut where the only real client of the serialized file is probably the original creator, and it is thus more reasonable to expect a higher degree of personal responsibility in keeping it up to date.</text></comment>
<story><title>“This presentation can’t be opened because it’s too old”</title><url>https://plus.google.com/+StefanUrbanek/posts/LKkGeEoPUzA</url></story><parent_chain><item><author>jakejake</author><text>The author might consider using Microsoft products because they are obsessive about providing backwards compatibility.  That&amp;#x27;s one of the positive things about Microsoft products.  The downside is that they have to deal with a lot of old baggage as a result.&lt;p&gt;Apple, on the other hand is almost the opposite.  They&amp;#x27;re obsessive about upgrading everyone and leaving the past behind.  That&amp;#x27;s great because they&amp;#x27;re free to make bold and innovative changes.  The downside of course is that you and your files sometimes get left behind.&lt;p&gt;Both are valid strategies in my opinion and appeal to different customers.  If you feel like backwards compatibility is a really important feature then whether you want to admit it or not, you probably would be happy as a Microsoft customer.</text></item></parent_chain><comment><author>Touche</author><text>Files are data. Data should be eternal. You should be able to convert a presentation you make today 30 years from now to a newer format. Making software not-backwards compatible is fine and normal but if files expire in a few years Apple is saying that the things you do on their computers are disposable.</text></comment>