September 11, 2012 at 13:11Apache Flex posted Falcon sources
The day has come, which I personally have been waiting for a very long time - Falcon sources appeared in Apache repositories - a new stage in the evolution of the flex compiler, the development of which was actively conducted in Adobe before the transfer of Flex to the hands of the redskins.
What we know about Falcon:
- Less memory consumption
- Constant propagation - substitution of constants, getting rid of dead code
- A new concept for checking code on the fly in the IDE using the provided (hopefully lightweight) mechanisms that are part of Falcon
- Speeding up compilation of code , both in incremental and in normal modes
- Multimodular projects should compile much faster (if they don’t lie, then the modules are now compiled multithreaded using java.util.concurrent.IFuture
, which will give an increase with an increase in the number of processor cores) - And finally, the code generated by Falcon is more optimized , which gives benefits not only from the development process, but also in the final product!
It is also worth noting that Falcon improved the process of parsing code, as well as redesigned the entire compilation workflow - now MXML is converted immediately to AST (Abstract Syntax Tree), bypassing code generation, as it was before.
Of course, this will give an increase in the compilation performance of projects containing MXML, and I, as his follower, are very pleased with this fact.
But what about ASC 2.0?
So far, there have been no announcements regarding the development plans of Falcon and ASC 2.0 (the former Falcon, recently announced by Adobe, supporting inline, etc.), while it looks like a fork, but I hope that their further development will go side-by-side, and we, proponents of MXML and more, will not stand aside.
Read
Flex is dead! Long live the new Flex!
