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

objective - c

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

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

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

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

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

Scala是我最喜欢的语言。五件讨厌的事?容易:

Takes a long time to learn properly. I know you can write Scala as a 'better java'. That is what we used to say about C++ and C too. I agree this is an inevitable consequence of the deep ideas in the language. But still ... Methods vs. Functions: def f(x: Int) = x*x defines a method f, not a function f. Methods are not functions despite a lot of early Scala tutorial material blurring the distinction. The language tries to blur it too because if you supply a method in some places where a function is expected it is accepted. Do we have to have both methods and functions? Yes it is fundamental. But it was initially confusing to me. Composing classes or objects from mixins in the 'cake' pattern is prone to NPE's. e.g. trait X { val host: String; val url = "http://" + host } is a mixin that will NPE on instantiation, or not, depending on its position in the class declaration. The compiler could tell you if it will fail but doesn't. (In 2.7 anyway.) It is hard to diagnose the problem in complex inheritance graphs. Arrays in 2.8 rely on implicits to mesh with the main scala collection types. But implicits are not applied everywhere. An Array can be supplied where a Seq is expected. But an Option[Array] cannot be supplied where an Option[Seq] is expected. I know there are no completely 'right' ways to handle java Arrays. Type erasure. Enough said.

c#:

1)静态方法必须是类的成员

2)静态扩展方法只能添加到静态类中

3)接口函数的实现不会被标记为“override”之类的东西来显示它们来自基类或接口(这使得你很难确保你正在重写你所期望的方法(具有正确的签名))。

我只有3个。我想那很好。

经过一些思考后重写了这篇文章…

虽然我喜欢PHP，但我讨厌它的五个方面(排名不分先后):

内置函数中的命名和参数顺序不一致。 面向对象的数组方法多亏了SPL，但遗憾的是还没有字符串。 PHP本身没有真正的并发，只有通过托管web服务器的多处理 没有像JavaScript那样的异步调用 只能通过扩展进行操作码缓存。不是很糟糕，只是有点烦人。

这些是令我烦恼的语言特性(或缺乏)，但更大的问题是这些与人/社区相关的东西:

事实上，很多使用PHP的人，对编程和良好实践一无所知，从而产生了非常混乱的代码。JavaScript也有同样的问题。 大量的教程/书籍传授了非常糟糕的做法和风格。这可能是第三条的主要原因。 它的坏名声主要是因为第三条和第四条。

Haskell(包括所有GHC扩展，而不仅仅是Haskell'98的基础规范)。

我讨厌它的一点是:它不是主流。