We at last received our Flash CS4 licences at Motion-Twin !
It always takes a lot of time to be able to get the international version in France... and the prices in euros are much more expensive than in dollars. We calculated that next time we would have better hiring some guy to go the US by plane and buy CS4 licenses for us in dollars...
Anyway, since I already played with all the Flash 10 features, I was not so much in a hurry to try it, since I barely use the IDE. But our designers do... and they didn't like it.
Even on a brand new computer with a lot of RAM, opening one of our current projects FLA takes much more time than on CS3, and much more memory (it peeks at 1.2 GB of used memory !). And after that, a lot of simple operations such as adding keyframes complains... about the lack of memory... (even if the computer still has more than 2GB free memory)
Memory issues are is not CS4 specific, but are even worse now. I'm quite sure that we are not the only ones that have issues with big FLAs, and that's a shame that a "professional software" loads everything into memory and is not able to be a bit more efficient in the way it handles resources.
That's the same for disk space : I can understand that there are more infos in an FLA than in a SWF (layers and library) but for instance a SWF of 500KB makes an FLA of.... 157 MB (more 300 times the amount of information !). We don't care so much about it since we have plenty of disk space, but when all these informations get loaded into memory... ouch !
What's exactly stored in an FLA ? I would have liked to know more about that, by using for instance the brand new XFL format that was announced before and would "open" the proprietary FLA format by being able to use an xml-based format instead.
Sadly, while XFL would have been very useful to get some informations about FLAs, CS4 can only import XFL and not export it.... WTF ?