Upon a week of drama across the world of Flex, the past week proved to be business as usual… and thank heavens for that.
In case you have missed it, the Flex team at Adobe has amended their original statement regarding the future of Flex in the context of Adobe.
We are preparing two proposals for incubating Flex SDK and BlazeDS at the Apache Software Foundation.
In addition to contributing the core Flex SDK (including automation and advanced data visualization components), Adobe also plans to donate the following:
- Complete, but yet-to-be-released, Spark components, including ViewStack, Accordion, DateField, DateChooser and an enhanced DataGrid.
- BlazeDS, the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Flex applications.
- Falcon, the next-generation MXML and ActionScript compiler that is currently under development (this will be contributed when complete in 2012)
- Flex testing tools, as used previously by Adobe, so as to ensure successful continued development of Flex with high quality
Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility. Adobe has in-development work already started, including additional Spark-based components.
You can read the entire post here:
Eventually, its a much more positive and inspirational variant of the post after the update compared to the original one, so thanks to Andrew and Deepa for taking the time to make the effort to apply the amendment.
In retrospect, I found the entire experience of having the bag shaken in which we have placed our faith to be motivational and a reminder to update my skillset. This last point is something we can all take away from this experience.
Upon talking with dozens of Flex developers over the past weeks, it became clear that some of us had forgotten to stay updated and expand our toolset, and regardless of what happens to Flex, this is an important reminder. A professional is only as good as his tools allow him to be and the quality of the output depends on both the skill of the professional as well as their ability to choose the right tool for the job.
We should use Flex when it makes sense and remember to stay tuned to what is going on in other areas or our industry for the moment when Flex may not be the optimal tool for the job.
Another reminder I have taken away from this experience is my old commitment to continuously contribute to at least one Open Source project at any given time… obviously I will be contributing to Flex once it hits the repositories… why don’t you join me ?