最近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.
憎恨并不是衡量人们了解多少的唯一尺度，但我发现它是一个相当不错的尺度。他们讨厌的事情也让我知道他们对这个话题的思考有多好。
Python
No statements in lambdas. GRRRR
foo( a for b in c if d ) feels wrong, it surprises me every time I get away with it. Shouldin't it be foo( (a for b in c if d) )?
Can i have a dict comprehension?
map and filter operators have special syntax in list comprehensions, how about something for reduce? or sort?
Just by having a yield statement in it, a function is magically transformed into a generator, and its interface changes completely. Also, that generator cannot do any work before the first next(). at least, not without using a function that returns a generator.
JavaScript
No brief syntax for making modular code libraries. You have to call a function that returns a dictionary of public methods. And you have to edit that in (at least) two places every time you alter the interface of your module.
Creating closures involves returning it from a function that returns a function from ('sup dog) yo' function. Clutter!
for each ( foo ) syntax and behavior feels like an afterthought.
Knowing when your code will actually run (and in what order) is more of a dark-art. The only way to get it right for sure is put everything (yes, that too) in one big file. and even then you still need to wait for a document.onload
Am i missing something? is there no trivial way to get json serialized values without building them by hand? (yes jQuery can do this, sort of).
Erlang不在此列表中。在我最喜欢的语言中，但有一些缺陷是肯定的:
Syntax. This includes the 3 terminating tokens (,;.) and aesthetics, but more generally on how the semantic meaning of the code is expressed in text. An example is on how all lowercase tokens are atoms, so to refer to a function you can't just name it, you have to fun my_function/1, and ?PRECEDE_CONSTANTS_WITH_QUESTION_MARKS. Coming from Scheme, Haskell, etc. you just wish you could use a name.
Library support is lame. This is mostly external libraries, but even the old standard library. Newer versions of Erlang have sensible POSIX regexes, but the old one had a pretty horrible library for basic string manipulation. You also never know when you're getting the value, or {ok, Value}.
Related: non-uniform tools for building and distribution. Ruby has gem and rake, RSpec. Perl has CPAN. I'm unaware of decent equivalents in Erlang.
The few Erlang specific tools are pretty strange. Mnesia is a great database, but coming from SQL you have lots of trivialities to learn. Same with the documentation @spec, which has a strange way of describing signatures.
Often the functional paradigm hurts when you just want that little bit of mutation. Supposing you want a Hash Table, you can't just hack it as in Scheme, or SML. ets and dets alleviate some of the pain, but not much.
第六,奖金:
模块的导入和导出语法是一堆失败，这与Java的80多行导入语句没有什么不同。
综上所述，Erlang是一种乐趣^_^
PHP:
1)强迫我创造不必要的变量:
$parts = explode('|', $string);
$first = $parts[0];
2) lambdas的实现如此蹩脚，它大致相当于使用eval()，而且如此糟糕，我从未使用过它(参见http://www.php.net/create_function)。
3) try/catch系统只能捕获大约80%可能发生的错误。
4) Regex支持和lambda支持一样蹩脚，因为它必须在常规字符串中编写，这使得最难学的编程工具之一变得困难了三倍。PHP应该是一种“简单”的语言吗?
5)没有办法安全地从$_POST中取出东西，而不写两次或构建自己的函数，或使用'@'操作符:
$x = isset($_POST['foo']['bar']) ? $_POST['foo']['bar'] : null;
6)额外答案:“@”。如果你懒得写正确的代码，那就添加'@'，这对以后调试你的代码的人来说太糟糕了。
Ruby有许多与速度相关的缺陷，但我并不讨厌它们。它也有社区传福音过度的缺陷，但这并没有真正困扰我。以下是我最讨厌的:
Closures (blocks) have 4 different creation syntaxes, and none of them are optimal. The elegant syntax is incomplete and ambiguous with hashes, and the full syntax is ugly.
The community tends to be against real documentation, favoring ‘read the code’. I find this childish and lazy.
Metaprogramming abuse, particularly in libraries, makes bugs a nightmare to track down.
On a related note, pervasive metaprogramming makes a comprehensive IDE difficult, if not impossible, to make.
The way block passing to functions is done is silly. There is no reason blocks should be passed outside the parameter list, or have odd special syntax to access (yield). I am of the opinion that blocks should have been given a less ambiguous syntax (or hashes could have used different delimiters; perhaps <> rather than {}), and passing as parameters to methods should have been just like all other parameters.
object.method(1, {|a| a.bar}, "blah")
These oddities, like the block must be the last parameter passed and passing more than one block is different with longer syntax, really annoy me.
