I just finished a write up for InfoQ on the Flight Framework. Flight compares themselves to Cairngorm, without all the “boiler-plate” code. The association with Cairngorm is a turn off for me to seriously consider using Flight, as I still don’t understand what value Cairngorm provides (old post 1 & 2). That doesn’t mean I don’t believe that Flight may have value, but in learning about the framework there seem to be the typical assumption that everyone is out there looking for the perfect MVC solution (old post 3).
I lived through the countless MVC frameworks in Java. So, I don’t believe it is naive when I ask, what is so great about MVC anyway? We all love to work in code where the separation of concerns (SoC) have been adhered to, but do I need MVC to accomplish this in Flex? I don’t believe I do…
Anyway, back to Flight, they did allude to some additional features in the framework, like history management. Although that specific feature is available in Flex 3, there maybe other features that make it useful. The documentation is pretty slim right now – we will see what else is there when the docs evolve. For me, I guess I want to see frameworks that do more than attempt to enforce a pattern.
