R (R- project for statistics)

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

Java:

没有过程编码，它编译成过程代码，所以让我使用它! 没有多重继承，试图用15,000个接口做同样的事情很糟糕。 约会课，我还需要多说吗。 我不能充分利用多态性。Java不会覆盖不同的参数类型来触发。 我想不出第五个原因，如果我知道，我会回来编辑这篇文章。

C++:

1:头文件。

链接代码比编译代码更难。同样，模板在翻译单元中包含完整源代码的要求也是荒谬的。在那边的那个文件里。你两秒钟前编译的那个。去那里看看。愚蠢的编译器。

2:空标准库。

我的意思是，是的，在c++ 0x中有std::thread，但没有std::socket或任何类似的东西。没有跨平台代码的主要原因是，您必须为希望在多个平台上执行的每个函数学习一个新的库。没有作为标准提供的OS头文件或OS函数，c++只适合推位。

3:没有多次返回或返回值重载

Double x, int y, char z = func();和void func(double x, int y, char z)一样有效;请。没有返回值重载的唯一原因是我们“可能”编写了模棱两可的代码。可能!请在我真正写出模棱两可的代码时给我悲伤，而不是之前。

4:不反思

可以将反射设置为编译时反射。的确如此。没有任何库使得编写大量的库变得困难，并且严重地惹恼了我。我可以滥用预处理器，但是..

5:在模板上鸭子打字

Yaargh。请，概念和正确的模板错误消息。使用Boost这样的库实际上是不可能的，因为如果你用错了，你就是在瞎猜。

我讨厌Java(目前它是我最喜欢的语言)的五个方面，排名不分先后。

As much as I am a fan of Java Generics, there are a lot of oddities that arise from the way it was designed. As such there a myriad of annoying limitations with generics (some of which are the result of type-erasure). The way Object.clone() and the Cloneable interfaces work is totally broken. Instead of taking the high-road and making everything an object (a.la. SmallTalk), Sun wimped out created two distinct categories of data-types: Objects and primitives. As a result there are now two representations for fundamental data types and wierd curiosities such as boxing/unboxing and not being able to put primitives in a Collection. Swing is too complex. Don't get me wrong: there's a lot of cool stuff one can do with Swing but it is a great example of over-engineering. This final complaint is equally the fault of Sun and those whom have written XML libraries for Java. Java XML libraries are way too complicated. In order to simply read in an XML file, I often have to worry about what parser I am using: DOM or SAX? The APIs for each is equally confusing. Native support in the language for easily parsing/writing XML would be very nice. java.util.Date sucks. Not only is it unnecessarily complicated but all the useful methods have been deprecated (and replaced with others that increase complexity).

Python

__init__ 有些库很笨拙，比如smtplib self必须在方法声明中!! (3.0之前)对unicode的支持有点差 缺少内联尝试捕获 没有直接引用"this"/current模块(相反必须使用sys.modules[__name__])

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.