Hacker News new | past | comments | ask | show | jobs | submit login

Well, not really. I guess they got sick of the same how do I write a CGI? questions again and again.

Perl was popular for the web for one reason and one reason only: It was the only dynamic interpreted language that was widely available, and it was widely available for the simple reason that your sysadmins had already installed it for their own use. Back in the early-mid 90s, you got C, C++ (maybe) and FORTRAN compilers on the typical institutionally-owned (university or corporate) large, Internet-connected Unix box. The choices for any ordinary user wanting to put something dynamic on the web were, umm, C and that's about it, or Perl. Lots of people got into Perl just for CGI like nowadays they get into Ruby just for Rails (or Tcl just for Tk).




You could have written your CGI scripts in Tcl too --- it was also dynamic, interpreted, and widely available. But Perl was better.


Perl had "better" regexp handling, certainly. But several major products such as AOLServer and CNET's StoryServer (which they later spun off into a separate company) were Tcl-based. Joe Hacker running a website out of his home directory at college wouldn't have seen them but Tcl was once a huge presence on high-traffic websites.

Incidentally back then Tcl was only really a presence on Sun kit... Perl was already everywhere.


One area where Tcl missed out was in terms of web servers. There were a number of proprietary ones that integrated Tcl as a server-side language (sort of like PHP), which, of course, is a much higher performing model than launching a CGI for each request. However, by the time those servers were open sourced (AOLServer), the PHP cat was out of the bag.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: