So what do you think about it? I don't see the changes that kind of negative.
Having an independent Foundation is a big chance for 3th Party vendors to be part of that project. The question "who comes first" or "who is the leader" in such a project is actually the question that nobody is interested in ... except the management teams of the projects. And even they should notice that after all negative feeling to be "eaten" by others that in the end the profit is what counts. And the profit is naturaly bigger in ONE big project as if your business decisions are affected on the question "what can we do to compete with Adobe". In terms of the OpenLaszlo project it would be kind of a re-union of what always belonged together ... not only in terms of technology but also as it somehow feels like 50% of the the folks working at OL have been former or present Adobe/Macromedia staff and vice versa And last but not least beeing native compatible with potential "Apache Flex" would result in having an update possibility for all existing customers .... While currently I guess nobody will invest big amounts of $ into a technology not knowing what happens in 1,2,3 or 10 years. Sebastian 2011/11/17 Raju Bitter <[email protected]> > Another update on the Adobe/Flash/Flex developments of the past week. > Instead of the Open Spoon Foundation, it's now the ASF: > "Given this, we are planning to contribute the Flex SDK to an open > source foundation in the same way we contributed PhoneGap to the > Apache Foundation when we acquired Nitobi" > > Should the ASF agree to take the technology, the road map will be > managed by an independent governing body operating under Apache's > bylaws. Adobe will continue to dedicate full-time engineers to further > debug and develop the SDK, the company pledged. > > Link to the blog post, and longer excerpt: > http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html > > > > We know Flex provides a unique set of benefits for enterprise > application developers. We also know that the technology landscape for > application development is rapidly changing and our customers want more > direct control over the underlying technologies they use. Given this, we > are planning to contribute the Flex SDK to an open source foundation in the > same way we contributed PhoneGap to the Apache Foundation when we acquired > Nitobi. > > What specifically is Adobe proposing? > > 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) > > Falcon JS, an experimental cross-compiler from MXML and ActionScript to > HTML and JavaScript. > > 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. > > -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
