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

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


当前回答

我有一本书探讨了SNOBOL中的各种项目。第一章探讨了SNOBOL编程和语言的历史和文化,并花了一些时间论证一个优秀的程序员喜欢一种语言不是因为它的缺陷,而是尽管有缺陷。

我最喜欢的语言是Icon/Unicon。但还是有一些事情让我很恼火:

它不是很出名,也不是很受欢迎。 与PHP、Perl、Java等相比,它的库要小得多。数据库访问是通过ODBC完成的,这实际上非常烦人。 对于所有其他出色的列表处理,我想念PHP内置的explosion()和implode()。 它没有表常数。列表,是的,表格,不是。 它是一种编译(实际翻译)语言。

其他回答

C

No parametric polymorphism (i.e. C++ templates). It makes writing reusable data structures and algorithms a pain (and there's hardly any static checking). See for instance the comparator argument to qsort and bsearch: the comparator takes void pointers :( No library of data structures. I really hate writing my own hash table. I also really hate scouring the web for a library of reusable data structures. Especially if it turns out to be incomplete. Strings. Inefficient representation, unwieldy if you make it sane, too hard to safely input a string. No standard for snprintf. Too hard to create a format string with sprintf, then use that to create a string with sprintf again, in a safe way. Only lexical macros. If different compilers expects function annotation in different places, I have to put the same HAS_NO_SIDE_EFFECTS in different places. Why can't I just grab the function, switch over the compiler type, and then insert it at the right place by a macro call? No portable libraries for common functionality. For sockets and threading, I use SDL---a frigging game library. For .ini-style parsers, the only library I could find which was packaged for ubuntu, I posted on the daily wtf (it calculates an array of hash values, then does a linear scan through it...)

C++

Template syntax is heavy and unweildy. Let's see, for(map<string, int>::const_iterator it = mymap.begin(); it != mymap.end(); ++it). Design errors in the STL. Should changing allocation strategy for your vector really change its type? Overly complex type system. Type T1 has a convert-to-T2 method, and T2 has an implicit from-T1 constructor. Which is called? How does overloading, overriding and multiple inheritance interact? Poorly, I guess... Incredibly long and unwieldy error messages from templates. You know what I mean... References means you can't see output parameters at call sites. In C, you can guess what foo(bar, &baz) can and can't modify.

以下是我不喜欢Java的一些地方(它不是我最喜欢的语言):

Generics type erasure (i.e. no reified generics) Inability to catch multiple exceptions (of different types) in a single catch block Lack of destructors (finalize() is a very poor substitute) No support for closures or treating functions as data (anonymous inner classes are a very verbose substitute) Checked exceptions in general, or more specifically, making unrecoverable exceptions checked (e.g. SQLException) No language-level support for literal collections No type-inference when constructors of generic classes are called, i.e. the type parameter(s) must be repeated on both sides of the '='

C

bit fields -- they aren't well specified by the language and how they work is compiler dependent and architecture dependent. It's often hard to find where a particular symbol is defined in a large mass of code, esp. if that symbol is produced by a macro. Which reminds me... The preprocessor is a rather ugly hack, amenable to all sorts of abuse. lack of standard sized integers (remedied by uint*_t lately, but there is lots and lots of old code floating around out there with custom typedefs or #defines for DWORD, WORD, BYTE, etc.) Lack of something akin to Perl's cpan.org (would love to be wrong about that one.)

编辑: 在考虑C的CPAN时,我想……我该怎么称呼这样的东西,然后想到了“ccan”,然后谷歌了一下,我看到了这个: http://ccan.ozlabs.org/

不过,它似乎还处于起步阶段。

Ruby是我最喜欢的语言,以下是我不喜欢的语言:

绿色线程+阻塞C库=巨大的失败 慢得令人痛苦 标准库本身与其使用bang!方法 模块包含+扩展是混乱的。 “开放类”不能是范围-我想添加一个String#dostuff,但我不希望泄漏到所有的第三方库 没有二进制部署打包解决方案。

VB6

仅Windows。 不再支持。 数组可以从任何数字开始,而不是全部归一化为0。 已编译的应用程序依赖于许多dll才能正常运行。 许多复杂的控件(如浏览器控件或复杂的代码段)在运行未编译的代码时往往会破坏IDE,但在编译后却可以正常工作。