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

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

objective - c

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

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

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

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

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

德国

我的母语……虽然它听起来比克林贡语更美，但它是一个语法地狱……

conjugations: even regular verbs have different forms for each person and time (with few exceptions)... Example: I see, you see, he/she/it sees, we see, you see, they see translates into: Ich sehe, du siehst, er/sie/es sieht, wir sehen, ihr seht, sie sehen. polite form of address: equals 3rd person plural, used to equal 2nd person plural in the middle age... I really hate the concept of distinguishing between "Du" and "Sie" for my philosophy is that each human being should be considered equal in the amount of respect for it deserves (I mean, what are swear words for, hm?) punctuation: show me a language that uses more commas regularly! missing suitable words: eg. there's no real German equivalent of "convenience" or any derivate of this word... in almost every case you just can't translate it into another German word and keep the meaning... instead you would have to make up a whole subset to describe it somewhat adequate... Anglicisms and Denglish: Sure, the English language has "Kindergarten" or "Poltergeist" and what not but the German language is overflowing with Anglicisms nobody needs... Even worse: We redefine some words we adopt, eg. in German "Handy" means a cell phone and has nothing to do with the adjective it is in English... There are influxes on grammar as well, leading to "Denglish" expressions (see linked article at Wikipedia) There's more, but I don't want to exaggerate this and those are my personal Top5 of what I hate about the German language...

Common Lisp:

关键词往往太啰嗦。 库支持是可怜的。 在希望更严格地处理内存的操作系统中不能很好地工作。 没有与操作系统交互的良好工具。 “循环”功能没有很好地定义，当然看起来也不像Lispy。

Haskell。

默认情况下导入Prelude。 类型类的范围是通用的。 模块不是一流的。 类型不能依赖于值。 单子不统一Functor。

Python

No statements in lambdas. GRRRR foo( a for b in c if d ) feels wrong, it surprises me every time I get away with it. Shouldin't it be foo( (a for b in c if d) )? Can i have a dict comprehension? map and filter operators have special syntax in list comprehensions, how about something for reduce? or sort? Just by having a yield statement in it, a function is magically transformed into a generator, and its interface changes completely. Also, that generator cannot do any work before the first next(). at least, not without using a function that returns a generator.

JavaScript

No brief syntax for making modular code libraries. You have to call a function that returns a dictionary of public methods. And you have to edit that in (at least) two places every time you alter the interface of your module. Creating closures involves returning it from a function that returns a function from ('sup dog) yo' function. Clutter! for each ( foo ) syntax and behavior feels like an afterthought. Knowing when your code will actually run (and in what order) is more of a dark-art. The only way to get it right for sure is put everything (yes, that too) in one big file. and even then you still need to wait for a document.onload Am i missing something? is there no trivial way to get json serialized values without building them by hand? (yes jQuery can do this, sort of).