MEMORY CLEAN SNOW LEOPARD MAC OS
MEMORY CLEAN SNOW LEOPARD WINDOWS

I think Apple just went with a simplest solution here instead of introducing the whole new concept of merging and new UI to users to potentially create a confusion ('hm. This would also require some kind of comparison dialog to ask users what files to overwrite. (Note that you can't simply name this thing replacing as in Windows, because it's really merging). Apple could add 'Merge' button (or maybe a better title meaning 'Replace files inside the destination folder with files in source folder') in addition to 'Replace' in 'what do you want to do' dialog. I see one solution to this problem: let user decide what to do. How would merge/replace work for him? Since he doesn't have Cool.app, '.cool' folders are not registered as packages, they look like folders to him. Then we send him another version of this document. Now we send this document to a person who doesn't have Cool.app installed. We have 'ol', which is treated like a package in Finder. Our Cool.app stores user documents in packages. Upshot: Apple's UI designers seem to regret adapting the newspaper publisher's concept of the clipboard, and have been trying to invent workarounds ever since, probably because it's a form of 'hidden state.' (See iPhone 1.x and 2.x for a more recent example.) The only time in recent memory Apple acknowledged the validity of a clipboard model was when they tried to adapt it to a 'publish and subscribe' dynamic system in System 7, only to give up when implementation and UI complexities with the concept rendered that unpopular.

MEMORY CLEAN SNOW LEOPARD MAC OS

The notion that you only do work in just one app was considered 'missing the point' for multitasking, which is part of the reason the original 'Switcher' metaphor for multitasking in the classic Mac OS was abandoned. (Even apps that tried to do so were constrained by the OS to provide a 4-pixel gutter around the edges of the screen so the user could always option-click the Finder to the foreground.) Since drag-and-drop requires visible targets to work, and users were expected to have to see data from two or more apps at the same time, it was considered 'rude' to take up the entire screen. (Something that Apple themselves didn't fully come through with regarding APIs until System 7.) It was expected for end users to use drag-and-drop to move information between applications, instead of using the clipboard.

When MultiFinder was introduced to System 6, the Mac's primary difference from the PCs of the era was an emphasis on mouse manipulation, instead of keyboard manipuation (via DOS's command line, mostly).

Sorry, a bunch of irritation just leaked out, there.

MEMORY CLEAN SNOW LEOPARD WINDOWS

I used to blame Windows for this before the local Windows admin demonstrated that no local Windows machine had this problem. The whole thing is terribly buggy and must be approached in an exact manner (FIRST 'eject' any visible shares, THEN cmd-K to bring up the SMB window, type the IP (no hostnames, even though ping, etc works!), wait for about two minutes (literally), then immediately do the auth window when it comes up - waiting a bit will require restarting the process - and then immediately get or put whatever you need.).

Even then, if I'm on wireless (but not on 100MB ethernet, oddly), I only get one use out of it: if I close that Finder window or don't use it for a bit, the share is closed to me in fact, even though it appears to still be there until I try to use it. That's great, because that's never actually worked for me anyway I always have to type the IP address I know the share is on. No concept of 'browsing' SMB networks exists in PF.

Memory clean snow leopard