4 Things Bad About PureMVC
Posted by
Charles |
October 6, 2008 .
Tech Per has another post to take a in-depth look at one of the ActionScript based framework, PureMVC. This time the post listed 4 things he hates about PureMVC. “hate” might be a strong word for a framework but I got his points. Framework is a tough business to get in only because it just can’t please everyone, especially for PureMVC that has bigger and greater goal to apply its design across different languages. Besides, I always think all complex client side frameworks are overrated anyway. Anyway, here are the 4 things Tech Per hates about PureMVC:
- Use of Service Locator instead of Dependency Injection: I agree with this one. Service locator is bit outdated or it fits better at server side. DI is modern and a simply way of hiding complicity. Simplicity is beauty.
- Casting, casting, casting: Tech Per doesn’t like the excessive use of castings in PureMVC. It’s irritating but it’s a necessary evil for abstraction, and sometimes for DI. So, guess he and we have to deal with it.
- Forced Inheritance everywhere: I’m whole heart agree with that. I hate “have to”. To use PureMVC, you have to extend its classes all the time. Very intrusive.
- Avoids Platform Dependencies: It’s the shortcoming of PureMVC from its design goal, which is to use the closely similar framework for languages such as ActionScript, C#, Java, PHP, etc. Every time you want to be as much generalization as possible among different beasts, you are closer to be a mediocre.
At the end, Tech Per said again he somewhat like what PureMVC intents to offer. A nice dude, indeed.
Leave a Comment
If you would like to make a comment, please fill out the form below.
Recent Comments