Common Lisp

缺少提供更现代功能的标准库(套接字，线程，…) 是否可以使用映射到本机窗口系统的标准化UI Scheme将lambda表达式赋值给变量并将变量直接作为函数调用使用的能力看起来比APPLY for FUNCALL更整洁。我猜这是使用多个名称空间的副作用 标准化的库源代码级打包系统，以便可以从多个实现中轻松使用它们

我想知道强类型的口齿不清会是什么样子

c#中缺少预处理器。

我知道他们把它放在一边是因为有些人会滥用它，但我认为他们把孩子和洗澡水一起倒掉了。代码生成被认为是一件好事，在c++中，预处理程序是我的第一个代码生成器。

C / C + +

缺乏完整的SWAP功能 模板的语法 你不能#define一个#define(没有多通道) 编译器之间的结构打包不兼容 Char是有符号的还是无符号的?

Java

边缘上的不变性 没有像c#一样的ref关键字 到处尝试/捕捉积木 运行时性能差 所有与字符串相关的东西

Python

没有“main”(我已经习惯了!) 强调关键词 有限的线程支持 用self代替this 缺少类似C/ c++的语法

Objective Caml

Non-concurrent garbage collector. I can write multi-threaded programs all day long, but they're only ever going to get one of my eight cores at a time. This makes me sad. No type classes (or their moral equivalent). There's Furuse-san's GCaml, but it's A) not quite as good as type classes, and B) not in the INRIA distribution. Badly in need of a Cocoa bridge. Seriously. If I wrote more code with actual interfaces to DNA-based life forms, then I'd probably break down and write the damned thing myself. Why hasn't anybody else done this yet? Functors are abominable. Seriously, modules ought to be first-class values. There should be only one kind of function. Read Montagu and Rémy before you flame me for this. Should use LLVM for its back-end. Who do I have to murder to get OCaml to compile for my stupid little ARM6 core?

是的，我有一些问题。我仍然非常喜欢这门语言。这太棒了。

C#

I wish I could switch() on any type, and that case could be any expression. Can't use object initializer syntax with 'readonly' fields / private set autoprops. Generally, I want language help with making immutable types. Use of {} for namespace and class and method and property/indexer blocks and multi-statement blocks and array initializers. Makes it hard to figure out where you are when they're far apart or mismatched. I hate writing (from x in y ... select).Z(). I don't want to have to fall back to method call syntax because the query syntax is missing something. I want a do clause on query syntax, which is like foreach. But it's not really a query then.

我真的到达这里了。我认为c#非常棒，而且很难发现它有什么缺陷。

C++

Strings. They are not interoperable with platform strings, so you end up using std::vector half of the time. The copy policy (copy on write or deep copy) is not defined, so performance guarantees can not be given for straightforward syntax. Sometimes they rely on STL algorithms that are not very intuitive to use. Too many libraries roll their own which are unfortunately much more comfortable to use. Unless you have to combine them. Variety of string representations Now, this is a little bit of a platform problem - but I still hope it would have been better when a less obstinate standard string class would have been available earlier. The following string representations I use frequently: generic LPCTSTR, LPC(W)STR allocated by CoTaskMemAlloc, BSTR, _bstr _t (w)string, CString, std::vector a roll-my-own class (sigh) that adds range checking and basic operations to a (w)char * buffer of known length Build model. I am sick to death of all the time spent muddling around with who-includes-what, forward declarations, optimizing precompiled headers and includes to keep at least incremental build times bearable, etc. It was great in the eighties, but now? There are so many hurdles to packing up a piece of code so it can be reused that even moms dog gets bored listening to me. Hard to parse This makes external tools especially hard to write, and get right. And today, we C++ guys are lacking mostly in the tool chain. I love my C# reflection and delegates but I can live without them. Without great refactoring, I can't. Threading is too hard Language doesn't even recognize it (by now), and the freedoms of the compiler - while great - are to painful. Static and on-demand initialization Technically, I cheat here: this is another puzzle piece in the "wrap up code for reuse": It's a nightmare to get something initialized only when it is needed. The best solution to all other redist problems is throwing everything into headers, this problem says "neeener - you cannot".

诚然，其中许多内容超出了严格的语言范围，但在我看来，整个工具链都需要进行判断和发展。