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

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


当前回答

Python:

You usually have the entry point of the program at the end of the file. (Because if it calls any function defined in the module, it has to occur after those functions in the sources.) I hate it when you have to spend time looking for the entry point of a program, so I always have a simple main.py file with: def main(): ... if __name__ == '__main__': main() When an exception is raised, it can only be catched by the main thread. Or something like that. Destructors are quite useless, because when written in Python they may break garbage collection IIRC. I've never figured out how relative imports work in Python 2. I'd like to see more collections in the standard library. For example: linked lists, thread-safe collections, ...

其他回答

Ruby有许多与速度相关的缺陷,但我并不讨厌它们。它也有社区传福音过度的缺陷,但这并没有真正困扰我。以下是我最讨厌的:

Closures (blocks) have 4 different creation syntaxes, and none of them are optimal. The elegant syntax is incomplete and ambiguous with hashes, and the full syntax is ugly. The community tends to be against real documentation, favoring ‘read the code’. I find this childish and lazy. Metaprogramming abuse, particularly in libraries, makes bugs a nightmare to track down. On a related note, pervasive metaprogramming makes a comprehensive IDE difficult, if not impossible, to make. The way block passing to functions is done is silly. There is no reason blocks should be passed outside the parameter list, or have odd special syntax to access (yield). I am of the opinion that blocks should have been given a less ambiguous syntax (or hashes could have used different delimiters; perhaps <> rather than {}), and passing as parameters to methods should have been just like all other parameters. object.method(1, {|a| a.bar}, "blah") These oddities, like the block must be the last parameter passed and passing more than one block is different with longer syntax, really annoy me.

c# 4.0

“动态”关键字,被滥用的时机已经成熟。如果你想要/需要使用反射,使用并让它明显地显示你正在使用它,不要试图用动态来伪装它。

我使用Java,我最大的不满是字符串操作的低效率。当你使用+运算符时。说真的,难道编译器不能计算出我添加了多少字符串,然后在后台为我生成StringBuffer的东西吗?

通常,使用+的代码比StringBuffers操作序列更具可读性。

另外,我讨厌本机数组和集合框架之间的冗余。. toarray()的语法极其丑陋。

我讨厌Java的五个方面:

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

我知道,我应该试试Scala。

Self

没有真正的代码浏览器 数百个小窗户飞舞 周围。 只是一个研究项目, 不够稳定,没有活动 社区。 没有相当快的版本 适用于Linux或Windows。只有Mac OS X。 不支持标准键盘 命令。 哦!关于编写本地插件的文档也太过时了!