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

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


当前回答

Haskell

Sometimes the type system feels backwards. What if I don't want the compiler to infer types for my variables? What if I want the opposite, where it does constraint checking on said variables? For example, instead of inferring the type of the elements of a list, it instead makes sure that they all belong to a particular typeclass. This is a subtle but huge difference that makes it difficult for me to program UIs. It can be done, but it takes more effort than it does in some other languages. Haskell rocks for the non-UI parts, but the UI I leave to an untyped language. Allowing the construction of infinite values leads to some really frustrating errors sometimes. NoMonomorphismRestriction. Bytestring handling bites me in the ass sometimes and you don't know it until your program crashes because you mixed them up improperly. Something is wrong here, when we are losing type information that should have prevented this. Typeclasses should be automatically derived for trivial cases, like witness types, but there's a strong potential for abuse there.

其他回答

很多人认为Java很慢,但我同意一定程度的使用。

Java是戏剧性的。他们为你想做的一件事提供了很多课程。但是你知道灵活性属性XD。

Java一开始很难,但总是很有趣。

当你写一个简单的代码打印“Hello,World!”请不要使用java !XD我相信我是有道理的。

Java是一种混合,所以不要说它是纯粹的面向对象语言。

还有很多,但我只局限于5个XD。谢谢!

Emacs Lisp

目前还没有足够的商业市场让人们全职用elisp编码 GNU Emacs vs XEmacs不兼容 Scheme中的嵌套函数很整洁,我希望elisp有[1]的概念 用于简单遍历列表的do循环或其他一些工具不是标准的(当然,您现在可以使用lambda进行映射)[1] (function (lambda(…)))[1]应该有一个简写

当然,Lisp的一个美妙之处在于,用一行代码在你自己的代码中修复这些问题并不难。但这并不是与生俱来的,这让我很恼火。

好的问题;我有点不好意思,因为我想不出更好的东西来恨,但说实话,法官大人,没什么好恨的。

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"?

C

字符串操作。

必须手动处理字符串缓冲区是一个容易出错的痛苦。由于如此多的计算实际上是移动和修改字符串(计算机并不像人们想象的那样用于大型数字运算),因此能够使用托管语言或c++的字符串对象来处理这些非常好。当我必须在直发C时,感觉就像在流沙中游泳。

闲聊

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