Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Moxie Zhang on Sep 17, 2008
Mate is a tag-based Flex framework created by AsFusion in June 2008. In the period since InfoQ reported reactions among the Flex community on its release, Mate has been gaining attention among Flex developers. Now, many are asking how Mate fits into Flex rich Internet application (RIA) development compared with established frameworks, like Cairngorm and PureMVC.
Java developer Per Olesen at TechPer has posted his findings about the good, the bad and the ugly of Mate on his blog.
According to Olesen, the best thing is:
Mate is a Flex framework, meaning it does not try to hide or abstract access to Flex apis. It uses normal flex events as communication mechanisms, and depends heavily on the Flex apis in general. This is something it shares with Cairngorm, but stands in clear contrast to PureMVC.
Mate utilizes dependency injection (DI), which is a programming pattern I have come to like and use day in and day out when doing Java development.
Using Mate, the mxml view definitions become really simple and uncluttered with anything but the view code. This is something Mate shares with PureMVC, but not with Cairngorm.
In general, Olesen likes Mate and acknowledges its Flex heritage. However, there are some things about Mate Olesen does not like. He comments, “There seems to be too much magic happening behind the scenes. Mate has something called an EventMap, a place where one wires up the application. The EventMap is all done in XML. Programming in XML quickly leaves you up creek without a paddle. I hate that!”
As to the ugly, Olesen notes there is a segment inside Mate code that is in desperate need of improvement.
John Blanco of Rapture in Venice disagrees with Olesen on whether there is “too much magic” with Mate. He explains:
Mate is a framework; thus, the implication that it should somehow be understandable within five minutes doesn’t seem fair.
Also, you don’t have to use the HTTPServiceInvoker if you don’t like coding in the XML. It’s your choice based on your project. You could use nothing but MethodInvoker and be able to easily imitate Cairngorm’s Command and PureMVC’s Command and Mediator.
However, Olesen responds:
The EventMap is a very important part and concept of Mate. A large part of the framework is centered on the EventMap. It is thought of as the place for this. This is the intention of the framework. If a person is going to use Mate, he or she should also buy into the concept of the EventMap. It is an important area of Mate, and it should help you. And it might. I just doubt it.
The 5 Mandates of Software Development Teams - Presto Manifesto
Regaining control of the data centre
Innovation in Your Data Centre
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
No comments
Watch Thread Reply