I hate binhex!

File formats and associated fiascos	Binhex	MacBinary II
Step 1: Download file	Binhexed files are always more bloated versions of the original file at a ratio of usually around 3:4. So they take that much longer to download, wasting everyone's time, bandwidth, and patience. Just imagine the savings in network traffic if the files were left at their normal size..	MacBinary files are the same size as regular since they're just both forks of the file, enclosed in one fork. So, they transfer in the normal amount of time.
Step 2: Interpret/convert incoming file	This can either be done before or after the transfer is complete. But with binhex, even if the program DOES interpret the file on the fly (which is rare), it's not like it cuts down on transfer time or anything. So the way used most (both for reliability and freedome of download software) is to convert afterwards with Stuffit Expander. This also raises a chicken and the egg situation. How do you de-binhex stuffit expander if you've gotten it off the net? I've seen it come up more times than I'm willing to count, and it's going to keep on happening until people stop using stupid binhex all the time. The second part of this step that is annoying is that like the time it takes to transfer, it also takes far too long just to convert it when you have it already on your drive...the waiting involved in these steps is intolerable.	MacBinary can also be interpreted during or after the transfer. And even though most web browsers currently don't interpret it on the fly (Internet Explorer is the only one that does as far as I know), FTP clients do. Macbinary information is also automatically encoded if the server you're downloading from is a Mac (without the need to add the .bin extension to the end of the file). If you need to interpret it after the download though, it's still not as bad since it takes a fraction of the time compared to binhex.
Step 3: Decompress file	This is the step where binhex and macbinary are equal...well, almost. If you're decompressing from files converted after download, the amount of disk space used can be astonishing with binhex..especially if it's a large file or files. 15 meg stuffit file? Say hello to using up 20 extra megs (or more if the dipweeds that encoded it binhexed it TWICE...which has been done by apple and a bunch of other big companies..like netscape...and microsoft) to actually get to unstuff the file. Macbinary is at least predictable in this area. What it is, is what it is. Even if you have to interpret it after the download.
Conclusion? Binhex sucks. Macbinary should be used for all core internet storage/transfer of Mac files. All the Mac client software should interpret incoming MacBinaries so none of us need waste time or disk space having to do it afterwards.

The whens, whys, and how muches of my binhex hatred.

One of the most annoying things about using a Mac on the internet, is dealing with BINHEX. It's everywhere, and I HATE it.

I mean, if all servers still transfered at 7 bit there would still be REASON to use such a dippy format. But they don't. They transfer binary at 8 bit just fine now with http, ftp, gopher, dcc and any other protocol you want to put on TCP. So there's no more damn reason to use it! AAAGH!
Now you're probably wondering, WHY I hate binhex so.. Well, I'll tell you. It's because, it adds so much annoyance to the process of downloading files. It's like if you were only able to start your car by using a hand crank out in front, to turn the key that you've already stuck in the ignition. Here is a demonstration table of events that take place using binhex, and macbinary:

File formats and associated fiascos Binhex MacBinary II
Step 1:
Download file Binhexed files are always more bloated versions of the original file at a ratio of usually around 3:4. So they take that much longer to download, wasting everyone's time, bandwidth, and patience. Just imagine the savings in network traffic if the files were left at their normal size.. MacBinary files are the same size as regular since they're just both forks of the file, enclosed in one fork. So, they transfer in the normal amount of time.
Step 2:
Interpret/convert incoming file This can either be done before or after the transfer is complete. But with binhex, even if the program DOES interpret the file on the fly (which is rare), it's not like it cuts down on transfer time or anything. So the way used most (both for reliability and freedome of download software) is to convert afterwards with Stuffit Expander. This also raises a chicken and the egg situation. How do you de-binhex stuffit expander if you've gotten it off the net? I've seen it come up more times than I'm willing to count, and it's going to keep on happening until people stop using stupid binhex all the time.
The second part of this step that is annoying is that like the time it takes to transfer, it also takes far too long just to convert it when you have it already on your drive...the waiting involved in these steps is intolerable. MacBinary can also be interpreted during or after the transfer. And even though most web browsers currently don't interpret it on the fly (Internet Explorer is the only one that does as far as I know), FTP clients do. Macbinary information is also automatically encoded if the server you're downloading from is a Mac (without the need to add the .bin extension to the end of the file). If you need to interpret it after the download though, it's still not as bad since it takes a fraction of the time compared to binhex.
Step 3: Decompress file
This is the step where binhex and macbinary are equal...well, almost. If you're decompressing from files converted after download, the amount of disk space used can be astonishing with binhex..especially if it's a large file or files. 15 meg stuffit file? Say hello to using up 20 extra megs (or more if the dipweeds that encoded it binhexed it TWICE...which has been done by apple and a bunch of other big companies..like netscape...and microsoft) to actually get to unstuff the file.
Macbinary is at least predictable in this area. What it is, is what it is. Even if you have to interpret it after the download.
Conclusion? Binhex sucks. Macbinary should be used for all core internet storage/transfer of Mac files. All the Mac client software should interpret incoming MacBinaries so none of us need waste time or disk space having to do it afterwards.

So with all this going against the binhex format, why is it still the most common form found for Mac files to be in? I have no idea...but there are several possibilities to choose from:

People are stupid.
People are lemmings and will do anything that all the rest of them are doing.
People don't know any better.
People are stupid.
Computers are actually behind the whole thing, resentful for the Mac's ease of use and people in general.
There is NO..rule 6.
Mac users want to be like ibm users and torture themselves with backwards-ass methods of doing things.
Bill Gates is actually behind it all, secretly influencing the use of binhex to forward the interests of his own company.
People are like, deprived of donuts or something..which distracts them to the point of continuing to use binhex when it's not necissary.
People are stupid.

For other complaints, back up a page.

Created June 10, 1996