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

1-3:没有一个明显的打包/构建/文档系统的选择(比如Perl的cpan、POD或Ruby的gem、rake、rdoc)。 4: Python 3.0是不兼容的,需要两个源分支(2。x和3.x)用于每个Python项目。但是Python 3.0的不兼容性还不足以证明它的合理性。大多数py3k的优势都太微妙了。 5: Jython, IronPython, CPython不兼容。

其他回答

C++

cryptic error-messages when templates are involved lack of template constraints (many cases can be worked around with template metaprogramming, but this will result in unreadable code (at least for average programmers) in most cases) pointer to member-function syntax c++ standards committee should release offical standards more often (or at least release separate updates to the standard library itself), i mean really TR1 was released 2005, and we still dont have a shared_ptr, bind and alike in the standard library. -

Python

错误/异常在调试时是模糊的 我工作时不用 在类中使用__init__, __repr__, __str__等 不能简单地编译可执行文件(.exe或其他) 还有一件事我还没试过,但肯定会让我心烦

对于所有的c语言程序员来说,self对我来说更有意义,因为对象引用的是它的self

VBA(含MS Office IDE):

1)文件不足 2)错误信息差 3)数组操作例程不足 4)必须重复DIM语句的类型 5)无法彩色打印(必须购买第三方插件)

C++

编写一个简单的代码片段要花很多时间。 对于(std::vector::const_iterator iter =[…] Vector.remove()不移除。 Vector.push_front()不存在。 头文件 没有λ 如果至少有一个虚函数,则没有自动空虚析构函数。

c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的,明天问我,我会想出一个不同的5个:)