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

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


当前回答

C#

Cannot create a reference (var &t = struct) No local scope destructors (IDispose comes close but its not the same) ToString, i almost dislike that every object has it but it turns out i dislike everything using it like string.format does. I rather have things that accepts a certain type (like ints, floats, text, chars only). So instead of passing in any object i need to pass in something with a implicit typecast or interface. I ended up writing something like this to safely escape text for html which worked great. Cannot use a virtual typecast (blah)obj; does not work if obj does not inherit/has an interface of blah. Simple workaround is to supply an interface with a convert function. Has no local creation. Instead of writing var o = new Item(); i would like to write (something like) Item o() (with an automatic dispose if it has one).

其他回答

VBA(因为你认为你的语言不好)

Whitespace inside a line is rigidly enforced. Statements just end, and require a " _" to break to the next line, but not every line can be broken. No ++,--,+=,-= statements. Seriously? Arrays can begin at any index, not just 0. Some types (i.e.: fixed-point "Decimal" value) must be subtypes of Variant, and aren't available as their own type. != and <>. "=" is used as both comparator and assigning, instead of splitting into "=" and "==". "Option Explicit". UI hasn't been updated since 2000. Office2k7 didn't upgrade to VB.NET Most object models are non-sensical and overly verbose.

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

TCL

这是我最喜欢的语言,几乎可以做任何事情。多年来,它已经(慢慢地,非常缓慢地)演变为解决大多数让我烦恼的事情。而且这门语言非常灵活,很容易实现语法来覆盖那些仍然困扰我的东西。但是语言中有一些东西是不能轻易改变的,只是打破了它的禅意:

Arrays (of the associative kind, what Perl calls hash) don't have proper value semantics. This makes them awkward to pass to and return from functions. Also, this means that they can't be nested. For this reason dicts (dictionaries) were invented but too late, the nice array access syntax: $array($foo) is now forever taken by stupid arrays for backwards compatibility. We're now stuck with: dict get $dict $foo which is much more verbose and to me feels less readable. No real closures. Though it can be emulated somewhat by globals or namespaces but that defeats the reason for closures in the first place. Although, I can't really see for now how closures can be implemented in a pure value semantics system. Teacup is hard to use and is not at all intuitive compared to all other repository tool out there. This is more ActiveState's fault than tcl-core and doesn't really break tcl's Zen when coding but it is still very annoying.

C#

1)缺乏为值类型编写泛型的实际能力。例如,任何白痴(好吧,大多数白痴)都可以编写一个例程,用c++计算int, float, double等列表的标准偏差,它写起来很简单,易于阅读,并作为快速的非泛型代码执行。我认为,如果你能用c#写一些东西,接近于达到这三个中的任何一个,而在其他两个上又不荒谬,你就是一个真正伟大的程序员。

2)协方差和反方差,尽管这被添加到4。

3)非常糟糕的LINQ文档(好吧,并不是语言的一部分)。

4)尝试使用foreach/迭代器,当我每次都想做同样的事情,除了上次略有不同(如连接一串字符串与逗号之间的单词和最后两个)。如果我用一个IEnumerable来写它,它很难写和读,而用一个for (int I =0 I <…)它并没有好到哪里去,而且效率更低。

5)我知道我会收到抱怨,但是缺少受控的例外。这并不需要像在java中那样实现(框架开发人员确实提出了一些很好的观点,为什么他们没有这样做),但我很乐意看到编译器警告不喜欢受控异常的用户可以关闭。

JavaFX

Type inference sometimes doesn't behave like you would expect, so you often need to explicitly declare the type. def behaves likes const in C and not final in Java you can insert a value in a sequence by accessing an index >= seq.length, which should actually throw a compiler error (according to the reference). if you assign null to a String, it defaults to "". If you assign null to an Integer, a compiler error is thrown (in contrast to what the reference says). handles CheckedExceptions the same way as RuntimeExceptions