good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
The attitude around work is strongly "don't use Perl", in an informal way. It's not an official position, and there's been no talk that I know of about not allowing Perl in the workplace. There are a couple of key scripts that can't be replaced until we move completely into a container-based deployment model. So Perl is officially supported, for now. That doesn't stop people from putting up style guides for various tools and toolsets in the company, and having a page for Perl that simply says:
It's hard for me to rise above this attitude problem. They've gotten it stuck in their heads that Perl is just a spaghetti has-been language and that Python is "all that". I do what I can... but we all know that story. I write good Perl, I instruct and inform people of good Perl that I've written that does useful things. But I have a problem: I identify with Perl. I care about it, because it not only was part of my career identity for 20 years; I LIKE Perl and think it does many things better than other languages. I'm biased. And it offends me that others are so openly contemptuous. I need thicker skin. What's the best way to get thicker skin about Perl's unpopularity? I was having an okay day until I saw this blatant display of contempt and smugness. In reply to Perl Contempt in My Workplace by rje
|
|