i owe my career to Perl. I was a liberal arts major and in 94 there was a language i could use because it was designed for folks who needed to use what they co

i owe my career to Perl. I was a liberal arts major and in 94 there was a language i could use because it was designed for folks who needed to use what they could understand at any time without knowing it all, with the aim of building cumulative mastery. Kind of like unix, learn useful things and piece them together. This was by design as Wall treated Perl to be acquired the same way we learn a spoken language. That is why we have really good and really bad perl5 code out there. I remain a learn-by-debugging programmer instead of a play-with-a-lang-from-squareone type. My pattern is, if there is a compelling app i'll learn the language/framework. (bonus points for pg support.). Bricolage got me into HTML::Mason and mod_perl. Discourse got me into ruby. Actionhero got me into nodejs. Flask in python. PHP became unavoidable (sigh). I find PHP to be my language of "wow i can't debug this at all" but good php is really good - the same way perl detractors see perl. Low barrier to entry (perl php browser js) is a gift and a curse, but a good dev can make anything a joy to use. With perl anything done after the faux-OO world blew up takes a lot of effort to understand even though it should be the reverse. I still use perl for scripting in linux but have avoided it for new apps. After a lot of nodejs async, I am tempted to use Mojolicious and avoid the Mooseshaving