按最讨厌到最不讨厌的顺序排列。

1.) Backwards compatibility police. Yes backcompat is a strength but Perl 5 takes it too far. Now we don't really even get new features in our language without having to enable them explicitly. I'm much prefer the inverse, if a new feature causes a problem let me disable it or enforce old behavior. e.g. perl 5.10 added say I'd rather have no feature 'say' if I have my own say implemented than have to put use feature 'say'; or use 5.010; also if 5.8 worked but 5.10 didn't. I'd rather have use 5.008; to restrict my code to only use features available up to and including 5.8 if no use version; was defined then it should be defaulted to whatever version you're running, and a recommended practice of not to restrict it unless you have to.

2)。过度的样板。

#!/usr/bin/perl
use strict;
use warnings;
use utf8;
use autodie;
use English '-no_match_vars';
use 5.010;
package Package::Name;

BEGIN {
    Package::Name::VERSION = 0.1;
}

sub somesub {
    my $self = shift;
    my ( $param1, $param2 ) = @_;
}
1;

现在你可以开始编码了。这不会因为第一条而改变。当然也有一些捷径，比如使用common::sense;或者使用modern::perl;这将缩短上面的内容，你可能需要一些稍微不同的模块或pragma。但因为第一条，我们永远无法把它降低到。

#!/usr/bin/perl
package Package::Name 0.01;

sub somesub ( $param1, $param2 ) {
}

一些模块正在帮助这一点，在5.0.12中有新的包版本，它完全允许这种语法，尽管我认为它需要使用5.012;首先，和Method::签名，但它永远不会完全解决，(在语言)。

3)。糟糕的变量选择

吸吸文件

#!/usr/bin/perl
use strict;
use warnings;
open my $fh, "< foo" or die $!;
local $/; # enable localized slurp mode
my $content = <$fh>;
close $fh;

WTF是$!和美元/ ?重写为易读。

#!/usr/bin/perl
use strict;
use warnings;
use English '-no_match_vars';
open my $fh, "< foo" or die $ERRNO;
local $INPUT_RECORD_SEPARATOR; # enable localized slurp mode
my $content = <$fh>;
close $fh;

不要忘记，如果您不想受到性能影响，'-no_match_vars'必须存在。

不直接创建匿名标量怎么样?

#!/usr/bin/perl
my $scalar_ref = \do{ my $anon_scalar };

他们就不能想出点什么办法吗?

#!/usr/bin/perl
my $scalar_ref = <>;

哦，perl是线程不友好的，因为所有的变量(包括特殊的变量)默认是全局的。至少现在你可以使用我的$_;对其词法作用域，并对其他词使用local。

4.)非常难看的语法

MooseX::Declare是一个更好的语法。我也希望->被替换为。(个人喜好不太重要)

5)。太多的TIMTOWTDI或太多的最佳实践似乎你必须读3-5本书才能弄清楚你应该如何做事情。

6)。以前的(不再适用)。Un-sane版本。5.10.0有新功能5.10.1的新功能没有设定时间，直到下一个版本。现在是每年一次的特性发布，每季度更新一次。

7)。象牙塔视角。社区问题，似乎是许多开发者想要设置更高的准入门槛，并认为可以不尊重n00b(或任何不同意他们的人)。

8)。疯狂的版本号/字符串Perl有浮点版本号，它们很难看。开发人员不知道并不是所有的下游处理版本比较的方式都是一样的。不是语言问题

0.012 # simple
5.012001 # semantic 
4.101900 # time based + version (for multiple versions in a day)
0.035_002 # prerelease

所有有效版本的perl..我们就不能用…

0.12 # simple
5.12.1 # semantic
20100713 # time based (just use the date and be careful not to need to release more than 1 a day)
0.35-beta2 # prerelease

除了

9)。升级后没有明显的方法重新安装所有XS模块

Perl 5:

