Ruby:

重要的空白。对于解释器，行尾=语句的结束，除非看起来语句应该继续(或者显式转义换行符)。 慢 在线文档不如Python的好(为了辩护，Python的很棒) 我刚才提到慢了吗?

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

SAS

从不有自己的想法(一切都是借来的)。 贪婪于庞大的数据集。 使用Java，但从未学习过什么是对象。 窃取Perl，但将其隐藏在其数据步骤中。 统计学家总是撒谎!

但这只是因为VB6毒害了整整一代程序员

我在一个曾经是VB6商店的VB . net商店工作，而在这里工作的每一个曾经是VB6开发人员的人都顽固地拒绝学习任何关于. net的知识。他们编写的代码就像VB6一样，他们的应用程序就像VB6应用程序一样糟糕。我的老板非常不鼓励使用LINQ，因为她担心其他人很难理解，这是事实，因为没有人想要理解它。

我认为如果微软只使用c#，我们会过得更好，这让我很难受，因为我认为花括号远不如VB的冗长结束语句。

Delphi(又名Object Pascal)，我将讨论本机版本，而不是。net。

Var块! 语言中的接口在设计时就考虑到了COM的使用——因此比c#或Java要复杂得多。ie。涉及引用计数，除非显式禁用它。 没有尝试，只有最终结束; 对象创建过于显式: var obj: TMyObject; .．. obj:= TMyObject.Create; 试一试 .．. 最后 obj.Free; 结束;

而是像这样

auto obj: TMyObject; // compiler adds the default constructor call and the destructor call in a try/finally block. 

好吧，语言太好了，我真的想不出更多，所以我在这里强迫自己:内置类型，如字符串，整数..或者枚举最好有方法。ie。i. tostring代替IntToStr(i)。

c#(好吧，我猜一部分是VisualStudio IDE):

No covariance (yet), like Class<D> cannot be used in place of Class<B> even though type D derives from type B. Graphic designers don't support generic based inheritance (or inheritance from abstract classes), even though the inheritance itself works just fine if you work around the designer problems by adding extra inheritance levels just so designers always see concrete non-generic variants of your code. No constructor inheritance No constructors in where clauses of generic type parameters VisualStudio seems to have a tendency to mysteriously check out files (like project files and/or unit test definitions) when opening a solution, even though the files do not seem to actually get altered.

如果你明天再问我，可能会有不同的名单。即使协方差和设计师的麻烦将在我的前5名，直到他们被解决(随着方差添加到c# 4.0，这似乎已经发生了至少一个…)