我讨厌所有语言的五件事(至少就我所知):

Does what I say/type, not what I mean Will undoubtedly meet people who think they are experts in the language, but just make a mess of it (e.g. people who insist that removing comments/unused local variables will speed up execution time for a program) Unless the language is obsolete, then it will probably continue to evolve (either the actual language, or the concepts behind using it effectively) requiring you to actively develop with it so as to not fall behind. Can't modify the lexer/compiler (add in own context sensitive grammar) No perfect language (every language is missing some sort of useful feature that usually is either impossible to simulate, will unavoidable have an ugly interface or just require far too much time to implement and get it right)

Haskell:

空间泄漏——懒惰的默认代价——也许代价太高了? 甚至像head和tail这样的纯函数也会调用错误并引导您进入IO。 fail from Monad -带回MonadZero。 Num类-(+)应该在AdditiveGroup或类似的类型中。 那个单子不是一个应用程序。

C是我最喜欢的，但也很糟糕。

It has the worst pre-processor ever. Why didn't they use something like m4? The whole header vs source file model is broken. Pascal got it right with units. It needs case ranges in the switch statement. Unions and casts from void* break the type system. This makes garbage collectors impossible. No nested functions. GNU C has this, but it should be standard. No boundary checking for allocated memory. There are tools that discover this but they don't detect errors where a piece of code miscalculates an address and writes to an allocated region which isn't related at all. I hate the whole pointer arithmetic. No bounds checking for arrays. Too many issues regarding portability. Even wchar_t differs across platforms.

MEL(玛雅表达语言):

Single dimensions arrays: Forcing me to manually sync two or more lists, or use delimited strings to simulate more complex data structures. Naturally, they're immutable too. Single threaded and slow: Causing the entire Maya application to hang while it completes a task. Bonus points for not being able to kill long operations, instead having to close and re-open Maya. Script sourcing paths aren't recursive: Meaning every directory you want to store scripts in must all be added to the script path. No namespaces: Forcing the inconsistent use of naming conventions to make sure global procedures don't collide. Modal commands: Each command is modal, meaning the Create, Modify, and Query operations are all handled by setting flags. This also forced the developers to cause most of the commands to return arrays Inconsistent command style: Most array commands actually return arrays, but the Tokenize command has to take an array as a reference which it then populates, rather than spitting out an array. This among other inconsistencies.

这些以及其他几个原因是AutoDesk采用Python作为次要脚本语言的原因，这带来了其他一些令人讨厌的因素:

并不是所有的MEL命令都受支持:大多数都受支持，但有时您会发现自己不得不使用MEL()函数来执行一些任意代码。更糟糕的是，你不得不对它进行所有烦人的逃避。 继承了模态命令风格:必须使用相同的create=True, query=True, edit=True的东西。

JavaScript

Every script is executed in a single global 'namespace'...something which you have to look out for when working with scripts from different sources If a variable is used but hasnt been defined before hand, it is considered a global variable Browser vendors making up standards as they please, making coding for us developers using such a beautiful language harder than it should be Case-Sensitivity - considering that there is no decent IDE for developing js with compile-time checking Workarounds (such as the use of hasOwnProperty method) to perform some, otherwise simple operations.

Java:

没有过程编码，它编译成过程代码，所以让我使用它! 没有多重继承，试图用15,000个接口做同样的事情很糟糕。 约会课，我还需要多说吗。 我不能充分利用多态性。Java不会覆盖不同的参数类型来触发。 我想不出第五个原因，如果我知道，我会回来编辑这篇文章。