Monday August 25, 2003
misunderstanding the technology
I was deeply saddened by a review of mod_perl
on cpanratings. to quote part of it
"the only thing that mod_perl has going for it is that it is widely known and a lot of material and modules have been written for it.
Architecturally, it's a poor choice for building dynamic web applications. The problem is that the same process(es) are serving simple files as well as generating dynamic pages. This means that while images, etc are being served to clients by apache processes, all of the memory consumed by the Perl interpreter is essentially wasted.
There is a binary optimized, Open Market standard that was designed for just this - FastCGI.
It is for these reasons that I hold my opinion that Apache/mod_perl will be one day seen in the same light as Sendmail - filled with the cruft of years of creeping featuritis.
now, to be fair, the criticisms he raises inbetween are valid - most are part of the price you pay for the technology. however, what really irks me is that the myth that mod_perl and FastCGI (or anything else, for that matter) are equivalent technologies - it's the access to the Apache API in Perl that makes mod_perl unique, something that is simply unparalleled anyplace else.
mod_perl offers complete access to the Apache C API in Perl
it's the thought that people don't understand this, despite all the literature and advocacy out there, that really saddens me.