Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I am not whining about it. Why do you keep bringing it up and dodging the question ?

I repeat once more in the vain hope you'll get it : Why are you so defensive against cut & paste ?



And again for the Apple people : Cut on a file does nothing in other file managers. It only marks the file for a move operation. Cutting a file and then rebooting does not result in loss of data. That would be insane.

Every other file manager got it right, are you claiming Apple wouldn't ?

Even when the computer completely shuts down?

I'm not “defensive” at all.
 
Even when the computer completely shuts down?

Are you being dense on purpose ? File managers, those designed intelligently, do nothing on a cut. Nothing. Your filesystem is left untouched. All it does, in a variable somewhere in the File Manager is mark it that the selected file will be moved on paste. If your computer completely shuts down and comes back up, the only thing you've lost is the fact that you were going to move the file, not the file itself.

I've explained this enough times, time to go play with Explorer, Dolphin, Nautilus, Konqueror, EFM and dozen other file managers if you want to see for yourself how much of a non issue this is.

Isn't that the whole purpose of a journaled filesystem?

The purpose of a journaled filesystem is wasted here because there are no operations on the filesystem that you could've lost in the first place. A journaled filesystem is good if writes were not committed before a crash, but in the case we're talking about, issuing a cut in a graphical file manager, nothing actually happens except in the state of the file manager.
 
Are you being dense on purpose ? File managers, those designed intelligently, do nothing on a cut. Nothing. Your filesystem is left untouched. All it does, in a variable somewhere in the File Manager is mark it that the selected file will be moved on paste. If your computer completely shuts down and comes back up, the only thing you've lost is the fact that you were going to move the file, not the file itself.

I've explained this enough times, time to go play with Explorer, Dolphin, Nautilus, Konqueror, EFM and dozen other file managers if you want to see for yourself how much of a non issue this is.



The purpose of a journaled filesystem is wasted here because there are no operations on the filesystem that you could've lost in the first place. A journaled filesystem is good if writes were not committed before a crash, but in the case we're talking about, issuing a cut in a graphical file manager, nothing actually happens except in the state of the file manager.

sjobs@apple.com WHINE at him!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.