Linked by Thom Holwerda on Sat 7th Mar 2009 23:47 UTC
Mac OS X Thanks to Ars Technica, we've got some Snow Leopard goodness for you. As always, Apple is quite secretive about its upcoming operating system, so even though test builds are released every now and then, information is scarce. An Ars reader has given some more insights into the latest Snow Leopard build, released on Friday.
Thread beginning with comment 352311
To view parent comment, click here.
To read all comments associated with this story, please click here.
MysterMask
Member since:
2005-07-12

*sigh*
Another 'I - Thom H. - am right and Apple is wrong' rant ..


Did I say so?


No, but it is quite obvious where you get your ideas from..



It's about destructiveness. It's more important that files do not get lost. Merging makes sure that this does not happen - replace makes people lose files, and there is no "undo" feature, which makes it even less desirable.


*tss*
The OS is asking you, if you like to replace the file / folder. Nothing get's lost accidentially (if you're not stupid and blindly think that it will act like Explorer).

Merging on the other hand means that you don't know exactly what you get, because files deep down in the hierarchy you're copying should or should not be merged.
I prefere to know the outcome of an operation before I do it and the outcome is crystal clear when it comes to the Mac implementation. No silly Explorer behaviour like "Oh, sorry, I just moved half of the files you liked to move and then hit one which was locked by another process so I just stopped copying in the middle of nowhere. Go find out yourself what I did or didn't."

BTW: If you really think that losing files is bad, please tell me why the Windows 'delete' behaves differently for a local file (goes to the trash) and a file from a networked drive (will be deleted immediately). Now, that's dangerous and annoying!


You can indeed move a file that's in use to the trash, but if you then try to delete it, it isn't possible.


At least you have it in the trash and can delete it later. That's what the trash is for: mark files for later removal. So the Mac implementation is all ok.

On the other side, try moving a file in Windows to the trash. You can't. You can't mark it for removal. So you have to think about it and do it later. Do you really think this is better?!



I've used Mac OS X for a long time now, since 2002/2003 (like I said, a little longer than your measly 18 months), so I know my shit.


Time doesn't matter that much. There are users that constantly try to get it the way they are used to from other platforms and others who learn to use it how it was meant to be on the platform they use.

Maybe you should start using the Finder the way it was meant to be. E. g. the Mac Finder was designed to be used with several windows open at once unlike Explorer which is often used in a 'single window' mode and hence would be unusable without things like 'cut' to move files.


I've yet to find a truly positive review of the Finder.


No problem. Finder is a very good file browser. I really like it much, much more than inconsistent, slow and buggy Windows Explorer (and I use both on a daily basis). The fact that Windows people get problems because they expect things to behave like Explorer doesn't matter for most long time Mac users. It is not very suprising then that Mac users mostly miss other features in Finder than switchers who are not willing to learn new things.

If you don't like Finder: there are other file browsers for Mac. Find one that fits into you're small world view..

Reply Parent Bookmark Score: 2

Thom_Holwerda Member since:
2005-06-29

No, but it is quite obvious where you get your ideas from..


...?

BTW: If you really think that losing files is bad, please tell me why the Windows 'delete' behaves differently for a local file (goes to the trash) and a file from a networked drive (will be deleted immediately). Now, that's dangerous and annoying


What is this weird thing that Apple fanatics have, where if you crticize a specific, small, isolated behaviour in Mac OS X, you're automatically approving of all behaviour in Windows? Where does this come from? Can you only OR hate ALL that Apple does, OR hate ALL that Windows does?

I'm sorry, but my world isn't as black and white as yours. Mac OS X and windows both suck a whole load of monkey balls, just like every other operating system out there. Suckage is a mandatory framework of operating systems, and Apple has been beating Mac OS X with t3h suck stick just as much as Microsoft has been beating Windows.

I'm pretty sick of people having this "OR... OR" view on operating systems. Just because you start farting fairy dust whenever you use an Apple product doesn't mean I'm not allowed to AND criticise it, AND still not like Windows.

On the other side, try moving a file in Windows to the trash. You can't. You can't mark it for removal. So you have to think about it and do it later. Do you really think this is better?!


It both sucks. Mac OS X gives you the wrong impression, and Windows doesn't let you mark it. The proper behaviour, of course, would be to state why the file can't be removed, which file we're talking about if it's part of a batch, what program is using it, and how we can resolve the issue.

Again, just because I think Apple's way sucks monkey balls doesn't mean Microsoft's way can't suck monkey balls either.

The fact that Windows people get problems because they expect things to behave like Explorer doesn't matter for most long time Mac users. It is not very suprising then that Mac users mostly miss other features in Finder than switchers who are not willing to learn new things.


Except... I'm not a Windows person. I've actually never met a file manager that I found pleasant to use, Explorer sucks, Finder sucks, Tracker sucks, Nautilus sucks... You name it.

Once again, just because I don't like the Finder, doesn't mean I automatically have to like Explorer. The world isn't black and white.

Reply Parent Bookmark Score: 2