帕斯卡对象:

There's a lot of jumping back and forth in the file you're editing since the interface and implementation are split into two parts but still jammed into the same file. Dynamic indexing of arrays, strings start at 1, you specify the starting index when declaring fixed arrays and dynamically allocated arrays always start at 0. Classes and objects (not to speak of interfaces) are bolted on top of the language and among other things can't be stack allocated like records can. When calling functions without parameters the () are optional, leading to a lot of pain when you are dealing with function pointers or trying to refer to the result of a function using the function name. Parameter lists can't handle fixed array types or function pointer types without external type definitions.

这仅仅是一种语言，一个标准库的遗憾借口，而脆弱的IDE应该有自己的列表。

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++

模板的语法 钻石传承问题 现代语言所拥有的标准库过多/缺乏(尽管boost也很接近)。 iostream IOStreams周围使用的语法

Python

空格是有意义的(有时) 强调关键词 有限的线程支持(至少目前) 用self代替this 空格是有意义的(有时)

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

Perl

我喜欢这门语言，我不想添加已经被使用过的东西，但还没有人提到过这一点，所以我就把它扔到锅上。当我使用这个特性时，我发现这是我一生中最可怕的经历(而且我用过汇编语言):

write()和format()函数。

它们的语法是最糟糕、最丑陋、最可怕的，但是它们并没有提供比printf()更好的功能更多的功能。任何人都不应该尝试使用这两个函数进行任何输出，因为它们有多糟糕。

我相信有人会不同意，但是当我研究它们，希望它们能解决我的问题时，我发现它们是一个“痛苦的世界”(引用Big Lebowski的话)，我希望Perl6已经消除了它们，或者更好的是完全重写它们，使它们在某种程度上更可用和有用。

Python

No statements in lambdas. GRRRR foo( a for b in c if d ) feels wrong, it surprises me every time I get away with it. Shouldin't it be foo( (a for b in c if d) )? Can i have a dict comprehension? map and filter operators have special syntax in list comprehensions, how about something for reduce? or sort? Just by having a yield statement in it, a function is magically transformed into a generator, and its interface changes completely. Also, that generator cannot do any work before the first next(). at least, not without using a function that returns a generator.

JavaScript

No brief syntax for making modular code libraries. You have to call a function that returns a dictionary of public methods. And you have to edit that in (at least) two places every time you alter the interface of your module. Creating closures involves returning it from a function that returns a function from ('sup dog) yo' function. Clutter! for each ( foo ) syntax and behavior feels like an afterthought. Knowing when your code will actually run (and in what order) is more of a dark-art. The only way to get it right for sure is put everything (yes, that too) in one big file. and even then you still need to wait for a document.onload Am i missing something? is there no trivial way to get json serialized values without building them by hand? (yes jQuery can do this, sort of).