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

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


当前回答

Objective-C / Cocoa / Cocoa Touch:

Lack of namespaces Difficulty using primitive values with any of the interesting and powerful techniques of Cocoa, e.g., distributed objects, notifications, KVO Inconsistency with the use of the shortcut dot syntax for accessing properties, often having to use the full length accessors No GC on the iPhone, and generally GC came rather late to an otherwise highly dynamic language Inconsistent library support, at least in Cocoa Touch; some very basic things have only recently gotten high level support, e.g., audio handling. Lack of blocks!

其他回答

PHP

没有构造函数重载 不一致的函数命名(str_replace,但strtolower) define()不像c++那样逐字替换全局变量。 在与XHTML组合时,像if-语句这样的语句必须以不缩进开始,即使为了保持XHTML缩进一致,XHTML是缩进的。

Ex:

你必须输入:

<?php
if($x == NULL)
{
?>
                     <p><?= $x . ' is null' ?></p>
<?php
}
?>

错误捕获非常糟糕

(不知道为什么又把5号改成了1号,随便了)

JavaScript:

The Object prototype can be modified. Every single object in your program gets new properties, and something probably breaks. All objects are hash maps, but it's difficult to safely use them as such. In particular, if one of your keys happens to be __proto__, you're in trouble. No object closure at function reference time. In fact, no object closure at all -- instead, this is set whenever a function is called with object notation or the new operator. Results in much confusion, particularly when creating event callbacks, because this isn't set to what the programmer expects. Corollary: calling a function without object notation or the new operator results in this being set equal to the global object, resulting in much breakage. Addition operator overloaded to also perform string concatenation, despite the two operations being fundamentally different. Results in pain when a value you expect to be a number is in fact a string. == and != operators perform type coercion. Comparisons between different types involve a list of rules that no mortal can remember in full. This is mitigated by the existence of === and !== operators. Both null and undefined exist, with subtly different, yet redundant meanings. Why? Weird syntax for setting up prototype chains. parseInt(s) expects a C-style number, so treats values with leading zeroes as octal, etc. You can at least parseInt(s, 10) but the default behaviour is confusing. No block scope. Can declare the same variable more than once. Can use a variable without declaring it, in which case it's global and probably breaks your program. with { }. Really difficult to document with JavaDoc like tools.

.NET框架(库)

嵌套类型很少使用(例如MessageBoxButton应该是MessageBox.Button) 可变结构体(Rect, Point) 系统名称空间中有太多东西 太多不同的平等概念(对象。等于,对象。ReferenceEquals, operator ==, operator !=, IComparable.CompareTo() == 0) 数组的成员是可变的,但长度是不变的。

还有一点:

XmlSerialization不适用于不可变类型

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

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

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

Lua

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

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

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