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 20:27:14 GMT
On Fri, Nov 16, 2012 at 3:08 PM, Stefan Horochovec <> wrote:


> The development of the new VM and AS4 specification is not reported or
> discussed with Apache Flex, knowing that we depend exclusively of Flash
> Player and AIR to execute applications. This in my opinion is terrible.
> Again we will have to wait for an update from Falcon to generate code for
> the V12, this delay the progress of the Flex when we are expecting more and
> more code from Adobe.
> I'm not saying that we should use haxe, or some other compiler, just think
> the time is an even broader discussion. The Flex should continue only with
> Flash Player / Adobe AIR runtime?

This is, and has been par for the course.  When Adobe doesn't want to hear
us whine and moan, they close off development.   It happened before (and in
many more products than just Flex/Flash), and I'm sure it will happen often
in the future.  They feel they can surround themselves with "stakeholders"
(a small, select subset of customers that their marketing team found them)
to make major changes to platforms, products, etc.   At least this time,
they were pretty clear in saying we wouldn't have a seat in the table for
the future.  Previous times they gave us the illusion that we did.

>From what I previously read, I don't think we were getting an updated
Falcon compiler that will generate AVM3 code.  They were not planning on
open-sourcing that (but correct me if I'm wrong in that aspect).

I'm pretty sure the community as a whole over the last 11 months have
determined to break our dependency of the Flash Player.  We've had a LOT of
proposals on how to do it -- none of them executed yet.  The silliest of
the bunch in my opinion is porting to HaXe or starting from scratch.  Our
power is leveraged from Adobe's initial 200,000 hours of labor over the
last many years.  We got an awesome code-base that while, it needs some
major tweaks, is is really good shape.  Dumping out the baby with the
bath-water is not the way to go on a platform that is mature and used by
MANY large enterprises.   That being said -- this is now in the Apache
world and I can't stop anybody from doing that, but I won't also be helping
redo Flex from scratch.


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