I just knew you'd latch on on to the "floppy" bit and ignore the DVD-ROM and network share parts. So, answer me about the other two, since they're still current and valid in this day and age.
You can't be serious! Do you think a floppy is faster that a DVD or a network connection? I concentrated on the floppy because it is the slowest of the three. ROFL!!!
No matter what the storage medium is, it takes less time to load something that is 4K than load an entire compressed EXE (which is usually much
larger than 4K). It is a matter of size and when it comes to loading something, smaller is better. A compressed EXE is not smaller than an uncompressed EXE when it comes to loading. The compressed EXE is actually larger.
Oh, and don't give me any of that garbage about "load times are irrelevant", because they're not.
Indeed, this is why you should choose the smallest possible thing to load (4K) than do like you are suggesting and choose the largest possible thing to load which actually works against the way the OS is designed to work.
You need to remember why executable compressors were first developed: to save space. That is it. Once drives hit the 850MB range, EXE compressors became highly irrelevant and developers moved to new marketing gimmicks
to push EXE compressors on programmers.
In the old days (100MB or less hard drives), space was always at a premium on your EU's system and you could not count on your EU using something like Stacker, DoubleSpace, DriveSpace or DIET to try and "stretch" the room on the storage medium. By developers reducing the size of their EXEs, your EU could fit more software on their system without having to rely on third-party compression software to compress the entire drive.