最近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#
5. 空合并运算符
的? ?运算符允许你写:
x = y ?? z;
而不是:
x = (y == null) ? y : z;
我喜欢这个运算符，但我想要另一个:
x = y ??? y.foo() : z.foo();
而不是
x = (y == null) ? y.foo() : z.foo();
我一直在使用这种东西，而且我发现输入== null部分很烦人。
4. 平等应该有更好的支持
我必须启动每个Equals(object obj)方法:
MyClass other = obj作为MyClass;
If (other == null)返回false;
你只需要写:
public override bool Equals(MyClass other) {...}
语言应该注意提供Equals(object obj)方法。
注意:other必须保证不为空。
3.不能使用不同类型的三元运算符
这不能编译，我认为它应该编译!
string foo = "hello";
int bar = 4;
object baz = foo == null ? foo : bar;
2. 缺少命名空间private
我喜欢内部保护，但我希望有一种保护只允许从同一名称空间内进行访问。这样可以更好地控制大型类库的访问。
1. 没有多重继承
我实际上只对接口的默认实现使用实现(类)继承，但很多时候我想这样做。
Python:
No standard GUI toolkit (the community goes round and round about this but never seems to settle on anything).
The evolution of tools and methods to distribute and install Python apps and libraries has been, well, rocky. (Although lately this seems to be moving closer to getting fixed.)
CPython is still slow as interpreters go (although PyPy is looking pretty good these days, if it becomes the "standard" Python this problem goes away).
You can't subclass built-in classes (e.g., list and dict) without overriding a lot of methods, even if all you want to do is a simple hook into an event (e.g., to hook into an item being added to or removed from the list, you need to override delitem, append, extend, insert, pop, and remove--there's no subclassable "change" event notification, nor any "protected" methods that factor out common code used by all the above methods).
Up until virtualenv was invented, keeping separate Python environments for different purposes on one machine was a real pain.
