Hello list, There are some fair points made in this thread.
Why waste resources on a HTML/js target when flex is far too far behind equivalent javascript frameworks? There are some arguments against this though: cross-compiling brings about new ways of using existing methodologies, new ways of using existing tools, and a body of existing knowledge that would otherwise simply go to waste. Javascript is not known for type safety, rigorous testing methodology, large-scale applications produced by large development teams, so many developers switching to this runtime will simply have to adapt to a development mindset geared towards the quality and productivity metrics of the runtime. The "point" of cross-compiling to javascript, is to have a premium framework with premium tools producing premium products on a runtime otherwise known for flakier variants. If you take the attitude of "who cares, flash is here now, when js arrives I will move to xyz framework", this seems like passing an opportunity to leapfrog the competition, and a lack of experience in the javascript industry. As already pointed out, those of us who don't see the flash player as a viable runtime for future proofing, will probably spend little time improving the flash parts of flex, so it's no use arguing where the brunt of the open source work should go. People will decide for themselves if they want to take part in flex, depending on the direction the development takes it. I think the more relevant question is: if a branch of the flex code occurs, that goes into an alternative js/HTML compiler, who is going to be backing it with sweat and coding ? Will it be a part of the official repo, or an outcast ? What compiler will it use ? Any other question is beating around the bush. I personally don't think haxe has a syntax that is different from actionscript (it is based on AS3 and is a subset). The learning curve for actionscript developers is trivial, it is a small step compared to learning javascript, C++ or scala. Citing this as a reason against haxe, is really an argument against change of technology in general, staying with the AVM runtime, and hoping against a slow and meaningless extinction. - Niel On Mon, Feb 27, 2012 at 6:38 PM, Maciek Sakrejda <m.sakre...@gmail.com>wrote: > > Of course, if we talk about dumping all Flex display code, maybe this > > is no longer a Flex framework project but an independent > > ActionScript-to-JS cross-compiler (which may or may not support some > > subset of the Flex framework). > > Also, the haXe solution being discussed may be more reasonable in this > context... >
