最近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、delphi、c#或ruby进行开发(这是不切实际的,因为我公司的主要开发语言是c#、delphi和java)。 从左到右的评估。 有类注释但没有方法注释(至少在Squeak中) 没有真正的标准库,在细节上有很多差异 缺少名称空间

其他回答

Haskell。

默认情况下导入Prelude。 类型类的范围是通用的。 模块不是一流的。 类型不能依赖于值。 单子不统一Functor。

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! ;-)

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()的区别

Haskell:

惰性计算导致空间泄漏。 数字层次结构不是根据数学抽象构造的。 严格的单元IO会使调试更加困难。 大型实现处理I/O的方式似乎与标准不太兼容。(特别是,输出字符只输出低8位——然后构建代码,使用这个假设来执行二进制I/O。我吐!) ($)运算符的结合性可以被改变以使某些表达式更漂亮。

大多数问题都不会上升到讨厌的程度,有些人试图解决或为每一个问题构建可靠的变通办法。

编辑:关于第5点有些困惑。特别是有些人似乎认为我指的是论证的顺序,但我不是。我不解释我的意思,我只想让人们去下面的链接http://hackage.haskell.org/trac/haskell-prime/wiki/ChangeDollarAssociativity,它很好地表达了我的意思。