C++

cryptic error-messages when templates are involved lack of template constraints (many cases can be worked around with template metaprogramming, but this will result in unreadable code (at least for average programmers) in most cases) pointer to member-function syntax c++ standards committee should release offical standards more often (or at least release separate updates to the standard library itself), i mean really TR1 was released 2005, and we still dont have a shared_ptr, bind and alike in the standard library. -

Python

那些我不理解的…

math.ceil() and math.floor() return floats, not integers (probably to avoid an integer overflow in the underlying C function - but why not cast to a Python long?) len() is a function not a method reload() is very limited, does not reload a module 9 times out of 10, only reloads an imported label if it is a module - i.e. cannot do from bar import foo; reload(foo) if foo is not itself a module Mutable default arguments have a single reference (why not a new instance each function call?!) All these underscored variables - if they are so private, how come we see inbuilt ones so much in code? Get a namespace! Strings are not mutable - maybe there is a good reason for this but I have come across many situations where I would like to tweak one particular character ...

那些基于实现有意义但令人讨厌的……

array.sort()不返回数组(我认为它发生在原地) 列表/生成器推导式不定义新的作用域(只是for循环的语法糖，对吗?)

以及几个在Python 3中修复的

默认为整数除法 Global只能引用顶级名称空间

C / C + +

缺乏完整的SWAP功能 模板的语法 你不能#define一个#define(没有多通道) 编译器之间的结构打包不兼容 Char是有符号的还是无符号的?

Java

边缘上的不变性 没有像c#一样的ref关键字 到处尝试/捕捉积木 运行时性能差 所有与字符串相关的东西

Python

没有“main”(我已经习惯了!) 强调关键词 有限的线程支持 用self代替this 缺少类似C/ c++的语法

R (R- project for statistics)

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

闲聊

我不想再用java、delphi、c#或ruby进行开发(这是不切实际的，因为我公司的主要开发语言是c#、delphi和java)。 从左到右的评估。 有类注释但没有方法注释(至少在Squeak中) 没有真正的标准库，在细节上有很多差异 缺少名称空间

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.