Python:

Global Interpreter Lock - Dealing with this complicates parallel processing. Lambdas functions are a bit clunky. No built-in ordered-dictionary type. Depending on how Python is compiled, it can use either UCS-2 vs UCS-4 for the internal Unicode encoding, many string operators and iterators may have unexpected results for multi-byte characters that exceed the default width. String slicing and iteration depend on the bit width rather than checking and counting characters. (Most other programming languages do similar things as well and have similarly odd behavior with these characters.) There are inconsistencies surrounding GUI frameworks for Python.

SAS

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

Python

1-3:没有一个明显的打包/构建/文档系统的选择(比如Perl的cpan、POD或Ruby的gem、rake、rdoc)。 4: Python 3.0是不兼容的，需要两个源分支(2。x和3.x)用于每个Python项目。但是Python 3.0的不兼容性还不足以证明它的合理性。大多数py3k的优势都太微妙了。 5: Jython, IronPython, CPython不兼容。

c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的，明天问我，我会想出一个不同的5个:)

闲聊

我不想再用java、delphi、c#或ruby进行开发(这是不切实际的，因为我公司的主要开发语言是c#、delphi和java)。 从左到右的评估。 有类注释但没有方法注释(至少在Squeak中) 没有真正的标准库，在细节上有很多差异 缺少名称空间

JavaScript

Function object syntax: f = new Function( "foo", "bar", "return foo+bar;" ); (It takes n arguments, the first n-1 are arguments for the function, then nth is the actual function, in string form. Which is just silly.) Function arguments can be repeated. f = new Function( "foo", "foo", "return foo;" ); The last repetition is the only one ever used, though: f( "bye", "hi" ) // returns "hi" f( "hi" ) // returns undefined E4X should just die. My users are always complaining that it doesn't work the way they think it will. Let's face it, when you need a page and a half of psuedocode for a setter, it's time to rethink things. A standard notion of stdin/stdout/stderr (and files!) would be nice. null != undefined It's irritating to have to handle them both. Sometimes it's useful, but most languages manage to limp along fine with one.