最近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.
憎恨并不是衡量人们了解多少的唯一尺度，但我发现它是一个相当不错的尺度。他们讨厌的事情也让我知道他们对这个话题的思考有多好。
第一个帖子，所以对我放松点:)…很棒的社区网站，顺便说一句!
我试着阅读其他所有的c#回复，这样我的回复就不会重叠了
c#……排名不分先后:
1) switch语句中的case没有fallthrough。如果没有转机……为什么必须显式的类型中断;呢?这只是弱智和令人困惑，因为它意味着没有休息的能力;!!
2)不能在子作用域中声明同名变量，但可以声明与类变量同名的变量?要么都允许，要么都不允许。否则，就没有意义了。
3)函数中没有可选/默认参数
4) finally{}中的异常应该隐式地捕捉每一行。或者至少，只有NullReferenceException异常。例如，在访问数据库后，应该总是清理。所以，finally块应该看起来像这样:
finally
{
if(par1 != null)
par1.Dispose();
if(comm != null)
comm.Dispose();
if(conn != null)
conn.Dispose();
}
如果可以写成这样，就会简洁得多:
finally
{
par1.Dispose();
comm.Dispose();
conn.Dispose();
}
但是，不……你必须检查你是否正在访问一个空对象，否则它可能会从finally块抛出一个NullReferenceException。谁真的需要finally块中的异常呢?
5)泛型:你可以指定new()来实例化你的泛型对象，但是这个对象需要有一个默认构造函数。为什么不能指定一个签名，这样就不需要在还没有空构造函数的情况下创建空构造函数，而只使用已有的构造函数。
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)是优秀的人。不要抱怨它，这并不明显，但考虑到迭代器模式，这是正确的方法。
REBOL
REBOL是我最喜欢的语言之一。我不能说我有一个最喜欢的，尽管Haskell排名也很高。
Its odd syntax scares off many developers before they even give it a try.
use [email rules url] [
; A small DSL that sends email to people about URLs.
rules: [
some [
into [
set email email!
set url url!
(send/subject email url reform [ "Check Out" url ])
]
]
]
; Global context
notify: func [ [catch] dsl [block!] ] [
unless parse dsl rules [
throw make error! "You screwed up somehow."
]
]
]
notify [ [ a@b.com http://www.google.com ] [ b@c.com http://www.yahoo.com ] ]
Recursive dialects are very easy to validate with PARSE but very difficult to evaluate. (Stacks can be helpful here.)
REBOL has very poor integration with many popular technologies, particularly XML. I suspect this is partly arrogance, because the REBOL BLOCK! datatype can do almost everything XML can do. However, the real world has XML in it.
No Unicode.
Thanks to AltMe, REBOL's user community is very insular. I can understand why they want to use AltMe. It's written in REBOL and shows off its strengths. Unfortunately it also puts them off on their own little island.
即将到来的REBOL 3有望解决许多这些问题，除了最后一个。
Python:
我仍然是python的一般用户，所以我的抱怨可能只是知识的锁或误用。欢迎提出意见。我很喜欢这门语言。
Poor thread support and GIL. If you'd like to take use of multicore platform, most of the python programmers would probably recommend multiprocessing or some sort, don't use threading. It wouldn't give you the performance you are expecting.
property only for instance variable. _class_var = property(classmethod(some_method)) just wouldn't work. How can I get a property wrapped class variable?
no access control. All access controls are syntax mangling. Like private is __private, protect is _protected, etc... And hope that everyone programs python follows the naming convention. Come on, we can do better than that.
I agree the python philosophy of being simple and clear syntax but some simple and clear syntax not being supported seems lock of good judgement, in my opinion. Such as, a++, ++a, a-- and --a, self-de/increment, what's wrong with those? foo = (a > b ? a : b) unary operation, what's wrong with those? (I know py2.6 has something similar introduced, but given the massive support of almost every other language for those simple syntax, why reinventing the wheel? why not just follow the best practice? Shouldn't a good thing just keep in its good "form"?)
Program to interface. Python has no interface or abstract class concept (py3k has something called abc), everything is concrete. Providing an "interface" or "abstract" keyword to build class skeleton and guard class inheritance and extension wouldn't be a bad idea I think. It helps on top-down design. Currently, I just have to fill the each of methods with NotImplementedError, quite a tedious job.
I have to add this. version less than 3.x has str and unicode types. This is a true nightmare. It makes ascii and non-ascii/unicode mixing most likely to fail (bad, bad)
我看到人们抱怨速度。我不明白。它是一种解释语言，代码直到运行时才编译成机器代码，这就是它的本质。你不能比较解释语言和编译语言的速度。据我所知，在解释/脚本语言中，python并不慢。
