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

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


当前回答

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

其他回答

我可以为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 !

C#

当被枚举的集合中的对象发生变化时,foreach命令弹出, UI控件吐出假人,因为它们在错误的线程上访问。当然是所有的调度员。调用可以移动到CLR管道, PInvoke,编组等, 我浪费了两年时间学习远程遥控, 它没有露比性感。

Self

没有真正的代码浏览器 数百个小窗户飞舞 周围。 只是一个研究项目, 不够稳定,没有活动 社区。 没有相当快的版本 适用于Linux或Windows。只有Mac OS X。 不支持标准键盘 命令。 哦!关于编写本地插件的文档也太过时了!

Objective Caml

Non-concurrent garbage collector. I can write multi-threaded programs all day long, but they're only ever going to get one of my eight cores at a time. This makes me sad. No type classes (or their moral equivalent). There's Furuse-san's GCaml, but it's A) not quite as good as type classes, and B) not in the INRIA distribution. Badly in need of a Cocoa bridge. Seriously. If I wrote more code with actual interfaces to DNA-based life forms, then I'd probably break down and write the damned thing myself. Why hasn't anybody else done this yet? Functors are abominable. Seriously, modules ought to be first-class values. There should be only one kind of function. Read Montagu and Rémy before you flame me for this. Should use LLVM for its back-end. Who do I have to murder to get OCaml to compile for my stupid little ARM6 core?

是的,我有一些问题。我仍然非常喜欢这门语言。这太棒了。

C++

(除了lambda函数,我已经避免了Cpp0X中可用的东西)

不强制使用"this"访问成员变量,::GlobalFunction访问全局命名空间。 (更具体地说,算法中缺少lambda函数,将在0x thou中修复)中的所有内容 处理依赖文件/头文件和源文件 基本数据类型上的愚蠢名称(应该命名为uint8, int16等) const_cast功能