This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
This my question does not seems to be technical, but I feel it it. I am a Java developer with Java web programming skills, but I wan to know the reason why the people in charge of Javaranch using a *.cgi platform for the site. I am not criticizing them but I want to add to my knowledge, but in the first place what is this *.cgi all about
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Henry Wong: I actually feel incredibly old here.
You probably are :-) But ... my first internet access was email only, so in order to retrieve files via FTP, I had to go through the motions of using FTPMail. Ah, the joy of downloading a dozen 64KB chunks of an 800KB sized file ... over a 2400 Baud modem, mind you!
This is not at all my earliest network use, but it's the one that strikes me the funniest now. I remember when Mac System 7 came out (like all Apple OSs of the day, it was FREE!) I was incredibly excited to get it. On the actual day it was released, I got it via FTP to a local server at MIT. Then to get it on my Mac Plus at home, I set things up to download the three or four 800K disk images via my 2400 baud modem, overnight.
I remember having to back up and delete a bunch of stuff to make room for that massive 2 or 3 megabyte download! It was a huge project, downloading the images and making 800K installer floppies, then upgrading the system.
My earliest memories of network programming was on OpenVMS (back when it was still VAX/VMS) using a VMS messaging protocol called mailboxes (nothing to do with email). I used it to create a two-player implementation of a board game named Isolation.
Originally posted by paul wheaton: You youngsters and your high falootin modems. You never had to deal with manually dialing a rotary phone and shoving the handset into an accoustic coupler modem for the whopping speeds of 110 baud.
i distinctly remember using an accoustic coupler. My dad brought home a dumb terminal (vt-52? i think?) one day, and we called his work computer. it had TWO lines you could call in on, and we (the kids) could only use it if the other line was not in use (something about people wanting to WORK having priority).
I also remember whistling into the thing to get weird characters to display on the screen. it was fun. of course, i was about 8.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Heh - I was talking the other day about how my coding quality was better back in the day when I had to hand in my program on cards and get the results back the next day. There is nothing like hearing 1/2 a day later that your program didn't even compile to make you really debug your program before submitting it.
I don't even remember why we were still using card readers back then - certainly dumb terminals were cheap enough that we could have had our own. I think I only had to endure about a month of working with cards thank goodness.
I can also remember working in an office where we had a dozen dumb terminals set up next to our Windows 95 computers. At least once a week some idiot would send a ~1 Mb email company wide, and all the PCs would try and download it from the Exchange server over ISDN simultaneously: instant lockup for 2 hours. So everyone would swap to the dumb terminals while they waited for the Windows boxes to start responding again.