Davide

looks like mac has already watched epi1-3…just joking,
actually a strange behaviour

baldo

yea.. when my mac is in sleeping mode, he watches my episodes.. :)

mediamixture

Yeah, that’s pretty weird. I would argue that both OS’s should not even ask the question for this situation. With this example, there isn’t even a naming conflict so why can’t it merge the files without any user input? In the event there is a filename conflict, why not defer the resolution until the end of the copy process so that I don’t need to sit there and wait for the next question to answer. Even if I chose not to deal with it at that moment, there’s no reason why the OS couldn’t just track those duplicate files so that I could just figure out which one I really wanted at some point in the future.

To me, it just seems like file systems should be smart enough these days to handle this gracefully.

baldo

yea.. mediamixture, you are right.. AND another big problem is that the overwrittten folder is just deleted and not in the trash..

luca maioli

This is not exactly smart, or useful but it is linear. Windows perform a merge and mac osx perform a clear and rewrite. the same as

rm -r MOVIES
cp /pathToOtherMovies/MOVIES .

So it’s not strange, It’s just different. If you want to replace the folder you do replace everything. I think it’s a good deal ;-), you get exactly what you asked.

baldo

Folders are not files. Files should be overwritted. Folder contents should be merged.

this is my view.. but maybe it’s forced by 10 years of Windows use..

luca maioli

folders are nodes but (special) files too (in the BSD layer, I can’t remember exactly), so I think it’s right to completely overwrite them. Anyway I was thinking about this post and I come up with a solution (because I like the overwrite thing): let the user choose beetwen merge and overwrite. This whould improve greatly the user experience, IMHO.

BTW in osx you can easily workaround this by using the spring folder feature, placing subfolder wherever you want.