Lua:

The built-in error system is absolutely horrendous You can implement a try-catch system by modifying the Lua interpreter; but it has no compatibility with the errors that are thrown by the built in functions. The fact they have __newindex instead of __setindex as the setter ... and __newindex is only fired when the key doesn't already exist. If it does, no metamethod is called at all. No good type comparison system. There's the type() function but it only handles the basic types (all tables are tables). It really needs to have a metamethod for type comparisons. I've implemented this before with an 'is' operator and a __type metamethod and it works really nicely. It's a bitch to define new keywords. You can do it, but the code inside Lua isn't well documented so it's kind of trial and error to find out how to get the result you want. This is a major issue when you want to implement the things I mentioned above yourself (not so much __setindex though, that's an easy modification). I can't use it in a web browser. Yeah not really a problem with the language itself, but damn, would I love to be able to use Lua instead of Javascript... :)

C#

Lack of multiple dispatch based on the runtime type of the method arguments. dynamic should solve most of this, but it hasn't been released yet. Interface implementation is declarative not structural. I really like the way Google's Go language is doing types Making asynchronous method calls is really bulky (and I'm pretty sure all threads are OS threads, not lightweight threads) No macro system. I'm not talking about C-style macros here; I'm talking LISP/Scheme style macros Operators are static methods and their signatures are overly constrained (and you can't create new ones).

Perl代表了一种可怕的语言。

No "public" or "private" or "protected" declarations/definitions. The "my $variable_name;" does not declare a global outside of a subroutine. The "my $variable_name;" gets accessed by subroutines but "use strict;" or other "use " creates warnings. Function prototypes end up unexplained, undemonstrated, unwanted, or some other excuse. Overzealous symbol use ends up "cool and quick" when reading globs of symbols. When one gets hot they like to stay hot, and need nothing to cool them. After a week of Perl, I end up unable to write a function and prototype it. What exactly is a module and does it actually NEED a ".pm" extension? If you want to create a public variable and access it from inside a subroutine, how do you accomplish this without creating a warning? Where do you find some neat scripts that teach one some neat Perl?

PHP

没有构造函数重载 不一致的函数命名(str_replace，但strtolower) define()不像c++那样逐字替换全局变量。 在与XHTML组合时，像if-语句这样的语句必须以不缩进开始，即使为了保持XHTML缩进一致，XHTML是缩进的。

Ex:

你必须输入:

<?php
if($x == NULL)
{
?>
                     <p><?= $x . ' is null' ?></p>
<?php
}
?>

错误捕获非常糟糕

(不知道为什么又把5号改成了1号，随便了)

C++

太容易随机破坏内存并创建几乎不可能找到的错误(尽管Valgrind在修复这个问题上走了很长的路)。 模板错误消息。 在使用模板时，很容易将所有内容都包含在一个文件中，然后进行愚蠢的编译。 标准库在现代是一个笑话(默认情况下仍然没有线程或网络?) 大量令人讨厌的C语言(特别是所有在short/int/unsigned/等之间的转换)。

C(好吧，这不是我最喜欢的，但当时还没人做过。)

套接字库语法。 没有函数重载。 c风格的字符串。 缓冲区溢出。 神秘的语法。我不知道有多少次我查到像atoi这样的东西，拍着我的额头，然后大喊“当然!”

编辑:如果我使用更多的库代码(就像我用套接字做的那样，但那些特别糟糕)，我可能会想出更多的库代码，但我已经觉得我选择C语言是在作弊。许多语言的存在只是为了取C语言的好的部分，取代坏的部分，这有点像在徒劳无益。