Now I got what you mean . Thanks a lot! But with DI you are much free and flexible. And the argument what you mentioned regarding to not encouraging patterns is the price we pay for "buying" that freedom. Are you agree?

Thanks for you response. But I wish I could understand your statements about simplicity. (It is not simple to understand the statement of simplicity Could you please outline how PureMVC is simple that helps and how RL is not simple that creates a mess, please.

I have just investigated both frameworks to understand the basic concepts, architecture and other details of PureMVC and Robotlegs 2 and now I don't know which one to choose. The problem is that I think both of the frameworks have almost the same architecture (Views, Mediators, events that create Commands which in its turn call some Proxy functions - in case of RL2 Models and Services). In addition to this I see that Robotlegs has introduced an elegant mechanism of automatic dependency injection (which as I know what taken from Java), and this really took that framework a hug step forward. In the case of PureMVC you should use the Facade. Now can I consider that Robotlegs has accomplished the same that PureMVS has done, but in a better way? If no, then what are the key advantages of PureMVC over Robotlegs?