我讨厌内梅尔的五个方面:

局部函数不能让步 编译lambda的能力有时取决于它是否内联 元组的值/引用类型语义不一致 数组下标和类型参数之间偶尔会出现歧义 缺乏普遍采用

Python:

Global Interpreter Lock - Dealing with this complicates parallel processing. Lambdas functions are a bit clunky. No built-in ordered-dictionary type. Depending on how Python is compiled, it can use either UCS-2 vs UCS-4 for the internal Unicode encoding, many string operators and iterators may have unexpected results for multi-byte characters that exceed the default width. String slicing and iteration depend on the bit width rather than checking and counting characters. (Most other programming languages do similar things as well and have similarly odd behavior with these characters.) There are inconsistencies surrounding GUI frameworks for Python.

Emacs Lisp

目前还没有足够的商业市场让人们全职用elisp编码 GNU Emacs vs XEmacs不兼容 Scheme中的嵌套函数很整洁，我希望elisp有[1]的概念 用于简单遍历列表的do循环或其他一些工具不是标准的(当然，您现在可以使用lambda进行映射)[1] (function (lambda(…)))[1]应该有一个简写

当然，Lisp的一个美妙之处在于，用一行代码在你自己的代码中修复这些问题并不难。但这并不是与生俱来的，这让我很恼火。

好的问题;我有点不好意思，因为我想不出更好的东西来恨，但说实话，法官大人，没什么好恨的。

C#

No easy way to check if a type is Numeric It means you are probably stuck using most of the microsoft stack, IIS and MSSQL Instead of being a specific tool for a specific problem, C# tries to be a language for every paradigm. Lack of community. Sure, there are starting to be open-source frameworks and libraries for C#. The same ones that have been available to Java developers for years. Hard to find good help. The internet is littered with poor examples of how to solve problems with C#. This goes back to problem #3.

C#

我对c#非常满意，但这两个真的让我很恼火:

Constructor-based initialization for immutable classes is less convenient, less intuitive (when you read the code you don't understand what you assign to what), has less IDE backing than inline object initialization. This makes you lean towards mutable classes inevitably. I know this has been mentioned before, but I strictly have problems with initialization syntax for immutable classes. switch is too verbose. Whenever I see a situation where a switch would be proper, I'm really inclined to use an if..else if.. just because it's more terse (~30% less typing). I think there should be no fallthrough for switch, break should be implied, and case should allow comma separated list of values.

Python:

1) line continuation syntax: "...\" works, but "...\ " does not, and that trailing space is generally invisible, without unusual eol-marking by editer. 2) a bare 'raise' is invisible in the stack trace, as the stack trace looks like the previous raised exception. 3) slow 4) poor integration into web-servers (mod_python: dead, mod_wsgi: limited scope of operation). This is complicated by 3], requiring daemonization or some sort of memory-persistance to perform well. 5) overly tolerant of mixed tabs and spaces, allowing changes to control flow to sometimes remain hidden. (maybe fixed in recent versions)