incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Kwiatkowski <>
Subject Re: Flex 5 in haxe
Date Fri, 16 Nov 2012 17:30:55 GMT
On Fri, Nov 16, 2012 at 8:17 AM, Justin Mclean <>wrote:

> I only know a little about Haxe. Could you comment on what would be
> required (in terms of skills and effort) to port Flex to Haxe? I know it's
> ActionScript like but is missing a few features that Flex may be using?
> Other than compiling to multiple targets does it have any other significant
> advantages? Any idea if there are likely to be major performance issues due
> to the fact that Flex is reasonably complex and designed for the Flash VM?

Haxe is a C++ "like" language.  It is not ActionScript, JavaScript, etc.
 It would be a complete re-write of everything we currently already know
and use.

Haxe is unique in that that single C++ like language then can output to
navtive apps, SWF, Silverlight, HTML/JS, etc.  It's not very good at any of
them, and the biggest problem with the language is that it limits itself to
the least common detonator of all the platforms it supports.

> Currently I see no compelling reason to move to the new VM when it comes
> out. Once we know more about it that may change but it sounds like it wont
> be compatible with AS3. The existing one for the moment works and is likely
> to be around for many many years.
AS2 is still well supported (and, surprisingly used) in most outputs.  No
reason to move and essentially invalidate all the work done up to this
point in time.  If we change technologies (HaXe or AS4) we throw out
EVERYTHING the community has built up to now.  Sure, we will have a shiney
new product, but nothing will stand on it.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message