Installers
Jul. 26th, 2007 03:23 pmI was reading What's Wrong With Setup.exe?, and so was Avery, apparently.
I pretty much agree with Avery (and commented so on Jeff's blog), but I'd like to comment on how tricky the part about the DMG files is. The problem is that Mac OS X bundles aren't a single file (that could therefore be downloaded "just like that" and would be very intuitive), but is really a directory full of files (that thus can't be fetched off a web server as a single unit).
I guess Apple was focusing more on the shrink-wrap software publisher's point of view (normally shipping an actual CD-ROM), and kind of provided a virtual equivalent, but it does feel a bit weird.
One solution could be to ZIP the bundle, and give the operating system the ability to run them directly. You could then just download an application, and run it, no weird installation, nothing. It'd be a challenge, for sure. For example, the fault handler in the kernel would have to be able to find the page inside of a compressed ZIP file, if you "do it right". You could cheat and decompress it silently, but that'd could make launching a big application with lots of resources very slow, which is exactly what using a bundle is supposed to help with in the first place (by demand-loading resources). I know about the "stuff the resources inside the EXE" trick, but bundles can (and often do) have multiple binaries.
But they could certainly bite the bullet and find a way, I'm sure.
Note that the Apple approach also follows Avery's first advice. Preference files are created as they are needed, while running the application. It also means that a system administrator can simply put up a read-only file share on the network with the applications used in the office, and it'll Just Work (tm).
I pretty much agree with Avery (and commented so on Jeff's blog), but I'd like to comment on how tricky the part about the DMG files is. The problem is that Mac OS X bundles aren't a single file (that could therefore be downloaded "just like that" and would be very intuitive), but is really a directory full of files (that thus can't be fetched off a web server as a single unit).
I guess Apple was focusing more on the shrink-wrap software publisher's point of view (normally shipping an actual CD-ROM), and kind of provided a virtual equivalent, but it does feel a bit weird.
One solution could be to ZIP the bundle, and give the operating system the ability to run them directly. You could then just download an application, and run it, no weird installation, nothing. It'd be a challenge, for sure. For example, the fault handler in the kernel would have to be able to find the page inside of a compressed ZIP file, if you "do it right". You could cheat and decompress it silently, but that'd could make launching a big application with lots of resources very slow, which is exactly what using a bundle is supposed to help with in the first place (by demand-loading resources). I know about the "stuff the resources inside the EXE" trick, but bundles can (and often do) have multiple binaries.
But they could certainly bite the bullet and find a way, I'm sure.
Note that the Apple approach also follows Avery's first advice. Preference files are created as they are needed, while running the application. It also means that a system administrator can simply put up a read-only file share on the network with the applications used in the office, and it'll Just Work (tm).
no subject
Date: 2007-07-26 09:44 pm (UTC)It makes trying new stuff out a little less hair-raising. It's probably as much of an effect as a cause of the package system, though: only the writer an app that needs to muck with your system (or one that would want you to sit there and watch "Adobe makes your life better" ads for an hour) would consider an installer.
no subject
Date: 2007-07-26 11:51 pm (UTC)no subject
Date: 2007-07-27 12:04 am (UTC)no subject
Date: 2007-07-27 02:37 am (UTC)This isn't even a pro-Mac comment. I'm just kind of half-amused, half-annoyed by the total geekiness of the complaint.
no subject
Date: 2007-07-27 03:13 am (UTC)And while Avery and I are basically saying the same thing you are, it's true that the whole disk image thing is a bit strange. It's not much effort in terms of time or clicks, but it's just conceptually odd, compared to how intuitively simple the rest of the process is. Note that mounting and unmounting devices is something that the Linux people had to work hard to get rid of and make it similar to Mac OS X (plug it in or insert it, appears right away), so having brought back the "mount" operation for the disk images is a bit backward.
But that anyone would prefer Windows-style installers, or even Mac OS X .pkg files, to the simplicity of just putting your application where you want it, I don't understand.
Even a "big" application like Photoshop could (and probably should) be simply on the CD-ROM, and you'd just drag it to your Applications folder, IMHO.