Thanks for the quick response, Greg!

On 12/20/11 9:37 PM, Greg Stein wrote:

That's true, but still would be good to have an open source, up-to-date scripting engine for ActionScript bytecode to enable other future runtimes (imagine running the same ActionScript 3 code in the client and on the server, like node.js). Therefore it would be very valuable to know if Tamarin is still compatible with the scripting engine Flash Player 11.

I'm not sure which projects you are talking about: .NET runtime should be compatible to Mono,

I think it is related to the proposal. If Adobe has binding contracts for future versions of Flex, and the Apache community would decide to change Apache Flex 4.7 implementation details, Adobe might be forced to fork the project for customers. How would that work?

Isn't it a valid question to ask which runtimes will be available for a a framework with compiler? To be technically correct, Flex applications WON'T run in mobile browsers without a Flash Player (which means you won't see a Flex application on iOS). You CAN compile a Flex application into a mobile application using the Adobe AIR SDK and the Adobe AIR player. The proposal mentions rich Internet applications running in desktop and mobile browsers. Elsewhere iOS is mentioned. As we all know, Flash applications (SWF files) cannot be rendered in iOS browser. Therefore the question if there will be a way run mobile Flex applications in mobile browsers as rich Internet applications (versus native apps) is very valid in my eyes.

I've been using Flash for the past 8 years in projects, organized Flex User Group meetings, co-organized events with Adobe. I have a good understanding of what Flash, ActionScript and AIR are capable off, how many people are using Flash, how useful it can be.

But none of the companies offering RIA related products and players in the past 7 years (Adobe, Microsoft, Sun, Oracle, to name the big ones) has not been affected by strategy changes of the management, often leaving developers and clients in positions which were less optimal. (Adobe Flex 1.5 -> 2.0 changes, differences in Silverlight APIs with major version upgrades, Sun/Oracle dumping JavaFX Script, Microsoft's decision to favor HTML5 over Silverlight).

Adobe decided to discontinue development of Flash Player for mobile devices and smart TVs (it's a company decision, we have to respect that, but it wasn't easy for large number of people to hear those news). If they would decide to discontinue the desktop version of Flash Player, wouldn't it be good if the community would have an alternative runtime prepared already? I believe it is in the interest of the Apache Flex community to have an alternative runtime for Flex in the not-too-far future, and if Adobe would express support of that goal , it would be very valuable.

The proposal might have a sentence saying: "Adobe will provide the Apache community with the technical information needed to develop additional runtimes for Flex." Would that be acceptable?

Thanks again for you comments!