All good points, but personally I think that there are other "reasons" why managers who are selecting technologies may prefer $other_tech to Perl, and they are reasons only in double quotes because they're all mostly related to FUD and misinformation anyway, so that activities like Obfu and Golf may be rather contribute to the phenomenon or be taken as an excuse for the "Oh, Perl is unreadable" pseudo-argument and I don't know how much they would weight in the overall bad reputation that Perl gets in some circles. I expect that the tons of examples alleged to be productive code but sporting bad programming habits that lie around in the net are much worse in this sense. OTOH that unreadable code is google-able doesn't mean that readable one is not: indeed it's easy to show that the latter overnumbers the former by large. If that is their argument, it's easy to counter it.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.