JavaScript:

All the coolest things are insanely complex, but then, all the coolness is also wrapped up in such a small amount of code that you feel stupid for struggling to follow it '+' is an absurd choice of operator for concatenation in a weakly-typed language. Were they trying to scare off the noobs? It's a cross-browser compatibility minefield (never mind if it's even turned on or not) It's generally untrusted - associated with scummery such as blocking the back button, pop-ups that never die, etc. It's nearly impossible to debug because there are only a few different error messages and a few different types (Number, String, Object, etc.)

如果不是jQuery，我可能还是会像以前一样讨厌它:)

Quenya

• Community is too small. It's next to impossible to get a good language-immersion program going when there's no easy to find another speaker nearby. • Irregular verbs. Yes, I know English and Spanish mentioned them, too, but Quenya was invented. Why does there still need to be irregular verbs? • No Unicode support. I have to have three different Tengwar fonts on my computer before I can read most messages, and several of them are poorly kerned. This wouldn't really be a huge issue given the existence of a Romanized transcription, but Tengwar is so beautiful, you don't not want to use it. • Not all concepts can be easily referenced in Quenya, leading to annoying circumlocutions, or resorting to Sindarin, Númenórean, or (Manwë save me) Klingon to get my point across.

Java

已检查的异常 类型擦除 缺少操作符重载(例如BigInteger/BigDecimal) 缺少regexp/date/duration /复杂文字 对不可变性的支持很差

下面是关于Perl 5的更多内容，来自创建了大量Perl模块，特别是在Moose上工作过的人的观点。

The horrible brokenness that is overloading and tied variables. Both of these features are a failed attempt to allow transparent extension to the built-in types. They both fail in various ways, and require module authors like myself to either implement horrible hacks to support them, or to say "never pass an overloaded object to the foo() method". Neither alternative is really acceptable. Lack of proper hooks into the compilation process and the meta-model. Moose in general, and role usage in particular, could be made much safer if the Perl core allowed us to affect the compilation process via a sane API that allowed us to hook into the meta-model (packages, classes, etc.) Lack of named parameters built into the language. Instead, everyone reinvents this. It's annoying. Similarly, lack of optional types. I don't want a static language, but the ability to specify types and constraints, particularly on function/method parameters, would be great. Perl 6 gets this right. Types are optional, but very rich, and there's no fundamental difference between built-in and user-defined types. The backwards compatibility police. This is more of a cultural issue. A number of the above issues can never really be fixed, since Perl 5 has a very strong commitment to backwards compatibility. So even if something were to be added that effectively replaced the current ball of shit that is tie and overloading, those features will never be removed. Of course, backwards compatibility is also one of Perl 5's greatest strengths. Bonus hate: Perl's built-in exception mechanism is a joke. The fact that exceptions may be a string or object makes for an eternity of fiddly exception-catching code, and the lack of a catch in the language syntax is the wart on the wart.

Clojure

Lack of built-in syntax for optional and keyword parameters in function definitions. Sure, you can add it easily enough, but that means library writers don't use it. Pervasive destructuring hasn't proven to be a good substitute yet Lack of method combination (before/after/around methods of the sort found in Common Lisp) Too much reliance on Java interop, e.g. there's no built-in file IO Sometimes I want static typing. This one isn't pure hate; I usually prefer dynamic, and attempts to mix the two have been largely unsatisfactory There's no built-in fast binary serialization format for the built-in data structures, though I hear people are working on it

C#

Lack of multiple dispatch based on the runtime type of the method arguments. dynamic should solve most of this, but it hasn't been released yet. Interface implementation is declarative not structural. I really like the way Google's Go language is doing types Making asynchronous method calls is really bulky (and I'm pretty sure all threads are OS threads, not lightweight threads) No macro system. I'm not talking about C-style macros here; I'm talking LISP/Scheme style macros Operators are static methods and their signatures are overly constrained (and you can't create new ones).