最近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.
憎恨并不是衡量人们了解多少的唯一尺度，但我发现它是一个相当不错的尺度。他们讨厌的事情也让我知道他们对这个话题的思考有多好。
MEL(玛雅表达语言):
Single dimensions arrays: Forcing me to manually sync two or more lists, or use delimited strings to simulate more complex data structures. Naturally, they're immutable too.
Single threaded and slow: Causing the entire Maya application to hang while it completes a task. Bonus points for not being able to kill long operations, instead having to close and re-open Maya.
Script sourcing paths aren't recursive: Meaning every directory you want to store scripts in must all be added to the script path.
No namespaces: Forcing the inconsistent use of naming conventions to make sure global procedures don't collide.
Modal commands: Each command is modal, meaning the Create, Modify, and Query operations are all handled by setting flags. This also forced the developers to cause most of the commands to return arrays
Inconsistent command style: Most array commands actually return arrays, but the Tokenize command has to take an array as a reference which it then populates, rather than spitting out an array. This among other inconsistencies.
这些以及其他几个原因是AutoDesk采用Python作为次要脚本语言的原因，这带来了其他一些令人讨厌的因素:
并不是所有的MEL命令都受支持:大多数都受支持，但有时您会发现自己不得不使用MEL()函数来执行一些任意代码。更糟糕的是，你不得不对它进行所有烦人的逃避。
继承了模态命令风格:必须使用相同的create=True, query=True, edit=True的东西。
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).
JavaScript:
All the coolest things are insanely complex, but then, all the coolness is also wrapped up in such a small amount of code that you feel stupid for struggling to follow it
'+' is an absurd choice of operator for concatenation in a weakly-typed language. Were they trying to scare off the noobs?
It's a cross-browser compatibility minefield (never mind if it's even turned on or not)
It's generally untrusted - associated with scummery such as blocking the back button, pop-ups that never die, etc.
It's nearly impossible to debug because there are only a few different error messages and a few different types (Number, String, Object, etc.)
如果不是jQuery，我可能还是会像以前一样讨厌它:)
JavaScript
Function object syntax:
f = new Function( "foo", "bar", "return foo+bar;" );
(It takes n arguments, the first n-1
are arguments for the function, then
nth is the actual function, in
string form. Which is just silly.)
Function arguments can be
repeated.
f = new Function( "foo", "foo", "return foo;" );
The last repetition is the only one
ever used, though:
f( "bye", "hi" ) // returns "hi"
f( "hi" ) // returns undefined
E4X should just die. My users are
always complaining that it doesn't
work the way they think it will.
Let's face it, when you need a page
and a half of psuedocode for a
setter, it's time to rethink things.
A standard notion of
stdin/stdout/stderr (and files!)
would be nice.
null != undefined
It's irritating to have to handle
them both. Sometimes it's useful,
but most languages manage to limp
along fine with one.
