KOENIG Yvan wrote:
Little Snitch is not in the list of applications matching OS X Lion rules, more, as far as I know, it's not available thru the MAS.
I am sorry Yvan I hoped you'd appreciate a little humour in this discussion. I was indeed directing my allusion at you.
I wanted to say, I don't understand your self-appointed sheriff approach to "rules".
When someone "breaks" Apple rules in your understanding, you report them. When Apple gives you a sign to be less vocal in this tread, you just keep plowing on.
When you make workarounds to make life with the new saving paradigm easier, it is ok.
When software companies do that, it is wrong. Do you see the pattern?
Versioning/Autosave feature—as useful as it could possibly be—is very fresh and it was implemented badly in many Apple users' opinion.
Apple often get their software and hardware right the first time but understandably had its lemons and misfires even in recent history. I could mention Mobile Me, Apple TV, Ping or FCP X fiascos. In some cases, Apple fixed them in future iterations. This is what I and many others contributing to this thread hope will happen here. This is why we are providing feedback and saying "this isn't working".
In current implementation of Versioning/Autosave files are easily disjointed with their versions if they're moved, sent, copied, opened on a network/portable drive or shared in other way. Even sharing with another computer via iCloud detaches it from saved versions.
There is too little control over when (and if at all) a version is created.
Autosave is not suited for graphic applications. Autosaving a JPG file will add lossy compression to a file initially saved with lossy compression.
Autosave is not suited for other types of applications, e.g. code editors, especially that those work with both local and remote files and make use of specialized version control software.
The list of holes in the implementation is long and was repeated here many times. There are more and more signs that Apple might want to reconsider the feature. If creators of Pixelmator, an app which has won Apple Design Award decides to add a secret switch, this is very telling.
As it turns out, software companies are not eager to implement Autosave/Versioning (or Sandboxing). Apple not only extended the deadline for those features, they also added a category in the App Store which would have not made sense had developers rushed to implement all the new features. Virtually all apps would belong in this category if all those features were good.
Seeing that many applications don't and will not use Autosave/Versions (note Adobe with their now accessibly-priced Creative Suite, also some AppStore apps that don't make the "enhanced" list), this created a situation where user can never be sure how each application on their computer saves files.
It is, simply put, an UX mess and it looks like it will stay a mess for a long time to come. I am sure they are aware of this at Apple and are looking for a good solution.
I am actually curious to see what Apple's decision on Pixelmator is if you have indeed reported it. I must say I would be happy enough if Apple provided a system-wide Terminal switch like Pixelmator's. This would allow to bring some consistency, i.e. regular users would all get the Autosave/Lock/Duplicate behaviour, power users would get the "normal" way. I predict this would convince developers to finally implement Autosave.
It has always been like that: regular users just go by Apple's defaults while others can opt to change them. I, for instance, don't use Time Machine and opt for daily differential SuperDuper! backups on my Apple Time Capsule.