最近Stack Overflow上有一群讨厌perl的人,所以我想我应该把我的“关于你最喜欢的语言你讨厌的五件事”的问题带到Stack Overflow上。拿你最喜欢的语言来说,告诉我你讨厌它的五件事。这些可能只是让你烦恼的事情,承认的设计缺陷,公认的性能问题,或任何其他类别。你只需要讨厌它,它必须是你最喜欢的语言。

不要拿它和其他语言比较,也不要谈论你已经讨厌的语言。不要用你最喜欢的语言谈论你喜欢的事情。我只是想听到你讨厌但能容忍的东西,这样你就可以使用所有其他的东西,我想听到你希望别人使用的语言。

每当有人试图把他们最喜欢的语言强加给我时,我就会问这个问题,有时是面试问题。如果有人找不出他最喜欢的工具的5个缺点,那他对它还不够了解,不能提倡它,也不能利用它赚大钱。他还没有在足够多的不同情况下使用它来充分探索它。他把它作为一种文化或宗教来倡导,这意味着如果我不选择他最喜欢的技术,我就错了。

我不在乎你用什么语言。不想使用特定的语言?那就不要。你通过尽职调查做出了明智的选择,但仍然没有使用它?好吧。有时正确的答案是“你有一个强大的编程团队,有良好的实践和丰富的Bar经验。改成Foo是愚蠢的。”


This is a good question for code reviews too. People who really know a codebase will have all sorts of suggestions for it, and those who don't know it so well have non-specific complaints. I ask things like "If you could start over on this project, what would you do differently?" In this fantasy land, users and programmers get to complain about anything and everything they don't like. "I want a better interface", "I want to separate the model from the view", "I'd use this module instead of this other one", "I'd rename this set of methods", or whatever they really don't like about the current situation. That's how I get a handle on how much a particular developer knows about the codebase. It's also a clue about how much of the programmer's ego is tied up in what he's telling me.

憎恨并不是衡量人们了解多少的唯一尺度,但我发现它是一个相当不错的尺度。他们讨厌的事情也让我知道他们对这个话题的思考有多好。


当前回答

C#

1)缺乏为值类型编写泛型的实际能力。例如,任何白痴(好吧,大多数白痴)都可以编写一个例程,用c++计算int, float, double等列表的标准偏差,它写起来很简单,易于阅读,并作为快速的非泛型代码执行。我认为,如果你能用c#写一些东西,接近于达到这三个中的任何一个,而在其他两个上又不荒谬,你就是一个真正伟大的程序员。

2)协方差和反方差,尽管这被添加到4。

3)非常糟糕的LINQ文档(好吧,并不是语言的一部分)。

4)尝试使用foreach/迭代器,当我每次都想做同样的事情,除了上次略有不同(如连接一串字符串与逗号之间的单词和最后两个)。如果我用一个IEnumerable来写它,它很难写和读,而用一个for (int I =0 I <…)它并没有好到哪里去,而且效率更低。

5)我知道我会收到抱怨,但是缺少受控的例外。这并不需要像在java中那样实现(框架开发人员确实提出了一些很好的观点,为什么他们没有这样做),但我很乐意看到编译器警告不喜欢受控异常的用户可以关闭。

其他回答

我讨厌Java的五个方面:

没有一级函数。 没有类型推断。 缺乏理智的默认值在eg图形。 NullPointerException不包含更多关于什么是null的信息。 毫无意义的“可配置”框架/服务提供者接口/工厂类/依赖注入系统的激增。可配置性几乎从未使用过,严重违反了DRY,代码的大小增加了四倍,易读性减少了一半。

我知道,我应该试试Scala。

C++

模板的语法 钻石传承问题 现代语言所拥有的标准库过多/缺乏(尽管boost也很接近)。 iostream IOStreams周围使用的语法

Python

空格是有意义的(有时) 强调关键词 有限的线程支持(至少目前) 用self代替this 空格是有意义的(有时)

VB。网

The behavior AndAlso / OrElse and And / Or seems backwards. Perhaps they should be switched. When can only be used for exception catching. The ability to do a When conditional would be nice for some other things. There is no friggin Refactoring in the VS IDE (not really the language's fault) like there is with C# Not <obj> Is Nothing. Yes, this has been remedied by IsNot, but for some reason I see the Not Is being used too often. (I see it much more frequently with devs who speak english as a second language, does it make better sense from that angle?) It doesn't require the () on ToString() and most functions. (Leads to sloppy coding habits) Having to do _ when breaking a line. It allows optional parameters. (Leads to sloppy coding habits) declaring an array is done by UpperBound and not by capacity. "Dim arr(2) as String" will actually hold 3 elements. Having = be a comparison and assignment operator.

Python:

Too slow! list operations don't return the list, so you can't do list.append(4).append(5). (I mean a reference to the same list, not a copy). This is a minor gripe; it's only come up a few times. statements don't return values (if, print, while, for, etc). This is only a problem when dealing with lambdas. lambdas can only be one expression. There's no real need for this restriction, as they are equivalent to functions in every other way. What if I want a button press event which calls two functions? I'd need to create a named function to supply that functionality to an action listener, while doing "lambda: f1(); f2()" would not hurt. you can only put standard a-zA-Z_0-9 as names. Having functions like "true?" and "+" would be great. Of course, this could lead to terrible obfuscation, but I'm not saying we immediately rename all functions to "p@$%3". Which do you find clearer to read: "dec2bin" or "dec->bin"? ("store_results" or "storeResults") or "store-results"?

Ruby

无类型推断 方法/函数不是一级对象 变量的范围不是词法的,尽管块变量的范围是词法的 Def内部的Def super和super()的区别