Python:

You usually have the entry point of the program at the end of the file. (Because if it calls any function defined in the module, it has to occur after those functions in the sources.) I hate it when you have to spend time looking for the entry point of a program, so I always have a simple main.py file with: def main(): ... if __name__ == '__main__': main() When an exception is raised, it can only be catched by the main thread. Or something like that. Destructors are quite useless, because when written in Python they may break garbage collection IIRC. I've never figured out how relative imports work in Python 2. I'd like to see more collections in the standard library. For example: linked lists, thread-safe collections, ...

Java -不支持语言级别的组合

JavaScript

Function object syntax: f = new Function( "foo", "bar", "return foo+bar;" ); (It takes n arguments, the first n-1 are arguments for the function, then nth is the actual function, in string form. Which is just silly.) Function arguments can be repeated. f = new Function( "foo", "foo", "return foo;" ); The last repetition is the only one ever used, though: f( "bye", "hi" ) // returns "hi" f( "hi" ) // returns undefined E4X should just die. My users are always complaining that it doesn't work the way they think it will. Let's face it, when you need a page and a half of psuedocode for a setter, it's time to rethink things. A standard notion of stdin/stdout/stderr (and files!) would be nice. null != undefined It's irritating to have to handle them both. Sometimes it's useful, but most languages manage to limp along fine with one.

PHP:

1)强迫我创造不必要的变量:

$parts = explode('|', $string);
$first = $parts[0];

2) lambdas的实现如此蹩脚，它大致相当于使用eval()，而且如此糟糕，我从未使用过它(参见http://www.php.net/create_function)。

3) try/catch系统只能捕获大约80%可能发生的错误。

4) Regex支持和lambda支持一样蹩脚，因为它必须在常规字符串中编写，这使得最难学的编程工具之一变得困难了三倍。PHP应该是一种“简单”的语言吗?

5)没有办法安全地从$_POST中取出东西，而不写两次或构建自己的函数，或使用'@'操作符:

$x = isset($_POST['foo']['bar']) ? $_POST['foo']['bar'] : null;

6)额外答案:“@”。如果你懒得写正确的代码，那就添加'@'，这对以后调试你的代码的人来说太糟糕了。

C(好吧，这不是我最喜欢的，但当时还没人做过。)

套接字库语法。 没有函数重载。 c风格的字符串。 缓冲区溢出。 神秘的语法。我不知道有多少次我查到像atoi这样的东西，拍着我的额头，然后大喊“当然!”

编辑:如果我使用更多的库代码(就像我用套接字做的那样，但那些特别糟糕)，我可能会想出更多的库代码，但我已经觉得我选择C语言是在作弊。许多语言的存在只是为了取C语言的好的部分，取代坏的部分，这有点像在徒劳无益。

再给c++投一票…仍然是我最喜欢的语言，有几个亲密的追随者——C和Python。以下是我目前最讨厌的名单，排名不分先后:

Plethora of integer types inherited from C - way too many problems caused by signed vs. unsigned mistakes Copy constructors and assignment operators - why can't the compiler create one from the other automatically? Variable argument madness - va_list just doesn't work with objects and I'm so sick of problems created with sprintf(), snprintf(), vsnprintf(), and all of their relatives. Template implementation is required to be fully visible at compile time - I'm thinking of the lack of "export" implementations or at least usable ones Lack of support for properties - I want to have a read-only member like "a.x" that can be read publicly and only assigned internally. I really hate the "val=obj.getX()" and "obj.setX(val)". I really want properties with access control and a consistent syntax.