I mostly lurk and seldom reply to anon.
But I'm compelled to say
Well Spoke, and thanks for the forethought.
Perl was the reason I started wrapping my brain around regular expressions. Later in the 90's I build complex backends using cgilib. Tried a few frameworks like mason..... I became a perlOphite for all the sentiments you expressed so well.
The ease of cpan, of quickly manipulating DBI tables, so many reasons why it, and its attitude,
always works for me. Off a CLI, wrapped up in a shell script, part of a larger pipe; I just cannot imagine using another interpreter as painlessly.
Specially for admin stuff and my personal libs of
files/data which require maintaining.
That said, were I a manager today I'd see the
sense in concluding that python, ruby, a compiled
lang, .... would have a better outcome from the
devs; despite my personal aversion for each of them. Enforcing Delimiters does not good code guarantee and makes editing others' code in vi more tedious (or macro'd). Maybe if I were an IDE
type of guy.
I found my time spent adopting/trying/using rails/passenger/gems/mongrel less warm-n-fuzzy
than squating in the cpan/perlmonkworld camp
I feel Perl epotimizes the LAMP stack, the finishing touch of what, for me, was a process
(mentioned earlier) of learning OS as much as CS
and appreciating the many ways to do one thing.
But not all programmers feel drawn to broader systems and from that narrower perspective more structure makes infinitely more sense.
For those who might say perl is a hackers language
I would heartily agree. Its where it's genius lies.