Actually, most of them nowadays would contain i386 and x86_64 code, but for most big software the major contribution to size is (as with games) assets rather than binaries.
For instance, Acorn has a dual-arch binary weighting 5.5MB, or about 15% of its total. A single-arch binary file would shave about 7% off the application. Not exactly significant.
For Address Book, the dual-arch binary is 319K (out of 20MB), Adium packs two architectures in a 3.9MB binary (about 5% of the total package size), …
> Stuff on OS X just takes a _lot_ more disk space. Arch Linux's package for emacs (http://www.archlinux.org/packages/extra/i686/emacs/) is 89.7MB installed, whereas your post indicates that on OS X emacs consumes 133MB.
Not all of the difference comes from the binary by a long shot: the binary itself is 33MB and triple-architecture, even single-arch the package would be around 110MB. The Arch Linux package might not contain compiled elisp files for instance.
For instance, the VLC 32/64-bit package for Intel on OS X, which is the first linked download and the one users are mostly likely to click, is ~40MB whereas the Windows download is ~20MB (the OS X 32-bit only is ~24MB). The Arch Linux package is a 6MB download.
Stuff on OS X just takes a _lot_ more disk space. Arch Linux's package for emacs (http://www.archlinux.org/packages/extra/i686/emacs/) is 89.7MB installed, whereas your post indicates that on OS X emacs consumes 133MB.
So really the space requirements will even less for non-OS X users.