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/

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

我有一本书探讨了SNOBOL中的各种项目。第一章探讨了SNOBOL编程和语言的历史和文化，并花了一些时间论证一个优秀的程序员喜欢一种语言不是因为它的缺陷，而是尽管有缺陷。

我最喜欢的语言是Icon/Unicon。但还是有一些事情让我很恼火:

它不是很出名，也不是很受欢迎。 与PHP、Perl、Java等相比，它的库要小得多。数据库访问是通过ODBC完成的，这实际上非常烦人。 对于所有其他出色的列表处理，我想念PHP内置的explosion()和implode()。 它没有表常数。列表，是的，表格，不是。 它是一种编译(实际翻译)语言。

Lua

我喜欢用Lua编程，但下面是让我头疼的事情:

没有办法用这种语言编写API——不像C .h文件或Java接口 语言有一流的功能，但有人忘记告诉设计库的人。 编写函数的语法太重量级了。 语法分为语句和表达式。 表达式形式是贫乏的:没有let形式，没有真正的条件表达式，……

尽管如此，我还是坚持认为Lua非常棒:-)

Python。

虽然前面提到了python处理作用域的奇怪方式，但我觉得最糟糕的结果是:

import random

def myFunction():

    if random.choice(True, False):
        myString = "blah blah blah"

    print myString

也就是说，if块内部的作用域与函数的其余部分相同，这意味着变量声明可以出现在条件分支内部，并且可以在条件分支外部访问。大多数语言要么阻止你这样做，要么至少为你提供某种严格的模式。

此函数有时会成功，但有时会抛出异常。虽然这是一个人为的例子，但这可能会导致一些微妙的问题。

C#

No easy way to check if a type is Numeric It means you are probably stuck using most of the microsoft stack, IIS and MSSQL Instead of being a specific tool for a specific problem, C# tries to be a language for every paradigm. Lack of community. Sure, there are starting to be open-source frameworks and libraries for C#. The same ones that have been available to Java developers for years. Hard to find good help. The internet is littered with poor examples of how to solve problems with C#. This goes back to problem #3.

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