Haskell。

默认情况下导入Prelude。 类型类的范围是通用的。 模块不是一流的。 类型不能依赖于值。 单子不统一Functor。

JavaScript:

The Object prototype can be modified. Every single object in your program gets new properties, and something probably breaks. All objects are hash maps, but it's difficult to safely use them as such. In particular, if one of your keys happens to be __proto__, you're in trouble. No object closure at function reference time. In fact, no object closure at all -- instead, this is set whenever a function is called with object notation or the new operator. Results in much confusion, particularly when creating event callbacks, because this isn't set to what the programmer expects. Corollary: calling a function without object notation or the new operator results in this being set equal to the global object, resulting in much breakage. Addition operator overloaded to also perform string concatenation, despite the two operations being fundamentally different. Results in pain when a value you expect to be a number is in fact a string. == and != operators perform type coercion. Comparisons between different types involve a list of rules that no mortal can remember in full. This is mitigated by the existence of === and !== operators. Both null and undefined exist, with subtly different, yet redundant meanings. Why? Weird syntax for setting up prototype chains. parseInt(s) expects a C-style number, so treats values with leading zeroes as octal, etc. You can at least parseInt(s, 10) but the default behaviour is confusing. No block scope. Can declare the same variable more than once. Can use a variable without declaring it, in which case it's global and probably breaks your program. with { }. Really difficult to document with JavaDoc like tools.

我觉得最喜欢的语言是不可能选择的。动态类型和静态类型不能进行比较，所以我只列出我使用的是哪一种类型

C++:

Template metaprogramming syntax is ugly. An implicit ::value would make it much more concise ->. Why can't the compiler figure out that I'm doing a ptr.thing and just do -> for me? I hate whitespace. So the whole vector<vector<int>> has to be vector<vector<int> > makes me get the jitters and then I can't focus whenever I see that line of code and I end up trying to figure out a way to use int[][] or something Macros. I personally love the concept of macros. But with C++, I that the system is a hack I'm a hater of ;

Python:

字符串是不可变的。这样我就不能用string[4]="b" 通过引用隐式复制列表。哪个泄漏到[[0]*width]*height问题 缺少尾递归(每当我输入错误递归函数时，我必须安装IDLE以避免吐出1000条错误消息) 字典键不接受列表/字典 缺乏深度范围。当我做一个列表推导时，我不希望其中的变量影响到外部作用域

c#(好吧，我猜一部分是VisualStudio IDE):

No covariance (yet), like Class<D> cannot be used in place of Class<B> even though type D derives from type B. Graphic designers don't support generic based inheritance (or inheritance from abstract classes), even though the inheritance itself works just fine if you work around the designer problems by adding extra inheritance levels just so designers always see concrete non-generic variants of your code. No constructor inheritance No constructors in where clauses of generic type parameters VisualStudio seems to have a tendency to mysteriously check out files (like project files and/or unit test definitions) when opening a solution, even though the files do not seem to actually get altered.

如果你明天再问我，可能会有不同的名单。即使协方差和设计师的麻烦将在我的前5名，直到他们被解决(随着方差添加到c# 4.0，这似乎已经发生了至少一个…)

D

we have in operator, but no !in operator? dynamic array 'length' property - ya canna do array.length += 512; no exit statement - as in python's sys.exit(), etc. Sure, you can call C's exit, but unflushed output don't get flushed associative array literals + string literals suck string literals found as is inside an associative array literal are interpreted as static, thus this char[][char[]] hash = ["hello":"world","goodbye":"angels"]; doesn't work without some extra casting due to different length string literals despite a. I didn't ask it to be interpreted as static arrays b. static arrays aren't allowed in associative arrays anyways cyclic dependencies disallowed (want to port that java lib? Have fun redesigning the class hierarchy)

谁帮我检查一下;不确定它们是否都有意义。

R (R- project for statistics)

糟糕透顶的字符串支撑 对于一些简单的描述任务，比如交叉表格，是非常困难的 大型数据集操作是在内存中完成的。