After analyzing 2 most popular framework both from syntax and performance point of view – I realized that both frameworks is not good enough for me. I work mainly with games and heavy applications that requires both code writing speed and code execution speed. With that knowledge I did what any programmer usually does in such situation – started my own project! where everything will be perfect! it will be fast! it will be comfortable to work with! and sun will shine all day long!
So I started with writing requirements…
Read more…
We all know that using framework in you application will hurt performance, and Flash has long and sad history of performance problems. I decided to find out how much exactly performance using framework costs us. As in last post I focus on 2 most popular frameworks: RobotLegs and PureMVC.
Run PureMVC tests [Source code: PureMVCSpeedTest.zip]
I tried to measure 4 things: running commands, getting stuff, creating mediators, communication.
I measured how much time one such action will take, and calculated how much actions you can use in your code to waste 1ms of execution time.
Then you start creating bigger applications, or start working in bigger teams – using good framework becomes essential.
I spent good amount of time with 2 currently most popular AS3 frameworks – PureMVC and RobotLegs, and here I will compare pros and cons of both.
Generally both frameworks are very similar! :
RobotLegs and PureMVC Pros:
- will help divide your code is small units and wire them;
- will help standardize your code;
- based on MVC;
- can be extended to your needs;
- makes you focus on your fun app instead of focusing on solving architecture puzzles;
- have big and active communities;
RobotLegs and PureMVC Cons:
- hurts performance a bit;
- harder to debug “black box” framework code;
- couples implementation with framework;
…but RobotLegs: Read more…