From: Thomas Hurst Date: 2002-10-01T21:00:53+09:00 Subject: Re: Ruby, Client/Server and Web Application * MikkelFJ (mikkelfj-anti-spam@bigfoot.com) wrote: > It has decent CGI Not much use for much more than trivial scripts. It's quite easy to push execution time past half a second because of startup costs. pperl can be useful in reducing startup costs for Perl scripts; anyone want to look into producing pruby? :) And did I mention I'm not keen on cgi's API? :) > and, I belive, Fast-CGI support. There is mod_ruby, mod_ruby needs to support more servers. Apache 2, IIS, thttpd, even CGI. It kinda sucks having one API for CGI, one for mod_ruby, another for FastCGI.. blegh. > and embedded Ruby (eRuby) for Apache. Isn't eRuby a generalised embedded ruby preprocessor? What's so Apacheised about it? > So you can certainly do web. Don't forget application servers. They look rather interesting :) > Yet you frequently see Ruby people using PHP for Web because they are > pragmatic and sometimes find other tools useful too. Yes. It's just so damn easy to get hold of. Not having a minimum startup cost of 0.1s is nice too :) The language is awful, though.. eww. -- Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/ - Work is the curse of the drinking classes. -- Mike Romanoff