我最喜欢的是c#，但是已经有很多关于c#的答案了，所以我将选择我的下一个“最喜欢的”:

t - sql

The GO statement, and the fact that you need it for all manner of DDL/DML scripting, and the fact that it also breaks transaction semantics, making it far more difficult than it needs to be to write an atomic script, which you really need to have in order to upgrade a production database. Inconsistent semicolon semantics. 99% of the syntax doesn't need it, MERGE statement has to end with it, WITH statement has to begin with it... make up your mind! WITH CHECK CHECK / WITH NOCHECK CHECK. Uuuu-gly. Optional parameters in UDFs aren't really optional. Caller must specify DEFAULT (and don't even try using NULL instead). Compare to SPs where they are truly optional. "...may cause cycles or multiple cascade paths." HATE HATE HATE HATE HATE HATE HATE HATE HATE HATE HATE

Java:

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

Ruby。

Strange scoping rules - variables, constants, and methods each behave differently from each other. The rules change also depending on which keyword you used to create a closure. Or on whether you're in a class, eigenclass, object, module, or module's self. Then there's instance_eval, which changes the rules to a different set of rules. And they change again when a module is "included" or "extended", which themselves do different things to scope. And some sets of rules can't be emulated by metaprogramming, so you have to use eval. Unless you're on ruby 1.9, where all of this is different. Namespacing is basically useless. If you have Foo::File, then the stdlib File is probably broken for all of Foo. require statement is broken. If two files require eachother, the behavior of those files can change dramatically depending on which is loaded first from elsewhere. libraries change APIs dramatically and suddenly, so you have to require specific minor revision numbers of all of your dependencies. For every single ruby application on your system. The rubygems package system overrides "require" rather than putting files in the search path - because why use a system when you can replace it?

德尔菲:

IDE有点不稳定。 代码洞察有时令人困惑。 调试有时是有bug的。 更新多个项目文件可能会很麻烦。 如果启动时一个或多个包不可用，错误消息会弹出几次。

C++

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

Groovy和Grails

动态类型 约定优于配置，假设您了解约定 你讨厌春天的一切 你讨厌Hibernate的一切 [Groovy]跨集合的常见操作不是(但最近的版本对此进行了改进)