A headless player is holding back CI in a big way.
I also can't see FalconJS delivering a full flex stack without help from the browsers. A lot could be rendered in a canvas, but then you get into situations where you need stage text etc...
I just wish Adobe had a simular JS environment to announce at the same time, or slightly before. At least then there would be a migration path. Currently Flex devs are trying to find a simular enterprise RIA platform, and none of them are owned by Adobe.
Even if you ignore all the other technologies that were labeled RIA, you simply can't ignore OpenLaszlo which happened before Flex and from which Adobe probably took inspiration:
OpenLaszlo was originally designed to be cross platform, first targeting Flash, then eventually other platforms like DHTML, which it now does. But FLEX is impossible to use with anything but Flash, by design.
And now, predictably, people are complaining about being locked into Flash because they used FLEX, while Adobe is abandoning FLEX and Flash.
"Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility." certainly doesn't read to me that they have abandoned the project.
"Falcon, the next-generation MXML and ActionScript compiler that is currently under development (this will be contributed when complete in 2012)
Falcon JS, an experimental cross-compiler from MXML and ActionScript to HTML and JavaScript."
That is actually one of the most exciting things I have read in a long time regarding software development. I wasn't aware work on this was under-way, though I had suspected it might be.
I will look back and laugh if in a couple of years all the people hating on Flex now are using these tools to build their HTML 5 applications.
I can actually see these developments improving Flex for the community in the years to come.