最近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.

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


当前回答

以下是我不喜欢Java的一些地方(它不是我最喜欢的语言):

Generics type erasure (i.e. no reified generics) Inability to catch multiple exceptions (of different types) in a single catch block Lack of destructors (finalize() is a very poor substitute) No support for closures or treating functions as data (anonymous inner classes are a very verbose substitute) Checked exceptions in general, or more specifically, making unrecoverable exceptions checked (e.g. SQLException) No language-level support for literal collections No type-inference when constructors of generic classes are called, i.e. the type parameter(s) must be repeated on both sides of the '='

其他回答

VB。网

默认情况下弱类型(Option Strict修复了这个问题,但默认情况下没有启用) 在方法上不需要括号(myFunction而不是myFunction()等等) 是否使用括号来定义数组/使用(myArray(12)而不是myArray[12]) 不支持直接递增(i++) 是否支持遗留的On Error关键字和整个VB6-Namespace

Python:

处理数字太慢了。这不是什么大问题,除非…… 不能简单地在程序中包含导入时自动编译的C代码。 在py3k接管之前,我们仍然要忍受愚蠢的整数除法规则。 在py3k接管之前,像imap和izip这样的好东西仍然存在于一个单独的模块中。 在py3k接管之前,我们还有很多工作要做。

Lua

我喜欢这门语言,但是有一些事情困扰了我很多年!

No (built-in) support of binary operations (as of 5.1, it might come with 5.2). Should have a built-in binary buffer implementation, allowing for example in place long string concatenation. I know it doesn't fit well in the syntax, but sometime I miss longVariableName++ or verboseVariableName += 5. Reference assumes knowledge of C (I have it but it is a minus for newcomers) and defers some help to C reference! And sometime it is too terse. It is starting to have a good deal of libraries, but you have to get them from various places. On the other hand, the download is very small! ;-)

Javascript;

the dynamic binding of "this" is very confusing and dangerous if you don't know exactly what you're doing. a function declaration requires the keyword "function". It's not the typing I object to, it's the reading it when I want to do something slightly clever. Hrm now I think of it maybe that's a plus. Discourages me from doing clever things. As a result of number 2, it's often less code (in terms of characters) to just copy/paste a code segment than to declare it as a function, if it's a fairly short idiom. This unfortunately promotes bad practice, especially in my own code. Javascript makes motions at being a functional language by having first class functions and closures, but there's no way to verify referential transparency in a function, at either runtime or compile time. Without this, some architectures become either risky or bulky. Its fantastically bad reputation, and thus my inability to say "I program in javascript" to anyone without being laughed at.

C++

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

Python

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