c#:

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

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

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

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

Objective Caml

Non-concurrent garbage collector. I can write multi-threaded programs all day long, but they're only ever going to get one of my eight cores at a time. This makes me sad. No type classes (or their moral equivalent). There's Furuse-san's GCaml, but it's A) not quite as good as type classes, and B) not in the INRIA distribution. Badly in need of a Cocoa bridge. Seriously. If I wrote more code with actual interfaces to DNA-based life forms, then I'd probably break down and write the damned thing myself. Why hasn't anybody else done this yet? Functors are abominable. Seriously, modules ought to be first-class values. There should be only one kind of function. Read Montagu and Rémy before you flame me for this. Should use LLVM for its back-end. Who do I have to murder to get OCaml to compile for my stupid little ARM6 core?

是的，我有一些问题。我仍然非常喜欢这门语言。这太棒了。

我觉得最喜欢的语言是不可能选择的。动态类型和静态类型不能进行比较，所以我只列出我使用的是哪一种类型

C++:

Template metaprogramming syntax is ugly. An implicit ::value would make it much more concise ->. Why can't the compiler figure out that I'm doing a ptr.thing and just do -> for me? I hate whitespace. So the whole vector<vector<int>> has to be vector<vector<int> > makes me get the jitters and then I can't focus whenever I see that line of code and I end up trying to figure out a way to use int[][] or something Macros. I personally love the concept of macros. But with C++, I that the system is a hack I'm a hater of ;

Python:

字符串是不可变的。这样我就不能用string[4]="b" 通过引用隐式复制列表。哪个泄漏到[[0]*width]*height问题 缺少尾递归(每当我输入错误递归函数时，我必须安装IDLE以避免吐出1000条错误消息) 字典键不接受列表/字典 缺乏深度范围。当我做一个列表推导时，我不希望其中的变量影响到外部作用域

VB6

仅Windows。 不再支持。 数组可以从任何数字开始，而不是全部归一化为0。 已编译的应用程序依赖于许多dll才能正常运行。 许多复杂的控件(如浏览器控件或复杂的代码段)在运行未编译的代码时往往会破坏IDE，但在编译后却可以正常工作。

.NET框架(库)

嵌套类型很少使用(例如MessageBoxButton应该是MessageBox.Button) 可变结构体(Rect, Point) 系统名称空间中有太多东西 太多不同的平等概念(对象。等于,对象。ReferenceEquals, operator ==， operator !=， IComparable.CompareTo() == 0) 数组的成员是可变的，但长度是不变的。

还有一点:

XmlSerialization不适用于不可变类型

Python:

我仍然是python的一般用户，所以我的抱怨可能只是知识的锁或误用。欢迎提出意见。我很喜欢这门语言。

Poor thread support and GIL. If you'd like to take use of multicore platform, most of the python programmers would probably recommend multiprocessing or some sort, don't use threading. It wouldn't give you the performance you are expecting. property only for instance variable. _class_var = property(classmethod(some_method)) just wouldn't work. How can I get a property wrapped class variable? no access control. All access controls are syntax mangling. Like private is __private, protect is _protected, etc... And hope that everyone programs python follows the naming convention. Come on, we can do better than that. I agree the python philosophy of being simple and clear syntax but some simple and clear syntax not being supported seems lock of good judgement, in my opinion. Such as, a++, ++a, a-- and --a, self-de/increment, what's wrong with those? foo = (a > b ? a : b) unary operation, what's wrong with those? (I know py2.6 has something similar introduced, but given the massive support of almost every other language for those simple syntax, why reinventing the wheel? why not just follow the best practice? Shouldn't a good thing just keep in its good "form"?) Program to interface. Python has no interface or abstract class concept (py3k has something called abc), everything is concrete. Providing an "interface" or "abstract" keyword to build class skeleton and guard class inheritance and extension wouldn't be a bad idea I think. It helps on top-down design. Currently, I just have to fill the each of methods with NotImplementedError, quite a tedious job. I have to add this. version less than 3.x has str and unicode types. This is a true nightmare. It makes ascii and non-ascii/unicode mixing most likely to fail (bad, bad)

我看到人们抱怨速度。我不明白。它是一种解释语言，代码直到运行时才编译成机器代码，这就是它的本质。你不能比较解释语言和编译语言的速度。据我所知，在解释/脚本语言中，python并不慢。