5 ms·
A few little arguments in favor of this practice: 1. You plug a USB device into one Mac. It asks you if you want to use it for Time Machine. You say no. Now, n
by derefr 12y ago
A few little arguments in favor of this practice:
1. You plug a USB device into one Mac. It asks you if you want to use it for Time Machine. You say no. Now, no other Mac will ask you this question again—because the preference has been stored on the drive, instead of on the computer.
2. You create a folder with an app you've written in it, and customize it with a cute "drag [this] onto [shortcut to Applications folder]" background, centering the icons on the background positions and sizing the window to perfectly fit the representation. You then copy this folder to another Mac (or any equivalent process, such as converting it into a DMG disk image and having someone download it.) They see exactly what you saw.
3. You keep an external hard disk that you frequently move back-and-forth between two Macs. The first time you plugged it into one of the Macs, it was indexed. Each time you modify it on either Mac, that index gets updated. The most recently created files are the most likely to be the ones you'll want to find through Spotlight when you plug the disk into the other Mac—but if the index was machine-local rather than disk-local, the new Mac wouldn't know about the new files yet, and would have to finish re-indexing to find them. (This is, of course, what happens when you modify the disk on a Windows computer, and it sucks. We really need a "metadata index API" to start being an expected offering of a filesystem, such that all OSes interacting with the filesystem can read and update it!)
On the other hand, Windows' Thumbs.db is exactly the sort of thing you don't want cached on the media. It'd be a great innovation if, say, cameras could pre-generate Thumbs.db files so Windows could immediately show the user what was on an SD card the first time it got plugged in... but cameras don't, because Thumbs.db is a random proprietary format. So, instead, it's only useful in the same situation that the Spotlight index is: moving a drive full of photos back and forth between two computers. Which might have separate screen DPI, and thus be set to show different thumbnails, meaning new thumbnails will get generated anyway.
- TylerE 12y agoI've always wonders why apple doesn't have some sort of .app.gz "special". Why does DMG have any reason to exist? Even if you really really think you need to ship a readme (Hint: No one reads them, and you don't) a zip is simpler and opens quicker.
- jordigh 12y ago> Why does DMG have any reason to exist? History and backwards compatibility. The format itself also does a bit more than just a file archive, as it's a disk image format. You can do things like style the background and so forth.
- derefr 12y ago1. Because a DMG can hold an HFS+ filesystem, and an HFS+ filesystem can represent files with resource forks. So, backward compatibility. 2. Because a DMG actually is a disk image, not a partition image—and therefore can represent a collection of volumes. If I recall, OSX's current "clean" install process effectively just takes a DMG containing {EFI, OS Base, Full Restore Image} volumes and uses the functionality of the "Erase and Overwrite with a DMG" option in Disk Utility to replace your disk's contents with it.
- kalleboo 12y agoA gzip could represent HFS+ forks and attributes the same way the article is discussing - AppleDouble files and .DS_Store files. In fact, this is exactly what is done with zip files you create in the Finder. Anyway, there's no way Apple is going to make improvements to the manual app install process anymore now that they have the App Store.
- derefr 12y agotar (which is what you mean) could do this, but until OSX Macs didn't ship with tar. DMG (technically the UDIF file format) came about as a continuation of .img files (the NDIF file format); there had already been built up some ecosystem around .img and .smi files and Apple wasn't going to suddenly switch to thinking in terms of tar files when they didn't have to. Plus, a UDIF image can be simply passed to the kernel as a loopback image for a block device, and the files on it will then be discovered as plain files. For the same to work with tar or zip files, Apple would have had to introduce either something like the concept of Plan9/FUSE-like server processes that translate arbitrary backing stores into filesystem mounts; or break the universal abstraction of a filesystem by creating a higher-level shell namespace that could "see into" archives (like Windows and GNOME do) making OSX's Unix integration much less useful. Mainly, though, it's that zip and tar are archival file formats. They're suboptimal for doing random-access updates on their contents, which is an important use-case of disk image formats. DMGs exist on OSX for the same reason that VHD(X)s exist on Windows: it turns out they're just a pretty great and flexible format for doing a lot of things OSes want to do.
- ploxiln 12y agoOr, OS X could wait until the appropriate time to offer you the option of messing with your disk. 1. Don't ask about using the disk for Time Machine. When the user goes to Time Machine because they want to use Time Machine, then have a button in the sidebar "Use drive blah for Time Machine" for any non-time-machine external drives present. 2. Have a button at the top of a finder window in which icons have been re-arranged saying "preserve layout in this folder" (which you only have to click the first time, of course it remembers along with the layout). (Also, make it more convenient to default all folders/finders to list-with-details view, for people who have any idea what they're doing.) 3. When the user opens Spotlight, have a button in the sidebar "index this drive for Spotlight" for any un-indexed drives present. In all these cases, it's still super duper easy to use all these things, without always bothering people who don't want these things.
- skore 12y ago> then have a button > Have a button > have a button That's your problem right there.
- emsy 12y agoUgh, OS X pseudo simplicity is the worst. Want to align the dock in a corner? Want to tab through dialog options? There's an arcane terminal command for that. The list goes on, I have these to on top of my head. At least the first two problems are the exception not the rule. I want most of my USB-Drives not to be used as a Time Machine, therefore it should be the rule: Drives are not used for Time Machine unless noted otherwise. Since there's a pref pane for it, it wouldn't even need an extra button. Most user's will not prepare the layout of the files and folders in some fancy way, so just show them arbitrarily, unless otherwise noted. Just hide the option in the "Get Info" dialog. Drive Indexing options could be hidden in the "Get Info" dialog, but I'd be fine with keeping it enabled by default.
- skore 12y agoAs a Kubuntu user and dedicated nerd, I fully agree. But as somebody who has spent some time trying to make user interfaces understandable to people, I'm a little more pragmatic and can see that pseudo simplicity still yields good results. The Time Machine thing is pure marketing, of course. It drives conversions. That's its own brand of terrible, but even THEN you could argue that pushing people to do backups in whatever way isn't necessarily pure evil.
- moe 12y agoNo need to contrive lame excuses. It's just bad software design, plain and simple.
- rakoo 12y agoI believe the way you describe is the better way for users, but the problem seems to be about the .files littering the whole filesystem. Why not have a top-level .hidden folder, where everything is put in, for any OS ? You'd have the OSX's .DS_Store, Windows' Thumbs.db, and whatever Linux-specific dot-file you can have. I kind of see a parallel with applications willing to put their stuff in ~/.myappconfig instead of the central ~/.config/myappconfig, and it bothers me as well.
- lultimouomo 12y ago> Thumbs.db is a random proprietary format I may be wrong here, but it doesn't look to me that .fseventsd, .Trashes and .spotlight are open, standardized multi-platform formats. Unless random proprietary format means "My mac doesn't read it".
- __david__ 12y ago".Trashes" is just a directory. There's no "format" to speak of… Your point stands for the other files, though.
- Nevor 12y agoJust a side note, Thumbs.db are no longer created in visited folders since Vista. Mac OS seems to be the last OS that randomly trashes removable mass storage.
- frik 12y agoFirst thumbs.db was a WinXP only thing. Windows Vista and higher store the thumbnails on C:\ in the users folder! But actually the thumbs.db file was great! The thumbnails were local next to the files. With WinNT 6+ the thumbnail store grows several GBs on C: for each user. If one moves a directory it has to reindex it. Attaching a USB removeable drive increases your central thumbnail file on C: even further. There is a pruning feature so if you don't access the USB storage the data is overwritten. Then the Windows Shell has to index Terabytes of external data again. Win7 has a bug that every now and then updating the central thumbnail store (and using Windows Security Essential) consumes more memory (16+ GB) than is available - it was clearly never tested with 100.000s of media files. It doesn't help that Windows Explorer starting with Vista lost several convenient features like remember the file list style of every folder or using a "folder.jpg" file as folder preview picture instead of showing 4 random pictures. Win8.1/10 at least brought back the "up" button. WinXP had also a real toolbar that could be changed, now you need a custom shell extension.
- RexRollman 12y agoAm I the only one who doesn't like file preview icons in my file manager? I always turn it off on Windows and OS X.