C#

Cannot create a reference (var &t = struct) No local scope destructors (IDispose comes close but its not the same) ToString, i almost dislike that every object has it but it turns out i dislike everything using it like string.format does. I rather have things that accepts a certain type (like ints, floats, text, chars only). So instead of passing in any object i need to pass in something with a implicit typecast or interface. I ended up writing something like this to safely escape text for html which worked great. Cannot use a virtual typecast (blah)obj; does not work if obj does not inherit/has an interface of blah. Simple workaround is to supply an interface with a convert function. Has no local creation. Instead of writing var o = new Item(); i would like to write (something like) Item o() (with an automatic dispose if it has one).

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的东西。

我讨厌c++的五个方面

联系时间。使用分布式构建，我可以在同一时间重新构建我们的整个项目，它需要我们的链接器运行。 没有防止内存操作重新排序的标准方法。使用写组合内存通常需要滥用volatile关键字。防止读重排序(在处理SIMD数学管道时通常是优化的关键)通常是通过在例程中间注入空ASM块来实现的。 多步宏来解决字符串化问题:

#define STR_LINE2(x) #x
#define STR_LINE(x)   STR_LINE2(x)
#define LINE_NUMBER STR_LINE(__LINE__)

做字符串操作通常是很痛苦的。 大量的非标准化printf变体(vsnprintf_s vs _vsnprintf_s)。

Python:

处理数字太慢了。这不是什么大问题，除非…… 不能简单地在程序中包含导入时自动编译的C代码。 在py3k接管之前，我们仍然要忍受愚蠢的整数除法规则。 在py3k接管之前，像imap和izip这样的好东西仍然存在于一个单独的模块中。 在py3k接管之前，我们还有很多工作要做。

C++

The inconsistencies in the libraries related to char* and std::string. All C++ libs should take std::strings. Characters are not bytes with respect to iostream. I do a lot of byte-oriented work. Having a "byte" type and a "character" type would significantly make it simpler. That, too, would permit scaling to Unicode somewhat easier. Bit operations should be easy on a value. I should be able to access and set the n'th bit of a value without playing AND/OR dancing. The lack of a standardized interface for GUIs. This is where Microsoft has really been able to position themselves well with C#. A standard interface binding that OS makers provide would go really far for my work.

Self

没有真正的代码浏览器 数百个小窗户飞舞 周围。 只是一个研究项目， 不够稳定，没有活动 社区。 没有相当快的版本 适用于Linux或Windows。只有Mac OS X。 不支持标准键盘 命令。 哦!关于编写本地插件的文档也太过时了!