> > There was a significant effect with this though if we did release a > haXe-based SDK. Anyone else using haXe to build upon the SDK would need all > of the Flex source files, not the SWCs and the compiler would recompile > Flex > every time. From crude tests I did with haXe, the need to recompile the > whole SDK every time you built you haXe-based project potentially added 1 - > 2 minutes to the compile time. >
Hm, I think that hurdle alone would be reason enough not to consider HaXe, in its current incarnation of course, as an alternative. I really do agree that with Falcon in our hands we'll be much more flexible, the runtime dependencies will then be something that the community itself can tackle. I totally respect HaXe for what it is, and I think the guys making it are pretty brilliant, but its still no reason to drop actionscript IMHO. Maybe we'll even be lucky and these guys will contribute some of their time on Falcon, I hope it tickles their interest :) Roland