All the really good stuff nowadays seems to require mod_perl, which has low availability everywhere I want to go. Some really incredible functionality can be encapsulated in modules, but what is under the hood is often fragile or frightening: source filters, typeglobs, whatever Moose is doing... DateTime is brilliant but still made some very bad design decisions (not returning a stopwatch duration when subtracting two DateTime objects) Dual-lifed modules in core and on CPAN still cause conflicts module authors still put interactive stuff in their module configuration scripts so that they can't be automatically installed

Haskell:

空间泄漏——懒惰的默认代价——也许代价太高了? 甚至像head和tail这样的纯函数也会调用错误并引导您进入IO。 fail from Monad -带回MonadZero。 Num类-(+)应该在AdditiveGroup或类似的类型中。 那个单子不是一个应用程序。

Common Lisp

conditions aren't classes (since classes came later), even though their interface is almost identical some of the names are just weird, e.g., flet / labels (only difference: scope), and defvar / defparameter (only difference: behavior when already defined), or any of the bit-twiddling functions (dpb, ldb, etc.) packages are ... really hard to get right -- every time I think I understand them, they don't do what I want built-in data structures and functions aren't as generic as they could be (e.g., why can't I define my own hash function portably?) multiple namespaces for functions, variables, etc. (I'm not opposed to this in principle, but CL made it too complex; Norvig has said he can't tell from the spec but there appear to be at least 7 namespaces)

Python:

1) It's a scripting language and not a fully compiled one (I'd prefer to be able to compile binaries—I don't care about bytecode). This is very annoying if I have to use very many libraries (i.e. everyone who uses my program has to install all the libraries, and this basically means no normal people will be able to, or have the patience to, properly set it up—unless I do a ton of work that should be unnecessary). I know ways to make binaries, but they don't always work, and I'm guessing they bundle the interpreter in the binaries anyhow (and I don't want that). Now, if I could get a bytecode compiler that would include copies of all the files that I imported (and only those) to be placed in my program's folder, that might be a suitable compromise (then no one would have to download extra libraries and such). It would also be nice if the compiled python files could be compressed into a single file with one specified as the file to run the program before this is done.

2)有时看起来有点bug;有几次，应该工作的代码根本没有工作(没有程序员错误)，特别是与“from moduleX import *”和其他导入相关的问题有关的代码，以及一些与全局和局部变量有关的问题。

3)最大递归深度可以更高。至少有一次，我觉得我需要它去更高的地方。

4)没有switch语句(更不用说允许数字、字符串和范围的语句)

5)新版本的Python似乎取消了很多有用的字符串操作，而且似乎没有简单的文档说明如何在没有它们的情况下做同样的事情。

6)强制自动垃圾收集(我希望能够手动执行，尽管不一定强制执行)。

7)没有预先制作的定时器类没有使用GUI(好吧，可能有一个，但在我所做的所有搜索之后，它肯定不方便找到!我确实找到了一些东西，但当我尝试时，它根本不起作用。)所谓计时器，我指的是每隔x秒执行一个指定函数的排序，并能在需要时关闭它，等等。

8)社区里举例的人很少告诉我们他们导入了哪些模块，以及他们是如何导入的。

9)与Lua集成的支持并不多。

10)似乎没有办法向一个类的特定实例(而不是整个类)添加一个额外的函数，除非你动态地向该类添加一个对象变量，该对象具有所需的函数(但仍然，你必须为此创建另一个类)。

Python

没有名称空间。 伪私有属性/名称混淆(主要使用getattr)。 文件路径操作分布在多个模块中。串在一起的os。路径调用是丑陋的，难以读取，并且在大多数情况下违反了DRY。常见的文件路径操作仍然没有方便的函数，比如获取目录下的文件列表。修复此问题的路径类型模块被拒绝。

([f for f in os.listdir('/file/path') if os.path.isfile(os.path. isfile)加入(/文件/路径,f))))

Python文档(我非常、非常、非常感谢有文档，而且它的格式很好，但我讨厌费力地在5000行快速入门使用示例中找到特定模块的单个函数文档(我正在查看optparse和logging))。内置类型在近10个不同的地方被零碎地记录。