The purpose of the project was to enhance and consolidate the feature set (differeent clients had evolved slightly different functionality over the years) for maintainability, provide per virtual-host configurabiliy, and make sure the scripts could be run persistently (for efficiency) while still enforcing the strict pragma for security.
Why perl, instead of witango? Sometimes clients want to take the development site with them, and the light-weight CMS we provide is often a selling point for getting the job. It's just easier to provide a perl script than convince them to run witango.
Now you can (and I did) pack a lot of functionality in 12 kB of perl, but it sure took me a lot longer than I expected, and way longer than the equivalent job in Witango. Environment, scopes, caching -- sure is nice to have that handled for you. And having pre-built metatags instead of building your own subroutines is real nice.
Sometimes it would be nice to have perl's string manipulation capability in Witango -- the metatags don't compare. And it would also be nice to have a metatag equivalent of File::find for traversing the file system. But Witango rocks!
bill
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
