Re^3: Perl in the Enterprise

[Anonymous Monk]

Actually I'm working somewhere we we have mission critical perl applications, and they were not written by experienced programmers, particularly experienced programmers. The system provides important information for the aviation industry.

I've come on board as an experienced perl developer to move from an evolved system (with some OO and some basic good practice) to a measurably robust and garunteed 24/7 system with 0 downtime and the ability to scale up to more projects.

Perl works very well in this job, the hard bit is the development process and defining the requirements. This applies to all languages, and I doubt very much a Java project would be an iota easier to refactor or maintain if developed in the same way.

Also - this is 90% non-web, a mix of PHP and Perl are on the web, but the data feeds and heavy lifting are all perl, so the CGI era crap won't stick.

I've been integrating systems using perl for about 6 years and can count the 'cgi scripts' I've written on one hand.

Formatting added by GrandFather