>>Hmm. IMHO, Spark was evolutionary which I think became its biggest >>ball-and-chain. And when I was working on my "carve up UIComponent" >>prototype, it was impossible to stay in sync with the rest of the team making >>changes in lines of code that were moving to other files.
IMO, spark was a problem because it was forced to be evolutionary. I was involved in the beginning of those decisions. I would have preferred spark be a complete rewrite based on a new ideas as well. Unfortunately with the staffing that was being allocated, the timeline to do so was prohibitive. I fear the same thing here. Changes that make it better in a month are interesting. Changes that solve real pain points that enterprises have today with using Flex might keep them on this framework and stop them from switching away... which is what every major enterprise is weighing today for new development. A theoretical rewrite that might make things better in the future requires 2 things: hope and faith. Adobe effectively abolished both of those qualities over the last few months. I know we don't see things the same way, but a really great framework that runs on Flash Player 1 or 2 years from today is totally useless to me. None of my clients will care or notice because they won't be using this technology. My hope is that we can make changes that make the 2 year time frame matter. Mike
