...I went looking for a Perl based CMS, hoping to leverage what I already know and ease the transition. What I found shocked me! There were tons of open source CMS packages written in PHP and Python, and little (that I could find) in Perl.
I get the impression that the PHP CMS applications outnumber the Perl ones as well (and it was in part some research into CMS apps. that fueled my interest in the mind share topic) though there are still a bunch of Perl ones to chose from. A search on http://www.cmsmatrix.org/ turns up over 20 that are written in or can be extended with Perl. (Try the same thing for PHP and you get over 120, whereas for Python there are fewer than 10. Of course a bunch of the PHP ones are close clones of each other.)
Further, where as Perl seemed to have the "here's the module, build it yourself", the others (especially PHP) were able to brag, "upload this one file, browse to it, follow the resulting install wizard!"...
The ability to easily (and securely) install Perl web apps without requiring shell access is indeed a weakness. This is particularly a problem for commercial developers of Perl web applications.
This is perhaps among the valid "technical" weaknesses that Perl has from the perspective of new web developers, and is along the same lines as a bunch of other points Bogart Salzberg made on this list earlier.
These problems are probably solvable with the effort of a handful of motivated developers.
Before anyone says "What about Mason!", let me say that "HTML::Mason" is a far cry from XOOPS...
As Dan Collis Puro pointed out in his posting on WebGUI, HTML::Mason really fits in at a different level. It's a templating library that can be used to build a CMS or whatever else. I wouldn't compare it directly to a CMS app.
-Tom
_______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
