Comment by codingdave

Comment by codingdave 16 hours ago

Keep in mind that in ye olden days, email was not a worldwide communication method. It was more typical for it to be an internal-only mail system, running on whatever legacy mainframe your org had, and working within whatever constraints that forced. So in the 90s when the internet began to expand, and email to external organizations became a bigger thing, you were just as concerned with compatibility with all those legacy terminal-based mail programs, which led to different choices when engineering the systems.

liveoneggs 15 hours ago

This is incorrect

Reply View 3 replies

kstrauser 11 hours ago

Are you certain? Not OP, but a huge chunk of early RFCs was about how to let giant IBM systems talk to everyone else, specifying everything from character sets (nearly universally “7-bit ASCII”) to end of line/message characters. Otherwise, IBM would’ve tried to make EBCDIC the default for everything.
For instance, consider FTP’s text mode, which was primarily a way to accidentally corrupt your download when you forgot to type “bin” first, but was also handy for getting human readable files from one incompatible system to another.

Reply View | 2 replies
- liveoneggs 9 hours ago
  
  I had a pre-'@' email address and it was able to communicate all over the world.
  
  Reply View | 1 reply
  
  kstrauser 8 hours ago
  
  My first reading was that you were disagreeing with the bits about email worrying about compatibility, and that part seemed reasonably true to me.
  As to the other bits, I think even in the uucp era, email was mostly internal, by volume of mail sent, even though you could clearly talk to remote sites if everything was set up correctly. It was capable of being a worldwide communication system. I bet the local admins responsible for monitoring the telephone bill preferred to keep that in check, though.
  
  Reply View | 0 replies