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

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


当前回答

我是在冒险,因为我不能全职使用它,但无论如何我会尝试一下!

Perl 6

func("frew") != func ("frew") It annoys me, but there is good reason for it. In Perl 5 print (5 + 6) * 10 still gets me every now and then It may be easier to parse than Perl 5 in a lot of places, but it still kills my editor sometimes It still has a lot of the line noise Perl 5 which scares a lot of people. That means it's harder to get them excited etc. There are no libraries yet. This will be a non issue if Perl 6 does indeed end up supporting Perl 5, but that may be a burden not worth bearing. There's no REPL, or what rubyists would call irb. A solid interactive Perl 6 with tab completion, color coding, etc, would make using and learning it so much nicer. Currently the documentation is basically the English spec. Not exactly an easy read. I know it's a stupid cliche, but it's not out yet! (I am allowed to complain because I am helping :-P)

前三点是语言;剩下的并不是语言本身,而是它还没有问世的事实。

其他回答

Haskell(包括所有GHC扩展,而不仅仅是Haskell'98的基础规范)。

我讨厌它的一点是:它不是主流。

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

CSharp / .NET

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

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

我讨厌所有语言的五件事(至少就我所知):

Does what I say/type, not what I mean Will undoubtedly meet people who think they are experts in the language, but just make a mess of it (e.g. people who insist that removing comments/unused local variables will speed up execution time for a program) Unless the language is obsolete, then it will probably continue to evolve (either the actual language, or the concepts behind using it effectively) requiring you to actively develop with it so as to not fall behind. Can't modify the lexer/compiler (add in own context sensitive grammar) No perfect language (every language is missing some sort of useful feature that usually is either impossible to simulate, will unavoidable have an ugly interface or just require far too much time to implement and get it right)

但这只是因为VB6毒害了整整一代程序员

我在一个曾经是VB6商店的VB . net商店工作,而在这里工作的每一个曾经是VB6开发人员的人都顽固地拒绝学习任何关于. net的知识。他们编写的代码就像VB6一样,他们的应用程序就像VB6应用程序一样糟糕。我的老板非常不鼓励使用LINQ,因为她担心其他人很难理解,这是事实,因为没有人想要理解它。

我认为如果微软只使用c#,我们会过得更好,这让我很难受,因为我认为花括号远不如VB的冗长结束语句。

帕斯卡对象:

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应该有自己的列表。