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

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


当前回答

Lua

我喜欢用Lua编程,但下面是让我头疼的事情:

没有办法用这种语言编写API——不像C .h文件或Java接口 语言有一流的功能,但有人忘记告诉设计库的人。 编写函数的语法太重量级了。 语法分为语句和表达式。 表达式形式是贫乏的:没有let形式,没有真正的条件表达式,……

尽管如此,我还是坚持认为Lua非常棒:-)

其他回答

Lua

If you do foo.bar(1,2) then 'self' is nil inside the bar method. You must remember to do foo:bar(1,2) instead. I'd rather have that switched ('self' should be defined by default unless you use the ':' operator, or you call a function that isn't a method). Variables are global by default. I'd rather ditch the 'local' keyword and have a 'global' one instead. Undeclared variables are assigned the nil. I'd rather receive an error message. You can sidestep this by manipulating the global env's metatable, but I'd rather have it implemented by default and be able to deactivate it. Multiple returned values on parameters are not handled very nicely. Say you have a function foo() that returns 1,2,3 (three values) and bar() returns 4,5 (two values). If you do print(foo(),bar()) you will get "1,4,5" ... only the "last" tuple is expanded on calls. The # (table length) operator only works in tables indexed with continuous integers. If your table isn't like that and you want to know how many elements does it have, you need to either parse it with a loop, or update a counter each time you insert/remove an element from it.

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

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

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

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.

Python,:

No switch keyword. And NO, dictionary is not a replacement for it. Not even a bunch of elif statements. Inconsistent line break handling. Why can I do: test = (1, 2, 3) And not: from itertools import cycle, islice, izip Why can't I do: if stuff \ and foo \ or bar: return "Formated string with %(arg)s" % \ {'arg': "bloody slash"} without using slashes? There is not one obvious and only one way to do it. Python fails on its motto just like Java failed on "Write once run anywhere". # what somebody from an another language would do if not test.has_key('foo'): test['foo'] = 0 n = test['foo'] = test['foo'] + 1 vs # what an agnostic beginer would do try: test['foo'] += 1 except KeyError: test['foo'] = 1 n = test['foo'] vs # what you end up after looking for dictionary default value in the python doc test.setdefault('foo', 0) n = test['foo'] = test['foo'] + 1 vs # what I would do n = test['foo'] = test.get('foo', 0) + 1 And the worst is that they don't do exactly the same thing. There are subtle differences. Choice between spaces and tabs. There should be no choice. Pick on, set it in stone and stop fighting. Why can you do that: test = {} test['foo'] = 0 but not: test = [] test[] = 0

附注:" ".join(l)是优秀的人。不要抱怨它,这并不明显,但考虑到迭代器模式,这是正确的方法。

Python:

1) line continuation syntax: "...\" works, but "...\ " does not, and that trailing space is generally invisible, without unusual eol-marking by editer. 2) a bare 'raise' is invisible in the stack trace, as the stack trace looks like the previous raised exception. 3) slow 4) poor integration into web-servers (mod_python: dead, mod_wsgi: limited scope of operation). This is complicated by 3], requiring daemonization or some sort of memory-persistance to perform well. 5) overly tolerant of mixed tabs and spaces, allowing changes to control flow to sometimes remain hidden. (maybe fixed in recent versions)