最近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#(好吧,我猜一部分是VisualStudio IDE):

No covariance (yet), like Class<D> cannot be used in place of Class<B> even though type D derives from type B. Graphic designers don't support generic based inheritance (or inheritance from abstract classes), even though the inheritance itself works just fine if you work around the designer problems by adding extra inheritance levels just so designers always see concrete non-generic variants of your code. No constructor inheritance No constructors in where clauses of generic type parameters VisualStudio seems to have a tendency to mysteriously check out files (like project files and/or unit test definitions) when opening a solution, even though the files do not seem to actually get altered.

如果你明天再问我,可能会有不同的名单。即使协方差和设计师的麻烦将在我的前5名,直到他们被解决(随着方差添加到c# 4.0,这似乎已经发生了至少一个…)

其他回答

不得不假设我们有语言。我们做什么?

Python (3.1)

奇怪的无序T if C else F语法用于条件语句。 字节字面值看起来太像STR字面值了。我们应该得到x'414243'而不是b' abc '。 str在某些平台上是UTF-16,在其他平台上是UTF-32。(尽管至少比2要好。x字符串。) 具有相同的加法和连接运算符。这对numpy.array这样的类型很不利。 运行缓慢。

Python:

没有分隔符表示块的结束会导致歧义,这样自动缩进就不能处理格式不佳的代码。 没有宏(修饰符不算) 没有像haskell的cabal或perl的CPAN那样的库自动获取 不能声明变量const(是的,可以自己定义变量,但是…) 元编程被削弱 差点忘了全局解释器锁

Scala是我最喜欢的语言。五件讨厌的事?容易:

Takes a long time to learn properly. I know you can write Scala as a 'better java'. That is what we used to say about C++ and C too. I agree this is an inevitable consequence of the deep ideas in the language. But still ... Methods vs. Functions: def f(x: Int) = x*x defines a method f, not a function f. Methods are not functions despite a lot of early Scala tutorial material blurring the distinction. The language tries to blur it too because if you supply a method in some places where a function is expected it is accepted. Do we have to have both methods and functions? Yes it is fundamental. But it was initially confusing to me. Composing classes or objects from mixins in the 'cake' pattern is prone to NPE's. e.g. trait X { val host: String; val url = "http://" + host } is a mixin that will NPE on instantiation, or not, depending on its position in the class declaration. The compiler could tell you if it will fail but doesn't. (In 2.7 anyway.) It is hard to diagnose the problem in complex inheritance graphs. Arrays in 2.8 rely on implicits to mesh with the main scala collection types. But implicits are not applied everywhere. An Array can be supplied where a Seq is expected. But an Option[Array] cannot be supplied where an Option[Seq] is expected. I know there are no completely 'right' ways to handle java Arrays. Type erasure. Enough said.

Python,:

No switch keyword. And NO, dictionary is not a replacement for it. Not even a bunch of elif statements. Inconsistent line break handling. Why can I do: test = (1, 2, 3) And not: from itertools import cycle, islice, izip Why can't I do: if stuff \ and foo \ or bar: return "Formated string with %(arg)s" % \ {'arg': "bloody slash"} without using slashes? There is not one obvious and only one way to do it. Python fails on its motto just like Java failed on "Write once run anywhere". # what somebody from an another language would do if not test.has_key('foo'): test['foo'] = 0 n = test['foo'] = test['foo'] + 1 vs # what an agnostic beginer would do try: test['foo'] += 1 except KeyError: test['foo'] = 1 n = test['foo'] vs # what you end up after looking for dictionary default value in the python doc test.setdefault('foo', 0) n = test['foo'] = test['foo'] + 1 vs # what I would do n = test['foo'] = test.get('foo', 0) + 1 And the worst is that they don't do exactly the same thing. There are subtle differences. Choice between spaces and tabs. There should be no choice. Pick on, set it in stone and stop fighting. Why can you do that: test = {} test['foo'] = 0 but not: test = [] test[] = 0

附注:" ".join(l)是优秀的人。不要抱怨它,这并不明显,但考虑到迭代器模式,这是正确的方法。