The problem you and other Windows users suffer from is due to M$ and silly and downright dumb fsckin implementations copied from other systems. The Pasteboard aka cut/copy/paste is intended for selected data to be placed temporarily in RAM to be migrated to another document either the same application or inter-applicationt!! Moving data in the above manner has been used by Unix systems years before M$ was even born "stdin/stdout". The primary use was and still is for ASCII data or Rich Text Format. As such it would be completely thickheaded to use the command to copy a 4 gig video file to move it to a different location on a hard disk. You will not have enough memory to accommodate such a task. Moving or copying files themselves execute Disk I/O tasks. The Finder of course offers Cut/Copy/Paste as it is intended, to be used with the text of file/directory names not the files or directories themselves.
Im sorry but what you are used to on an M$ system is another example of that companies failure to understand the logic behind such simplistic com-putative tasks which have been standardized decades before Microsoft decided to "Think with drunkenness" for the sake of not being scored for directly copying other systems. Kind of like a white cursor I suppose, all pages an documents after all are also white....so they decided to camouflage the cursor?? DUMB!!!
Your silly reasoning has no merit, in the sense that you still have to navigate the FS to paste the file in the location you wish, this is no different than using pop open windows to navigate to the directory to place the file. Either way you still need your mouse to navigate the FS. Here is another tip or 2, if you drag a file an navigate you system using pop open windows you hold down the Command key whilst dragging to move the file, Option key to copy, if you change you mind an want to cancel the operation simply drag it to the menu bar an let go of the file , as i say this will terminate the drag an leave the system as it was. If you still refuse to accept these methods, buy Path Finder, an replace the Finder with it an use the "Drop Stack" in Path Finder. This allows you to drag and drop a file or files eg 2 files then drop another 4 then another 3 then a single one on the Stack, as a temp holding location, then navigate your FS to the directory you wish to place the files then you may select any of the files you previously dropped in the stack, (single files, or the multi groups of files as described) and then move them using simple drag of holding option key down to Copy to the location.) NeXTSTEP had a similar feature called a shelf which was brilliant.
In summary, M$'s feature is fundamentally flawed, there are better ways an better alternatives. Do yourself a favor and investigate these possibilities and learn to adapt.
Spelling MS with a $ definitely makes you look objective. Your post highlights exactly what I feared. Blind arrogance and support for Apple's way of doing things while not considering that maybe this is a feature that many need and that just maybe Apple is in the wrong here. I suppose that because MS and others already have this, it is is hard to accept it as progress for OS X.
I'm not asking for a new feature, only for a more complete and consistent implementation of an existing feature. An implementation that works well on the several dozen operating systems I've used (BeOS, Windows: 95, ME, 2000, XP, Vista, Linux: SUSE, Ubuntu, Redhat, Fedora, Mandrake, Mandriva, Knoppix, Xandros, Linspire, Yopper, Kubuntu, Debian, Gentoo, UNIX: FreeBSD, PC-BSD, Solaris, etc.). I'm not the confused MS user you mistake me for. I'm sorry you consider that my "silly reasoning has no merit," but maybe you should try to view this from the perspective of the 95% not using OS X. Or even better, from an objective perspective. You think I "refuse to accept these methods," but you are wrong. I know the alternatives very well and I find them insufficient and slow for the way I work. This is very different. Once again, I only want a complete implementation of an existing feature and I'm far from being the only one. Like I mentioned, my bug report was not marked as "Behaves Correctly," it was marked as a duplicate. Thus, Apple does not pretend that this is simply the intended behavior.
I should also add that your technical information is completely inaccurate. Modern cut implementations do not copy a huge file in ram or even write it to a temp file to move it. They simply tag the file, for example on Windows it is visually represented as being grayed out, and then when pasted it is moved to its new location. It is no more expensive than drag and drop. The OS can't even distinguish the two at the IO level.
Next time you reply to me, please do your research. Carefully read my previous posts and you'll find most of your points answered. I'm not going to repeat myself again.
