生存巨:

标准库的奇怪之处:它并不总是显示最佳实践，而且文档不足 硬编码FunctionX, TupleX类 缺乏属性:getter和setter是分开的，这违反了DRY，并且使得像FRP这样的事情几乎不可能实现 需要= _来初始化属性

我不敢相信，我最讨厌的Python竟然还没被提到:

(Prior to 3.x) Relative imports look like absolute imports. import foo Does this import foo from the directory you're standing in or from the sys.path? Zipped eggs, leading to a sys.path full of shite. Zipped eggs means you can't use grep and find (to among other things debug problem 1)! Fortunately, there's pip. Use pip. Some of the included batteries are unpythonic. It grates to use them. Might be the fault of distro's and packagers, but still: sourcefile-encoding set to fscking ASCII on install/compile. WTF? Means I have to put the "# coding: UTF-8"-stuff in every single .py I ever make.

Py3k解决了我的其他几个讨厌的问题，例如坚持字符串是unicode的，8位的东西是不同的……

objective - c

1)没有命名空间，只有手动命名约定——我不介意在类分离方面，但我确实怀念能够在一行命名空间中导入所有类定义(如import com.me.somelibrary.*)。

2)库在像RegEx支持这样的重要领域仍然存在一些漏洞。

3)属性语法有点笨拙，需要三行(在两个单独的文件中)来声明一个属性。

4)我喜欢保留/释放模式，但它比应该的更容易释放一个引用，然后意外地使用它。

5)虽然不是真正的语言特性，但Xcode与Objective-C的使用是如此交织在一起，我不禁想到这方面……基本上自动补全，是很可疑的。它更像是一个奖励你找到你想要的东西的系统，然后把它作为一个选择。但我想我从来都不喜欢自动补全引擎。

C++

The inconsistencies in the libraries related to char* and std::string. All C++ libs should take std::strings. Characters are not bytes with respect to iostream. I do a lot of byte-oriented work. Having a "byte" type and a "character" type would significantly make it simpler. That, too, would permit scaling to Unicode somewhat easier. Bit operations should be easy on a value. I should be able to access and set the n'th bit of a value without playing AND/OR dancing. The lack of a standardized interface for GUIs. This is where Microsoft has really been able to position themselves well with C#. A standard interface binding that OS makers provide would go really far for my work.

Python

1-3:没有一个明显的打包/构建/文档系统的选择(比如Perl的cpan、POD或Ruby的gem、rake、rdoc)。 4: Python 3.0是不兼容的，需要两个源分支(2。x和3.x)用于每个Python项目。但是Python 3.0的不兼容性还不足以证明它的合理性。大多数py3k的优势都太微妙了。 5: Jython, IronPython, CPython不兼容。

C

bit fields -- they aren't well specified by the language and how they work is compiler dependent and architecture dependent. It's often hard to find where a particular symbol is defined in a large mass of code, esp. if that symbol is produced by a macro. Which reminds me... The preprocessor is a rather ugly hack, amenable to all sorts of abuse. lack of standard sized integers (remedied by uint*_t lately, but there is lots and lots of old code floating around out there with custom typedefs or #defines for DWORD, WORD, BYTE, etc.) Lack of something akin to Perl's cpan.org (would love to be wrong about that one.)

编辑: 在考虑C的CPAN时，我想……我该怎么称呼这样的东西，然后想到了“ccan”，然后谷歌了一下，我看到了这个: http://ccan.ozlabs.org/

不过，它似乎还处于起步阶段。