If we were starting without multiple years of experience using "Save As". The problem is a workflow that was expressly used by people to not mess up the original now messes up the original. This is so not good. If we were using OpenVMS (versioning of files is obvious), but it is really a bad design decision. Bringing auto saves to the Mac in the way they did is foolish.

Anyone coming from an iPad or iPhone has no experience of "Save As". These are the users Apple are now targeting. Like it or not.

Anyone coming from the iPad has no experience with the File menu, and Mac users have years of experience with it. Learning a new interface requires learning some new customs.

This is a huge issue with creation in iOS. It is not a form factor or input problem. It is this strange assumption the every action I do is correct and needs to be preserved. I cannot know that my rewrites will be good before I attempt them. Reverting on iOS is a huge pain if its even possible at all.

I wonder if/when Apple will bring Versions to iOS. It seems iCloud on OS X supports it at least.

The problem is that "Save As" has a very specific meaning that Apple's new implementation doesn't respect. In every other DE / other OS X applications / prior versions of OS X, "Save as" means "take the current working copy and save to disk under the given name, presevering the original". In Mountain Lion, "Save As" basically means "Rename". If Apple called the feature "Rename", this wouldn't be an issue; it's an issue because Apple co-opted a very well-established term for a completely different function