Well, for some folks it works fine on the internet as well:

http://www.mail-archive.com/fossil-users@lists.fossil-scm.or...

tl;dr: sqlite.org and fossil-scm.org run using a simple HTTP server via inetd and some parts of the website are CGI scripts. In 2010 they served over a quarter million requests per day on a tiny VPS with only 3% CPU load.

I run my entire web site on CGI scripts invoked by Apache. I really don't get the hate for it. It's extremely convenient and works great.

Same here. And to get the flame bait machine started, we even do it in Perl!

So I've been curious about this; Nimrod has some SCGI libraries and the like built in, but I didn't know whether that would be good enough for real world usage without building a concurrent application server into my App itself. How does it handle multiple requests at once without impacting performance badly? I know that's a noob question, I struggled to find good information on SCGI/CGI for today's use cases, so I sort of wrote it off as too hard basket...

Shhh! You're on Hackernews man...

CGI (when used with suexec) is still the tool of choice for your usual low-coat shared webhosting provider, and it's still good enough if all your customers want to do is deploy Wordpress, phpBB and maybe some custom PHP and Perl CGI scripts.