> AWK _should_ have been used in place of PERL (yuk) > and could have been used rather than js as client-side or > server-side CGI.
Well, certainly JavaScript is junk, and I'd have quite liked awk to be used for client-side scripting too -- awk is a lovely language, I use it extensively in Unix. For a long time my opinion of Perl was 'yuck!' too :) However, one of my clients uses Perl extensively in their product, so I have to work with it -- after a while it grew on me. It wouldn't be very good for client-side stuff (far too complex, I fear), but it is very nice for CGI. To be honest, I don't see what difference the language used for CGI scripts makes; some of those running on my router are in the Bourne shell, some are in Perl... Some I wrote in C, but for general scripting something like Perl is excellent. I have a bandwidth monitoring system set up with the pages and graphs generated through Perl (i.e. /config/cgi-bin/bandwidth-history-10m.jpg is actually a Perl script). Come to think of it, I don't think JavaScript is used at the server side as an embedded language -- if it is, it's hardly extensively. VBScript is (ick!), on ASP servers, and PHP is apparently quite good. I've never looked at embedded Perl (Apache can apparently do this) as opposed to a Perl CGI program though. I know the Department of Computer Science here uses Java servlets to generate a fair number of their dynamic pages, and that works quite well. Java itself is fairly well-suited to that environment, although I might have been tempted to use Perl myself. Regards, Ben A L Jemmett. (http://web.ukonline.co.uk/ben.jemmett/, http://www.deltasoft.com/) To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
