Earlier quoted context omitted.
The problem with "you can go fix it if you want" is that the barrier to "fixing it" is very high, even with such great things as #debian-mentors. I fully understand the need for all the process and policy but it can be very difficult to get things fixed in Debian without talking to the right people or attending the right conferences.
Agreed, what you can do on first contact, is not always what you would like to do. I didn't mean it's the only and single way to change something in Debian... the subtle of my message was, that complaining outside the project, does not help to anybody, and forms subjective opinions on persons that didn't have them. Today, someone at $work that never did write perl, was complaining on perl and Larry Wall just for laug…
I dunno, I'm pretty sure that this is a form of the "appeal to authority" logical fallacy - i.e. person X has achieved less than person Y, therefore their opinion is invalid. Perl has problems like any language has problems, but sometimes it's the right tool for the job.
I know the kind of person who derides languages for whatever reason - sometimes I am that person. It's fun to bash PHP, C#, Java, Ruby, Perl, Python, even Shakespeare Programming Language [1] but at the end of the day they're a means to an end, not an end to themselves.
Some comments at Linux.conf.au recently made me aware of platform/language shaming. It's not a good thing and I'm working to stop doing it.
1: http://shakespearelang.sourceforge.net/report/shakespeare/
\ VB6 can bugger off