incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: What to expect from FalconJS
Date Sat, 17 Nov 2012 23:23:23 GMT



On 11/17/12 10:01 AM, "s├ębastien Paturel" <sebpatu.flex@gmail.com> wrote:

> it depends.
> if the plan is to fully transcode flex app in HTML/JS and then use
> cordova to make it run as native app, yes i have reasons to think that
> it will have poor performances, because in the end it is still an
> HTML/JS app.
I haven't spent any time profiling JS apps.  I have seen some data that says
that JS runs faster than AS in certain situations, and work continues with
JS runtimes to make them faster, the same is not true for the AS runtime.
> if you only use this path for UI, and managed to transcode the logic in
> a real native code, why not.
> If separating the UI management make the cross compilation more easy,
> maybe it can be a viable solution. but it gets back to the question "how
> can you cross compile AS3 to native code".
It isn't obvious to me that if you can translate AS3 to JS why you couldn't
spit out some other language instead.
> And haxe made the choice to change AS3 language to make it more easy to
> cross compile. it means that it is not easy task.
For sure, it won't be an easy task.

I'm just getting started with Cordova.  If Cordova is too slow either they
will find a way to improve it, or it will fade away.  But it is exists today
and a FalconJ or FalconObjectiveC doesn't.  And, I believe it can at least
scroll a textinput and still give native text completion.

Everything we are doing is to provide abstractions to make different targets
possible. All of those things eat away at performance.  That's the price you
pay.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Mime
View raw message