Chris M. wrote in post #1018217:
For most application's that's true, but a couple of Apple products on
the Mac App Store (e.g. Xcode, OS X Lion) only give you an installer,
which you have to run manually. These products need to write files
outside of /Applications, and the Mac App Store can't do that by itself.
You mean the Mac App Store WON'T install outside of /Applications. This
is by design.
Besides, how is this drastically different than installing Xcode before
it was on the Mac App Store? You would download the Xcode installer and
then run the installer. The Xcode installer includes multiple
applications. There's Xcode, Instruments and an array of other utility
apps. If Xcode where to be installed like any other Mac App Store app
then each individual app would have to be installed separately, which
would be a PITA.
I somewhat understand the concern about needing to keep the installer
package hanging around on the drive. However, I don't see another way to
provide delta updates for a tool suite like Xcode. Any system capable of
running the latest version of Xcode most likely has a fairly substantial
amount of disk space anyway. It'll get to a point where we won't even
think about a 3 or 4 GB file. It'll just be another one of the already
millions of files on our drives we don't think twice about.
On Mac OS X there has always been two basic types of application
installations. Some apps don't need an installer package, some do. The
difference with the Mac App Store is that in order for third-parties to
be able to sell through the Mac App Store the app must support the
"drag-and-drop" style application install. This is safer, and easier to
Third parties building apps that require installer packages will have to
resort to traditional methods of distribution. In some cases (e.g.
iWork) the requirement for an installer package can be eliminated by
separating the suite into individual applications.