It depends on the goals of the Flex project. If we are looking to create something that is purpose built for the Flash runtime, then I don't believe so.
However, if we are looking at Flex as a toolkit to build rich interfaces and are willing to break from the SWF compile target being our core focus, then I believe yes. I think that question really needs to be answered first. While I love Flex as-is, we are seeing Adobe's priorities change for the runtime and even some version fragmentation that we hadn't before (pepper flash player in chrome and the MS flash player built into metro IE). It pains me to say this but it looks like the standard HTML js CSS world is receiving all of the developer efforts right now and I think that we should make that a focus if we want this project to survive and thrive beyond the next year or two. There is a conflict of interest here which I'm sure we are all aware of. The goals of building the best toolkit for rich applications for mass consumption and the goals of enhancing the current toolkit to continue servicing our enterprise clients seem to be in conflict. This is my two cents of an opinion and I will be glad if I am mistaken. On Friday, November 16, 2012, sébastien Paturel wrote: > After several discussions about the difficulty to break UIComponent for > example, and the whole re-architecturing of flex SDK issue. > I'd like to launch this poll to see if there's a consensus about it. > > So in your opinion flex SDk: > > 1- Need a complete re write > 2- Can be re architectured from the current code base > > Thanks > >
