explorador - 5:31 pm on Aug 22, 2013 (gmt 0)
Perl is far from dead.
I could talk about the many things I have implemented on my latest CMS and it would sound as I'm trying to sell a magical solution here. It just works for may diff scenarios including clients, crm-ticket-system, contacts, reservations, scheduled posts and publications, multi store inventories, even daily, weekly and monthly backups including keeping an updated backup server with everything ready in case server A crashes, and also backup to other places.
Have you seen webmasters struggling with settings, configurations and database issues while they move to another server? I'm not there any more, Perl allowed me a one install of the CMS with full multi site applications and full drag and drop, I mean, I just pack and go, no config needed ever. And when in need to modify some script or add some new feature I just have to update a single file, not one per site.
I even have implemented special cache features for both desktop versions and mobile versions of the sites. It's been a never ending adventure. Still remember when I was researching Perl and discussions about flat file systems vs full databases, most people told me my personal choice was wrong, well this thing is fast! I'm off databases. When MYSQL service goes down the sites won't work, my sites still go on.
Always try my best to stay away from special plugins, modules, etc. Always looking for ways to do things with just code so I'm worried free about what's on the server I'm moving in. Other than that I had to write some scripts to migrate 5 websites owned by the company I work for to get all that content on Drupal. Not funny but Perl saved the day keeping the urls, images, etc.
Perl is everywhere on my applications, even use Perl on my desktop computer to deal with many tasks when in need.
Ok that's long enough.