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

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


当前回答

帕斯卡对象:

There's a lot of jumping back and forth in the file you're editing since the interface and implementation are split into two parts but still jammed into the same file. Dynamic indexing of arrays, strings start at 1, you specify the starting index when declaring fixed arrays and dynamically allocated arrays always start at 0. Classes and objects (not to speak of interfaces) are bolted on top of the language and among other things can't be stack allocated like records can. When calling functions without parameters the () are optional, leading to a lot of pain when you are dealing with function pointers or trying to refer to the result of a function using the function name. Parameter lists can't handle fixed array types or function pointer types without external type definitions.

这仅仅是一种语言,一个标准库的遗憾借口,而脆弱的IDE应该有自己的列表。

其他回答

c#中缺少预处理器。

我知道他们把它放在一边是因为有些人会滥用它,但我认为他们把孩子和洗澡水一起倒掉了。代码生成被认为是一件好事,在c++中,预处理程序是我的第一个代码生成器。

Haskell:

空间泄漏——懒惰的默认代价——也许代价太高了? 甚至像head和tail这样的纯函数也会调用错误并引导您进入IO。 fail from Monad -带回MonadZero。 Num类-(+)应该在AdditiveGroup或类似的类型中。 那个单子不是一个应用程序。

Common Lisp

缺少提供更现代功能的标准库(套接字,线程,…) 是否可以使用映射到本机窗口系统的标准化UI Scheme将lambda表达式赋值给变量并将变量直接作为函数调用使用的能力看起来比APPLY for FUNCALL更整洁。我猜这是使用多个名称空间的副作用 标准化的库源代码级打包系统,以便可以从多个实现中轻松使用它们

我想知道强类型的口齿不清会是什么样子

Clojure

Lack of built-in syntax for optional and keyword parameters in function definitions. Sure, you can add it easily enough, but that means library writers don't use it. Pervasive destructuring hasn't proven to be a good substitute yet Lack of method combination (before/after/around methods of the sort found in Common Lisp) Too much reliance on Java interop, e.g. there's no built-in file IO Sometimes I want static typing. This one isn't pure hate; I usually prefer dynamic, and attempts to mix the two have been largely unsatisfactory There's no built-in fast binary serialization format for the built-in data structures, though I hear people are working on it

我只有一个,但我相信它值得分享。

CSharp / .NET

我们有Length属性来获取数组中的元素个数,还有Count属性来获取集合中的元素个数。如果考虑到CLR在后台自动将IList、ICollection、IEnumerable添加到基于零的一维数组,那么它看起来就更奇怪了。

我相信CLR团队和BCL团队在讨论这个问题时遇到了困难;)