The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Scott Delap on Apr 25, 2007
...Using the MPL for open sourcing Flex will allow full and free access to source code. Developers will be able to freely download, extend, and contribute to the source code for the Flex compiler, components and application framework. Adobe also will continue to make the Flex SDK and other Flex products available under their existing commercial licenses, allowing both new and existing partners and customers to choose the license terms that best suit their requirements...The open source licensing of Flex is part of an initiative to engage the community in the creation of Flex technology. Starting this summer with the pre-release versions of the next release of the Flex product line, code named “Moxie,” Adobe will post daily software builds of the Flex SDK on a public download site with a public bug database. The release of open source Flex under the MPL will occur in conjunction with the final release of Moxie, currently scheduled for the second half of 2007...
InfoQ sat down with Adobe's James Ward and Ely Greenfield to discuss the announcement. Greenfield commented that the reasoning behind the move was to continue to build the developer community around the Flex RIA platform. He noted that it is one thing to have people using technology and another to have a community actively contributing to it. Ward outlined the transition as having the following steps:
Ward also commented on open source Flex in relation to Adobe's Apollo desktop platform. Since Apollo provides a runtime for Flex applications similar to the Flash player itself, changes to Flex by developers will be able to run on Apollo without changes to the Apollo runtime. In response to how development would be lead after the transition, Greenfield replied that the Flex SDK team would continue to drive the big picture of development. Adobe wants to get the community as involved as possible however in terms of providing feedback for where the SDK should go.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Great!
With a good community behind Flex, there is a chance Microsoft' Silverlight & XAML will have a worthy opponent.
I also think this is a brilliant move, now when evaluationg the "open source" RIA framework landscape, Flex can be easily included in any product evaluations. And definitely a good poosition to be in against MS.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
2 comments
Watch Thread Reply