Erlang

没有静态推断 就像在哈斯凯尔发现的一样。这 会导致运行时错误和一个 有认真写代码还是使用 透析器(1)发现 差异。动态类型是 慢的:也被认为是慢的; 与C、Java等语言相比，它几乎是未知的; 的lists(3)模块有时相当精简 我缺少用于列表处理的有用函数 (就像在数据。例如Haskell中的List); 让我在每句话的结尾都加上 在从句中，和。最后是后者。

Common Lisp:

关键词往往太啰嗦。 库支持是可怜的。 在希望更严格地处理内存的操作系统中不能很好地工作。 没有与操作系统交互的良好工具。 “循环”功能没有很好地定义，当然看起来也不像Lispy。

C#

它是一种很棒的语言，特别是在LINQ中，但是与c++相比泛型支持较差。它有如此多的潜力，但目前的实现只对强类型集合和类似的琐碎事情有用。下面举几个例子:

A generic argument cannot be restricted to enums (only classes or structs). A generic argument cannot be a static class. Why? This seems like a completely artifical restriction. You cannot specify that a generic type must have a constructor with a certain signature because you cannot have constructors on interfaces. Why not? It's just another method with the special name ".ctor". Similarly, you cannot specify that a generic type must have a static method, because those also cannot be declared on interface. Something like static T Parse(string s) would often come in useful. The compiler is too eager in prohibiting some casts which the programmer knows would actually work, so they require uglyness like (TheRealType)(object)value No covariance, eg. IList<string> cannot be converted to IList<object>, even though string[] can be converted to object[]. (Microsoft might be fixing this in C# 4.0, though.)

Python (3.1)

奇怪的无序T if C else F语法用于条件语句。 字节字面值看起来太像STR字面值了。我们应该得到x'414243'而不是b' abc '。 str在某些平台上是UTF-16，在其他平台上是UTF-32。(尽管至少比2要好。x字符串。) 具有相同的加法和连接运算符。这对numpy.array这样的类型很不利。 运行缓慢。

VB。网

The behavior AndAlso / OrElse and And / Or seems backwards. Perhaps they should be switched. When can only be used for exception catching. The ability to do a When conditional would be nice for some other things. There is no friggin Refactoring in the VS IDE (not really the language's fault) like there is with C# Not <obj> Is Nothing. Yes, this has been remedied by IsNot, but for some reason I see the Not Is being used too often. (I see it much more frequently with devs who speak english as a second language, does it make better sense from that angle?) It doesn't require the () on ToString() and most functions. (Leads to sloppy coding habits) Having to do _ when breaking a line. It allows optional parameters. (Leads to sloppy coding habits) declaring an array is done by UpperBound and not by capacity. "Dim arr(2) as String" will actually hold 3 elements. Having = be a comparison and assignment operator.

Haskell:

惰性计算导致空间泄漏。 数字层次结构不是根据数学抽象构造的。 严格的单元IO会使调试更加困难。 大型实现处理I/O的方式似乎与标准不太兼容。(特别是，输出字符只输出低8位——然后构建代码，使用这个假设来执行二进制I/O。我吐!) ($)运算符的结合性可以被改变以使某些表达式更漂亮。

大多数问题都不会上升到讨厌的程度，有些人试图解决或为每一个问题构建可靠的变通办法。

编辑:关于第5点有些困惑。特别是有些人似乎认为我指的是论证的顺序，但我不是。我不解释我的意思，我只想让人们去下面的链接http://hackage.haskell.org/trac/haskell-prime/wiki/ChangeDollarAssociativity，它很好地表达了我的意思。