So Many Frameworks, So Little Time
•
1 like•579 views
Once upon a time, choosing a framework for your Flash or Flex project was easy. You either used Cairngorm or you didn't. Then along came PureMVC, followed by Mate, Parsley, Robotlegs, Swiz, Sping Actionscript and many more. Getting to know all these frameworks takes a long time. Making a choice of which to use may take even longer. In this session Richard will use his experience developing with and recommending frameworks to help you make that choice. Richard will talk about the features that you need to consider when choosing a framework, he'll discuss the key differences between the various frameworks available, and he'll tell you how to know when you've made the right choice. And, he will try to answer the question of which framework is best.
Recommended
Recommended
More Related Content
Similar to So Many Frameworks, So Little Time
Similar to So Many Frameworks, So Little Time (20)
Recently uploaded
Recently uploaded (20)
So Many Frameworks, So Little Time
- 1. Flex and the City, October 2010 So many frameworks, so little time Richard Lord Technical Architect
- 2. There is no single best framework
- 3. Bloom Foundation Potomac Bojinx Foundry PureMVC Brute Guasax Rialy Bumpslide Hemlock Robotlegs Cairngorm HydraMVC Sekati Cocktail JumpShip Shell Ctx Kiichigo Siam Dawn Legato Slide Deepsplink Mate SmartyPants Dugong MIoC Spring Actionscript Dusk Moccasin Swiz EasyMVC ModelGlue:Flex Thin red line Flest MVCS Vegas Flight Nimbus ... Fly Parsley
- 4. So how do we choose?
- 5. Does the framework use the MVC pattern? Service Locator or Dependency Injection? Event bus or Method calls? Events or Notifications or Signals? Presentation model or Mediator or Code behind? Does the framework support Flex modules? Does the framework enforce a specific architecture?
- 6. What dependencies does the framework have? Is the framework performant enough? Is the code of a high quality? Is there plenty of good quality documentation? Does the code have good unit test coverage? Is the project actively maintained? Is support available? What will it cost? What license does it use? How many developers work on the framework? How many users use the framework? Is there a vibrant user community?
- 7. In fact there's only two important questions?
- 8. "Why do I want to use a framework?" "What are the risks in using a framework?"
- 9. "Why do I want to use a framework?"
- 10. A framework provides code that my developers don’t have to write themselves, which saves time and money.
- 11. A framework provides code of better quality than my developers would write, which improves product quality.
- 12. A framework provides a prescriptive application structure for my developers, which encourages consistency in our code.
- 13. A framework gives me a well-known architecture which new hires may already know, so they can quickly start developing useful code for me.
- 14. A framework provides documentation and support to the developers when they need it.
- 15. "What are the risks in using a framework?"
- 16. It's not my code...
- 17. Is the framework still developed and supported? (If not, you will have to fix bugs and upgrade features yourself)
- 18. Is that development dependent on the work of one individual? What happens if he/she decides to do something else instead? (You may find yourself using a dead framework)
- 19. Is the framework ready for production use? (If the developers don't think it's ready, it isn't ready)
- 20. Is the framework in use in a number of other projects that have been released? (Being an early adopter is risky)
- 21. If you write unit tests, does the framework have the level and quality of unit test coverage that you require of other code? (Do you regard lack of test coverage as a risk?)
- 22. Is the framework dependent on other projects? If so, do those other projects introduce risks?
- 23. A few other points to remember
- 24. You're not looking for the best framework, you're looking for a framework that does what you need.
- 25. Don't hire the developer of a framework to advise you on what framework to use. You already know their answer.
- 26. Consider what’s best for your team and your project when choosing a framework.
- 27. Don't forget, the framework your team already know may be the right choice.
- 28. How do you know you're using the right framework?
- 29. You know you're using the right framework when you stop worrying if you're using the right framework.
- 30. But which framework is best?
- 31. No single framework is best. But, when looking at client's requirements and balancing them against the features of different frameworks, one framework comes out top more frequently than any other. That framework is Robotlegs.
- 32. That's all folks http://www.richardlord.net/presentations/ twitter.com/Richard_Lord