Self

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

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

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)

Groovy和Grails

动态类型 约定优于配置，假设您了解约定 你讨厌春天的一切 你讨厌Hibernate的一切 [Groovy]跨集合的常见操作不是(但最近的版本对此进行了改进)

c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的，明天问我，我会想出一个不同的5个:)

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".

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

Ruby是我最喜欢的语言，以下是我不喜欢的语言:

绿色线程+阻塞C库=巨大的失败 慢得令人痛苦 标准库本身与其使用bang!方法 模块包含+扩展是混乱的。 “开放类”不能是范围-我想添加一个String#dostuff，但我不希望泄漏到所有的第三方库 没有二进制部署打包解决方案。