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

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


当前回答

Javascript;

the dynamic binding of "this" is very confusing and dangerous if you don't know exactly what you're doing. a function declaration requires the keyword "function". It's not the typing I object to, it's the reading it when I want to do something slightly clever. Hrm now I think of it maybe that's a plus. Discourages me from doing clever things. As a result of number 2, it's often less code (in terms of characters) to just copy/paste a code segment than to declare it as a function, if it's a fairly short idiom. This unfortunately promotes bad practice, especially in my own code. Javascript makes motions at being a functional language by having first class functions and closures, but there's no way to verify referential transparency in a function, at either runtime or compile time. Without this, some architectures become either risky or bulky. Its fantastically bad reputation, and thus my inability to say "I program in javascript" to anyone without being laughed at.

其他回答

Python。

虽然前面提到了python处理作用域的奇怪方式,但我觉得最糟糕的结果是:

import random

def myFunction():

    if random.choice(True, False):
        myString = "blah blah blah"

    print myString

也就是说,if块内部的作用域与函数的其余部分相同,这意味着变量声明可以出现在条件分支内部,并且可以在条件分支外部访问。大多数语言要么阻止你这样做,要么至少为你提供某种严格的模式。

此函数有时会成功,但有时会抛出异常。虽然这是一个人为的例子,但这可能会导致一些微妙的问题。

C#

No easy way to check if a type is Numeric It means you are probably stuck using most of the microsoft stack, IIS and MSSQL Instead of being a specific tool for a specific problem, C# tries to be a language for every paradigm. Lack of community. Sure, there are starting to be open-source frameworks and libraries for C#. The same ones that have been available to Java developers for years. Hard to find good help. The internet is littered with poor examples of how to solve problems with C#. This goes back to problem #3.

我可以为Python添加另一个:

给定一个列表l = [l1, l2,…], ln],那么repr(l) = [repr(l1), repr(l2),…, repr(ln)],但str(l) != [str(l1), str(l2),…, str(ln)] (str(l) = repr(l))。之所以这样做,是因为列表中可能有模糊的条目,如l = ["foo], [bar,", "],["], str(l)将返回"[foo], [bar,],[]",这“可能会使用户感到困惑”。然而,这使得str不可能仅用于转储数据,因为list杀死了“仅以可读格式转储数据”。Augh !

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.

ColdFusion

大型Flash表单的编译时间。 动态变量类型(有时我讨厌它们) CFScript缺乏特性。 CFTable(永远不能正确显示)。 CFChart中缺少图表类型。 完全缺乏NTLM支持(企业就绪-是的) cfc中的低能变量作用域 没有一个真正的NULL的概念-你的变量只是消失! 没有办法测试某些东西的存在(比如作用域,只是它们内部的成员)