Groovy和Grails

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

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

Lua:

元表是如此令人困惑，直到他们“点击” 缺少像a += 20这样的赋值操作符是一种痛苦 没有集成的面向对象的解决方案意味着每个人和他的狗都使用自己的口味 用于注释(——)的语法排除了加/减前后操作符的可能性 不入侵C端就不可能有任何先发制人的多任务系统

C#.

我最讨厌的是:

No multiple inheritance - imagine you could provide whatever GUI framework base class (Control, Window, whatever) with MVC - related stuff, etc... framework / base class agnostic! No "friend" keyword... I know, the RAD - victims would abuse it for all kinds of stinky code and for hilarious malpractices, but it would be nice for the OOD - guys to enforce the law of demeter No language integrated DBC features, there are the Contracts, but I would rather have that Spec# - style with a general purpose "!" - postfix operator No AOP (I don't get it... this language has attributes, it would have been SO EASY to add interception code in the compiler!) No weak event delegates - the observer pattern becomes nothing but a memory leak bait as it is now... :-(

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.

Ruby。

Strange scoping rules - variables, constants, and methods each behave differently from each other. The rules change also depending on which keyword you used to create a closure. Or on whether you're in a class, eigenclass, object, module, or module's self. Then there's instance_eval, which changes the rules to a different set of rules. And they change again when a module is "included" or "extended", which themselves do different things to scope. And some sets of rules can't be emulated by metaprogramming, so you have to use eval. Unless you're on ruby 1.9, where all of this is different. Namespacing is basically useless. If you have Foo::File, then the stdlib File is probably broken for all of Foo. require statement is broken. If two files require eachother, the behavior of those files can change dramatically depending on which is loaded first from elsewhere. libraries change APIs dramatically and suddenly, so you have to require specific minor revision numbers of all of your dependencies. For every single ruby application on your system. The rubygems package system overrides "require" rather than putting files in the search path - because why use a system when you can replace it?