JavaScript:

All the coolest things are insanely complex, but then, all the coolness is also wrapped up in such a small amount of code that you feel stupid for struggling to follow it '+' is an absurd choice of operator for concatenation in a weakly-typed language. Were they trying to scare off the noobs? It's a cross-browser compatibility minefield (never mind if it's even turned on or not) It's generally untrusted - associated with scummery such as blocking the back button, pop-ups that never die, etc. It's nearly impossible to debug because there are only a few different error messages and a few different types (Number, String, Object, etc.)

如果不是jQuery，我可能还是会像以前一样讨厌它:)

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.

C#

1)缺乏为值类型编写泛型的实际能力。例如，任何白痴(好吧，大多数白痴)都可以编写一个例程，用c++计算int, float, double等列表的标准偏差，它写起来很简单，易于阅读，并作为快速的非泛型代码执行。我认为，如果你能用c#写一些东西，接近于达到这三个中的任何一个，而在其他两个上又不荒谬，你就是一个真正伟大的程序员。

2)协方差和反方差，尽管这被添加到4。

3)非常糟糕的LINQ文档(好吧，并不是语言的一部分)。

4)尝试使用foreach/迭代器，当我每次都想做同样的事情，除了上次略有不同(如连接一串字符串与逗号之间的单词和最后两个)。如果我用一个IEnumerable来写它，它很难写和读，而用一个for (int I =0 I <…)它并没有好到哪里去，而且效率更低。

5)我知道我会收到抱怨，但是缺少受控的例外。这并不需要像在java中那样实现(框架开发人员确实提出了一些很好的观点，为什么他们没有这样做)，但我很乐意看到编译器警告不喜欢受控异常的用户可以关闭。

R (R- project for statistics)

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

C#

泛型参数是不变的，c# 4.0为泛型类型引入了协方差和逆变性 可覆盖的类成员必须显式地标记为virtual

Java

缺少无符号数字数据类型 基本数据类型不是对象

C++

Strings. They are not interoperable with platform strings, so you end up using std::vector half of the time. The copy policy (copy on write or deep copy) is not defined, so performance guarantees can not be given for straightforward syntax. Sometimes they rely on STL algorithms that are not very intuitive to use. Too many libraries roll their own which are unfortunately much more comfortable to use. Unless you have to combine them. Variety of string representations Now, this is a little bit of a platform problem - but I still hope it would have been better when a less obstinate standard string class would have been available earlier. The following string representations I use frequently: generic LPCTSTR, LPC(W)STR allocated by CoTaskMemAlloc, BSTR, _bstr _t (w)string, CString, std::vector a roll-my-own class (sigh) that adds range checking and basic operations to a (w)char * buffer of known length Build model. I am sick to death of all the time spent muddling around with who-includes-what, forward declarations, optimizing precompiled headers and includes to keep at least incremental build times bearable, etc. It was great in the eighties, but now? There are so many hurdles to packing up a piece of code so it can be reused that even moms dog gets bored listening to me. Hard to parse This makes external tools especially hard to write, and get right. And today, we C++ guys are lacking mostly in the tool chain. I love my C# reflection and delegates but I can live without them. Without great refactoring, I can't. Threading is too hard Language doesn't even recognize it (by now), and the freedoms of the compiler - while great - are to painful. Static and on-demand initialization Technically, I cheat here: this is another puzzle piece in the "wrap up code for reuse": It's a nightmare to get something initialized only when it is needed. The best solution to all other redist problems is throwing everything into headers, this problem says "neeener - you cannot".

诚然，其中许多内容超出了严格的语言范围，但在我看来，整个工具链都需要进行判断和发展。