This is not a post to request changing to Java or anything. BUt with CGI how are servers keeping with this ever growing site? don't your servers ever run out of memory with each new request? Also out of curiosity have you noticed anything that CGI offers that isn't or could be better offered withs servlets and jsp? or anything that you like about CGI?
I don't really understand the first part of your question. You seem to be implying that CGI is (memory intensive / has memory leaks / is slow / ...?). However CGI stands for Common Gateway Interface - it describes an interface, not an implementation. How that is implemented, and the language that the clients are written is, is not defined (if they were defined, the interface itself may not be required). So it is quite possible to have a CGI compliant application and server which scales well (CPU / memory / TPS / ...). And going to Java (or Ruby, or any other language) does not automatically mean that we are going to get any improvement in scaling.
Which is not saying that CGI is better than Java - just that the fact that it is CGI does not automatically mean that it is bad.
Moving forward though - your question as to whether there is anything that CGI offers that couldn't be done with some other technology, or if there is anything we particularly like about CGI: No on both counts.
However you are sort of getting to a very frequently asked question: why are we using CGI (or why are we not using Java). So you might want to take a look at this.
Originally posted by Andrew Monkhouse: Which is not saying that CGI is better than Java - just that the fact that it is CGI does not automatically mean that it is bad.
In fact, CGI and Java aren't even mutually exclusive.
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