Re: To be honest
"Save as" is the perfect example of how users get used to bad practice and obstinately wish to remain with what they are used to.
"Save as" is responsible more than anything else for file system detritus, with multiple versions of files littering the filing system where there is no clear cardinal working version. A recipe for disaster. When you consider that OSX now has versioning built right-in why, oh why do you need "save as"?
If you are renaming, use the rename function. On OSX you keep a single file with *all previous versions in it and browsable (with a handy comparison tool) and retrievable* and you won't end up with different versions littered everywhere and end up forgetting what the crap each one was for.
If you are starting a branched version, use the "duplicate" command. You will end up with a duplicate version you will be prompted to give a new name when you next save and you will also be explicitly prompted to save the old version before you exit that one too. The problem with using "save as" for making duplicates is users often forget to save a version before they use "save as", so what is in that version they have left behind, well um they aren't too sure when they last saved it, so better just leave it there for ever and f**king ever because the file is in that all important intermediate state "I'm not sure what but, hell, one day I might need it."
Like we need more of that in our lives.
Cm'on, engage brain, tell me one way "save as" can remotely be seen as better than using "duplicate" and "rename" commands.