问题描述
我想了解什么样的弊端已经Robotlegs的2 PureMVC的比较。看来，这是更优雅，更方便尽可能多的强大PureMVC的。什么是PureMVC的应该活，除了传统的codeBase的原因？难道是一次在不久的将来，这PureMVC的会尽可能的Robotlegs是活的死。我认为这个问题可以由一个人谁在实践中知道这两个框架很好地回答。
I want to understand what kind of drawbacks has Robotlegs 2 compared with PureMVC. Seems it is more elegant, more convenient and as much powerful as PureMVC. What is the reason PureMVC should live except the legacy codebase? Would it be time in nearest future that PureMVC will die as far as Robotlegs is living. I think this question may be answered by a person who knows both frameworks very well in practice.
推荐答案
PureMVC的一般比在性能方面的Robotlegs快得多。这是因为，依赖注入Robotlegs的依赖是相当缓慢的。
PureMVC is generally much faster than RobotLegs in terms of performance. This is because the dependency injection RobotLegs relies on is quite slow.
然而，大多数人会同意，清洁，Robotlegs的更直观的API超过弥补了这一点。
However, most will agree that the cleaner, more intuitive API of RobotLegs more than makes up for this.
这篇关于Robotlegs的2的缺点与PureMVC的比较的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！