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

太容易随机破坏内存并创建几乎不可能找到的错误(尽管Valgrind在修复这个问题上走了很长的路)。 模板错误消息。 在使用模板时,很容易将所有内容都包含在一个文件中,然后进行愚蠢的编译。 标准库在现代是一个笑话(默认情况下仍然没有线程或网络?) 大量令人讨厌的C语言(特别是所有在short/int/unsigned/等之间的转换)。

其他回答

Python:

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

C++

(除了lambda函数,我已经避免了Cpp0X中可用的东西)

不强制使用"this"访问成员变量,::GlobalFunction访问全局命名空间。 (更具体地说,算法中缺少lambda函数,将在0x thou中修复)中的所有内容 处理依赖文件/头文件和源文件 基本数据类型上的愚蠢名称(应该命名为uint8, int16等) const_cast功能

Python

那些我不理解的…

math.ceil() and math.floor() return floats, not integers (probably to avoid an integer overflow in the underlying C function - but why not cast to a Python long?) len() is a function not a method reload() is very limited, does not reload a module 9 times out of 10, only reloads an imported label if it is a module - i.e. cannot do from bar import foo; reload(foo) if foo is not itself a module Mutable default arguments have a single reference (why not a new instance each function call?!) All these underscored variables - if they are so private, how come we see inbuilt ones so much in code? Get a namespace! Strings are not mutable - maybe there is a good reason for this but I have come across many situations where I would like to tweak one particular character ...

那些基于实现有意义但令人讨厌的……

array.sort()不返回数组(我认为它发生在原地) 列表/生成器推导式不定义新的作用域(只是for循环的语法糖,对吗?)

以及几个在Python 3中修复的

默认为整数除法 Global只能引用顶级名称空间

Python:

1) line continuation syntax: "...\" works, but "...\ " does not, and that trailing space is generally invisible, without unusual eol-marking by editer. 2) a bare 'raise' is invisible in the stack trace, as the stack trace looks like the previous raised exception. 3) slow 4) poor integration into web-servers (mod_python: dead, mod_wsgi: limited scope of operation). This is complicated by 3], requiring daemonization or some sort of memory-persistance to perform well. 5) overly tolerant of mixed tabs and spaces, allowing changes to control flow to sometimes remain hidden. (maybe fixed in recent versions)

REBOL

REBOL是我最喜欢的语言之一。我不能说我有一个最喜欢的,尽管Haskell排名也很高。

Its odd syntax scares off many developers before they even give it a try. use [email rules url] [ ; A small DSL that sends email to people about URLs. rules: [ some [ into [ set email email! set url url! (send/subject email url reform [ "Check Out" url ]) ] ] ] ; Global context notify: func [ [catch] dsl [block!] ] [ unless parse dsl rules [ throw make error! "You screwed up somehow." ] ] ] notify [ [ a@b.com http://www.google.com ] [ b@c.com http://www.yahoo.com ] ] Recursive dialects are very easy to validate with PARSE but very difficult to evaluate. (Stacks can be helpful here.) REBOL has very poor integration with many popular technologies, particularly XML. I suspect this is partly arrogance, because the REBOL BLOCK! datatype can do almost everything XML can do. However, the real world has XML in it. No Unicode. Thanks to AltMe, REBOL's user community is very insular. I can understand why they want to use AltMe. It's written in REBOL and shows off its strengths. Unfortunately it also puts them off on their own little island.

即将到来的REBOL 3有望解决许多这些问题,除了最后一个。