There's a level of Hell reserved for the person who incorporated the concept of "ASCII" and "binary" files into the FTP protocol and the Windows operating system - Come'on, it's all just bits, ones and zeros, people!

Hope you never have to work with VMS. Or pretty much anything besides Unix, actually. But there may very well be a level of hell reserved for people who create filesystems that have multiple separate ways to store data associated with a file, dub one of them the "data fork", and then proceed to store data in the others.

There's a level of Hell reserved for the person who incorporated the \r\n line feed on Windows platforms

No, that's standard-compliant behavior. There's a level of hell reserved, I'm quite sure, for people who decide to save one byte per line by ignoring bits and pieces of well-established standards such as ASCII. (Not that the folks at MS aren't guilty of things like that too, but we can't take the time to list those infractions here, and they aren't Perl-related anyway.) A Windows file you can just send straight out a socket, but a Unix-style file has to be munged to adhere to all the protocols when you send it over the network. (That's not why MS followed the standard, though; they didn't care at the time about networks; they just wanted to be able to toss a file at the parallel port and have the printer "just work" with no driver. Remember ASCII printers? Yeah. I even had one that did Extended ASCII. The output was barely legible, but hey, it worked.)

for(unpack("C*",'GGGG?GGGG?O__\?WccW?{GCw?Wcc{?Wcc~?Wcc{?~cc'
.'W?')){$j=$_-63;++$a;for$p(0..7){$h[$p][$a]=$j%2;$j/=2}}for$
p(0..7){for$a(1..45){$_=($h[$p-1][$a])?'#':' ';print}print$/}
[download]