PHP:

人们永远无法确定某些几乎常见的扩展在所有web服务器上都可用。 试图成为未来的一切(goto，闭包，…) 对于没有经验的用户有很多安全风险 更多的操作符重载会很好 所有不学习如何使它正常工作的可怜的程序员，给它一个坏名声

尽管如此，PHP是(脚本)语言。: -)

Python。

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

import random

def myFunction():

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

    print myString

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

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

Python:

处理数字太慢了。这不是什么大问题，除非…… 不能简单地在程序中包含导入时自动编译的C代码。 在py3k接管之前，我们仍然要忍受愚蠢的整数除法规则。 在py3k接管之前，像imap和izip这样的好东西仍然存在于一个单独的模块中。 在py3k接管之前，我们还有很多工作要做。

C

It's so flexible and powerful that it's really easy to write really awful, or downright dangerous code (or, if you prefer, "with great power comes great responsibility"). '=' for assignment, and '==' for equality; easy to confuse in 'if' statements. The implementation of a number of fundamental parts of the language are compiler-dependent; e.g. the size of the basic types, order of bits in bitfields, padding and byte order in unions. Bitfields aren't parameterisable (i.e. you can array of ints, but you can't have an array of bits). String handling could be improved.

c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的，明天问我，我会想出一个不同的5个:)

方案:

缺乏用户/社区小