c# 4.0

“动态”关键字，被滥用的时机已经成熟。如果你想要/需要使用反射，使用并让它明显地显示你正在使用它，不要试图用动态来伪装它。

我讨厌Java(目前它是我最喜欢的语言)的五个方面，排名不分先后。

As much as I am a fan of Java Generics, there are a lot of oddities that arise from the way it was designed. As such there a myriad of annoying limitations with generics (some of which are the result of type-erasure). The way Object.clone() and the Cloneable interfaces work is totally broken. Instead of taking the high-road and making everything an object (a.la. SmallTalk), Sun wimped out created two distinct categories of data-types: Objects and primitives. As a result there are now two representations for fundamental data types and wierd curiosities such as boxing/unboxing and not being able to put primitives in a Collection. Swing is too complex. Don't get me wrong: there's a lot of cool stuff one can do with Swing but it is a great example of over-engineering. This final complaint is equally the fault of Sun and those whom have written XML libraries for Java. Java XML libraries are way too complicated. In order to simply read in an XML file, I often have to worry about what parser I am using: DOM or SAX? The APIs for each is equally confusing. Native support in the language for easily parsing/writing XML would be very nice. java.util.Date sucks. Not only is it unnecessarily complicated but all the useful methods have been deprecated (and replaced with others that increase complexity).

Erlang不在此列表中。在我最喜欢的语言中，但有一些缺陷是肯定的:

Syntax. This includes the 3 terminating tokens (,;.) and aesthetics, but more generally on how the semantic meaning of the code is expressed in text. An example is on how all lowercase tokens are atoms, so to refer to a function you can't just name it, you have to fun my_function/1, and ?PRECEDE_CONSTANTS_WITH_QUESTION_MARKS. Coming from Scheme, Haskell, etc. you just wish you could use a name. Library support is lame. This is mostly external libraries, but even the old standard library. Newer versions of Erlang have sensible POSIX regexes, but the old one had a pretty horrible library for basic string manipulation. You also never know when you're getting the value, or {ok, Value}. Related: non-uniform tools for building and distribution. Ruby has gem and rake, RSpec. Perl has CPAN. I'm unaware of decent equivalents in Erlang. The few Erlang specific tools are pretty strange. Mnesia is a great database, but coming from SQL you have lots of trivialities to learn. Same with the documentation @spec, which has a strange way of describing signatures. Often the functional paradigm hurts when you just want that little bit of mutation. Supposing you want a Hash Table, you can't just hack it as in Scheme, or SML. ets and dets alleviate some of the pain, but not much.

第六,奖金:

模块的导入和导出语法是一堆失败，这与Java的80多行导入语句没有什么不同。

综上所述，Erlang是一种乐趣^_^

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

Perl

我喜欢这门语言，我不想添加已经被使用过的东西，但还没有人提到过这一点，所以我就把它扔到锅上。当我使用这个特性时，我发现这是我一生中最可怕的经历(而且我用过汇编语言):

write()和format()函数。

它们的语法是最糟糕、最丑陋、最可怕的，但是它们并没有提供比printf()更好的功能更多的功能。任何人都不应该尝试使用这两个函数进行任何输出，因为它们有多糟糕。

我相信有人会不同意，但是当我研究它们，希望它们能解决我的问题时，我发现它们是一个“痛苦的世界”(引用Big Lebowski的话)，我希望Perl6已经消除了它们，或者更好的是完全重写它们，使它们在某种程度上更可用和有用。

Python

错误/异常在调试时是模糊的 我工作时不用 在类中使用__init__， __repr__， __str__等 不能简单地编译可执行文件(.exe或其他) 还有一件事我还没试过，但肯定会让我心烦

对于所有的c语言程序员来说，self对我来说更有意义，因为对象引用的是它的self