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, ...

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

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条错误消息) 字典键不接受列表/字典 缺乏深度范围。当我做一个列表推导时，我不希望其中的变量影响到外部作用域

.NET框架(库)

嵌套类型很少使用(例如MessageBoxButton应该是MessageBox.Button) 可变结构体(Rect, Point) 系统名称空间中有太多东西 太多不同的平等概念(对象。等于,对象。ReferenceEquals, operator ==， operator !=， IComparable.CompareTo() == 0) 数组的成员是可变的，但长度是不变的。

还有一点:

XmlSerialization不适用于不可变类型

到目前为止，我最讨厌我最喜欢的语言的地方是我的选择总是在变。每次我以为我找到了命中注定的那个人，我就会发现我讨厌他的5个(或更多)地方。然后那边的草看起来更绿……

VBA(因为你认为你的语言不好)

Whitespace inside a line is rigidly enforced. Statements just end, and require a " _" to break to the next line, but not every line can be broken. No ++,--,+=,-= statements. Seriously? Arrays can begin at any index, not just 0. Some types (i.e.: fixed-point "Decimal" value) must be subtypes of Variant, and aren't available as their own type. != and <>. "=" is used as both comparator and assigning, instead of splitting into "=" and "==". "Option Explicit". UI hasn't been updated since 2000. Office2k7 didn't upgrade to VB.NET Most object models are non-sensical and overly verbose.

TCL

这是我最喜欢的语言，几乎可以做任何事情。多年来，它已经(慢慢地，非常缓慢地)演变为解决大多数让我烦恼的事情。而且这门语言非常灵活，很容易实现语法来覆盖那些仍然困扰我的东西。但是语言中有一些东西是不能轻易改变的，只是打破了它的禅意:

Arrays (of the associative kind, what Perl calls hash) don't have proper value semantics. This makes them awkward to pass to and return from functions. Also, this means that they can't be nested. For this reason dicts (dictionaries) were invented but too late, the nice array access syntax: $array($foo) is now forever taken by stupid arrays for backwards compatibility. We're now stuck with: dict get $dict $foo which is much more verbose and to me feels less readable. No real closures. Though it can be emulated somewhat by globals or namespaces but that defeats the reason for closures in the first place. Although, I can't really see for now how closures can be implemented in a pure value semantics system. Teacup is hard to use and is not at all intuitive compared to all other repository tool out there. This is more ActiveState's fault than tcl-core and doesn't really break tcl's Zen when coding but it is still very annoying.