PHP:

荒谬的assert()函数…它对里面的代码运行eval() ?>标签删除了它后面的换行符?! 奇怪的数字字符串处理(尝试将它们作为数组键) 令人痛苦的unicode支持似乎将不再被PHP 6解决 入门成本低意味着95%的人给PHP程序员起了一个可怕的名字——试图在这5%中找到一个人来雇佣是疯狂的。

我可以为Python添加另一个:

给定一个列表l = [l1, l2，…]， ln]，那么repr(l) = [repr(l1)， repr(l2)，…， repr(ln)]，但str(l) != [str(l1)， str(l2)，…， str(ln)] (str(l) = repr(l))。之所以这样做，是因为列表中可能有模糊的条目，如l = ["foo]， [bar，"， "]，["]， str(l)将返回"[foo]， [bar，]，[]"，这“可能会使用户感到困惑”。然而，这使得str不可能仅用于转储数据，因为list杀死了“仅以可读格式转储数据”。Augh !

C++

(除了lambda函数，我已经避免了Cpp0X中可用的东西)

不强制使用"this"访问成员变量，::GlobalFunction访问全局命名空间。 (更具体地说，算法中缺少lambda函数，将在0x thou中修复)中的所有内容 处理依赖文件/头文件和源文件 基本数据类型上的愚蠢名称(应该命名为uint8, int16等) const_cast功能

Ruby有许多与速度相关的缺陷，但我并不讨厌它们。它也有社区传福音过度的缺陷，但这并没有真正困扰我。以下是我最讨厌的:

Closures (blocks) have 4 different creation syntaxes, and none of them are optimal. The elegant syntax is incomplete and ambiguous with hashes, and the full syntax is ugly. The community tends to be against real documentation, favoring ‘read the code’. I find this childish and lazy. Metaprogramming abuse, particularly in libraries, makes bugs a nightmare to track down. On a related note, pervasive metaprogramming makes a comprehensive IDE difficult, if not impossible, to make. The way block passing to functions is done is silly. There is no reason blocks should be passed outside the parameter list, or have odd special syntax to access (yield). I am of the opinion that blocks should have been given a less ambiguous syntax (or hashes could have used different delimiters; perhaps <> rather than {}), and passing as parameters to methods should have been just like all other parameters. object.method(1, {|a| a.bar}, "blah") These oddities, like the block must be the last parameter passed and passing more than one block is different with longer syntax, really annoy me.

C是我最喜欢的，但也很糟糕。

It has the worst pre-processor ever. Why didn't they use something like m4? The whole header vs source file model is broken. Pascal got it right with units. It needs case ranges in the switch statement. Unions and casts from void* break the type system. This makes garbage collectors impossible. No nested functions. GNU C has this, but it should be standard. No boundary checking for allocated memory. There are tools that discover this but they don't detect errors where a piece of code miscalculates an address and writes to an allocated region which isn't related at all. I hate the whole pointer arithmetic. No bounds checking for arrays. Too many issues regarding portability. Even wchar_t differs across platforms.

Python。

虽然前面提到了python处理作用域的奇怪方式，但我觉得最糟糕的结果是:

import random

def myFunction():

    if random.choice(True, False):
        myString = "blah blah blah"

    print myString

也就是说，if块内部的作用域与函数的其余部分相同，这意味着变量声明可以出现在条件分支内部，并且可以在条件分支外部访问。大多数语言要么阻止你这样做，要么至少为你提供某种严格的模式。

此函数有时会成功，但有时会抛出异常。虽然这是一个人为的例子，但这可能会导致一些微妙的问题。