R

不是我最喜欢的语言，但我经常使用它，有很多抱怨……

S3对象只是美化了的列表，S4类仍然将所有数据公开给用户 赋值操作符可以是<- ->或=，参见Mike Dewar的咆哮 我的。var是一个非常令人困惑的OO语言变量命名约定，参见谷歌的风格指南 我不应该后悔使用循环 神秘的错误消息

德尔菲:

IDE有点不稳定。 代码洞察有时令人困惑。 调试有时是有bug的。 更新多个项目文件可能会很麻烦。 如果启动时一个或多个包不可用，错误消息会弹出几次。

再给c++投一票…仍然是我最喜欢的语言，有几个亲密的追随者——C和Python。以下是我目前最讨厌的名单，排名不分先后:

Plethora of integer types inherited from C - way too many problems caused by signed vs. unsigned mistakes Copy constructors and assignment operators - why can't the compiler create one from the other automatically? Variable argument madness - va_list just doesn't work with objects and I'm so sick of problems created with sprintf(), snprintf(), vsnprintf(), and all of their relatives. Template implementation is required to be fully visible at compile time - I'm thinking of the lack of "export" implementations or at least usable ones Lack of support for properties - I want to have a read-only member like "a.x" that can be read publicly and only assigned internally. I really hate the "val=obj.getX()" and "obj.setX(val)". I really want properties with access control and a consistent syntax.

我是在冒险，因为我不能全职使用它，但无论如何我会尝试一下!

Perl 6

func("frew") != func ("frew") It annoys me, but there is good reason for it. In Perl 5 print (5 + 6) * 10 still gets me every now and then It may be easier to parse than Perl 5 in a lot of places, but it still kills my editor sometimes It still has a lot of the line noise Perl 5 which scares a lot of people. That means it's harder to get them excited etc. There are no libraries yet. This will be a non issue if Perl 6 does indeed end up supporting Perl 5, but that may be a burden not worth bearing. There's no REPL, or what rubyists would call irb. A solid interactive Perl 6 with tab completion, color coding, etc, would make using and learning it so much nicer. Currently the documentation is basically the English spec. Not exactly an easy read. I know it's a stupid cliche, but it's not out yet! (I am allowed to complain because I am helping :-P)

前三点是语言;剩下的并不是语言本身，而是它还没有问世的事实。

C++

The inconsistencies in the libraries related to char* and std::string. All C++ libs should take std::strings. Characters are not bytes with respect to iostream. I do a lot of byte-oriented work. Having a "byte" type and a "character" type would significantly make it simpler. That, too, would permit scaling to Unicode somewhat easier. Bit operations should be easy on a value. I should be able to access and set the n'th bit of a value without playing AND/OR dancing. The lack of a standardized interface for GUIs. This is where Microsoft has really been able to position themselves well with C#. A standard interface binding that OS makers provide would go really far for my work.

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