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

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


当前回答

HyperTalk:

很久很久以前就死了 没有简单的赋值(你不能说a:= 3,你必须说把3放进a 没有嵌套函数 没有真正的数据结构,只有字符串。要创建“列表”,您可以使用itemDelimiter分隔项并手动转义它们。你也可以得到行和单词比如txt的第5行第2个单词

说句题外话,我认为HyperTalk最酷的独特功能之一是特殊的it变量:

ask "How many years old are you?"
answer "You are " & it*12 & " months old."

其他回答

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是一种乐趣^_^

C#

泛型参数是不变的,c# 4.0为泛型类型引入了协方差和逆变性 可覆盖的类成员必须显式地标记为virtual

Java

缺少无符号数字数据类型 基本数据类型不是对象

C

字符串操作。

必须手动处理字符串缓冲区是一个容易出错的痛苦。由于如此多的计算实际上是移动和修改字符串(计算机并不像人们想象的那样用于大型数字运算),因此能够使用托管语言或c++的字符串对象来处理这些非常好。当我必须在直发C时,感觉就像在流沙中游泳。

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)额外答案:“@”。如果你懒得写正确的代码,那就添加'@',这对以后调试你的代码的人来说太糟糕了。

我是在冒险,因为我不能全职使用它,但无论如何我会尝试一下!

Perl 6

func("frew") != func ("frew") It annoys me, but there is good reason for it. In Perl 5 print (5 + 6) * 10 still gets me every now and then It may be easier to parse than Perl 5 in a lot of places, but it still kills my editor sometimes It still has a lot of the line noise Perl 5 which scares a lot of people. That means it's harder to get them excited etc. There are no libraries yet. This will be a non issue if Perl 6 does indeed end up supporting Perl 5, but that may be a burden not worth bearing. There's no REPL, or what rubyists would call irb. A solid interactive Perl 6 with tab completion, color coding, etc, would make using and learning it so much nicer. Currently the documentation is basically the English spec. Not exactly an easy read. I know it's a stupid cliche, but it's not out yet! (I am allowed to complain because I am helping :-P)

前三点是语言;剩下的并不是语言本身,而是它还没有问世的事实。