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

Common Lisp:

关键词往往太啰嗦。 库支持是可怜的。 在希望更严格地处理内存的操作系统中不能很好地工作。 没有与操作系统交互的良好工具。 “循环”功能没有很好地定义，当然看起来也不像Lispy。

方案:

缺乏用户/社区小

C++

太容易随机破坏内存并创建几乎不可能找到的错误(尽管Valgrind在修复这个问题上走了很长的路)。 模板错误消息。 在使用模板时，很容易将所有内容都包含在一个文件中，然后进行愚蠢的编译。 标准库在现代是一个笑话(默认情况下仍然没有线程或网络?) 大量令人讨厌的C语言(特别是所有在short/int/unsigned/等之间的转换)。

Python。

虽然前面提到了python处理作用域的奇怪方式，但我觉得最糟糕的结果是:

import random

def myFunction():

    if random.choice(True, False):
        myString = "blah blah blah"

    print myString

也就是说，if块内部的作用域与函数的其余部分相同，这意味着变量声明可以出现在条件分支内部，并且可以在条件分支外部访问。大多数语言要么阻止你这样做，要么至少为你提供某种严格的模式。

此函数有时会成功，但有时会抛出异常。虽然这是一个人为的例子，但这可能会导致一些微妙的问题。

再给c++投一票…仍然是我最喜欢的语言，有几个亲密的追随者——C和Python。以下是我目前最讨厌的名单，排名不分先后:

Plethora of integer types inherited from C - way too many problems caused by signed vs. unsigned mistakes Copy constructors and assignment operators - why can't the compiler create one from the other automatically? Variable argument madness - va_list just doesn't work with objects and I'm so sick of problems created with sprintf(), snprintf(), vsnprintf(), and all of their relatives. Template implementation is required to be fully visible at compile time - I'm thinking of the lack of "export" implementations or at least usable ones Lack of support for properties - I want to have a read-only member like "a.x" that can be read publicly and only assigned internally. I really hate the "val=obj.getX()" and "obj.setX(val)". I really want properties with access control and a consistent syntax.