Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.191 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Fri, 16 Nov 2012 09:38:47 -0800
Subject: Re: [POLL] - Must Flex 5 be a complete rewrite or can flex code
 base be re-architectured?
Thread-Topic: [POLL] - Must Flex 5 be a complete rewrite or can flex code
 base be re-architectured?
Thread-Index: Ac3EH5UOkauvm1SqQ3uDAi371YPULgAAaYqp
Message-ID: <CCCBBA27.489C0%aharui@adobe.com>
In-Reply-To: <50A6773C.4060803@gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.13.0.120411
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 11/16/12 9:26 AM, "s=E9bastien Paturel" <sebpatu.flex@gmail.com> wrote:

> Le 16/11/2012 17:53, Alex Harui a =E9crit :
>>   I still remain
>> convinced that once you force folks to rewrite their business logic in
>> another language, then they are more likely to review all of the
>> possibilities out there, and there are currently many, like Sencha,
>> PhoneGap/Cordova, going native for mobile
> But they are JS frameworks and native dev is not comparable to multi
> platform development.
Cordova is definitely about multi-platform.
> In fact i think that some flex users already made a switch to native dev
> because of the lack of visibility for flex future.
>=20
> I can't wait to ear about what you have to propose for the #2 objective.
> Maybe thats why you are more confident about the "keep AS3" solution.
> But your final objective is to get full backward compatibility at the end=
?
I don't think full backward-compatibility is a requirement, but IMO, it is
most important for the business logic and that's where it should be easiest
to transcode as it should have fewer platform dependencies.
> Because you are the one who convinced me that a full rewrite was
> inavitable, so if we don't have full compability at the end of the
> rewrite, why using AS3 is so important for third party code already
> existing?
Because I expect the major factor in deciding what to do with your existing
apps is about the cost of moving.  For sure, if you completely abandon Flex
you will have to rewrite all of your views and all of your business logic.
If I offered a solutions where you still had to rewrite your views but not
too much of your business logic, I think that would make it an attractive
choice.
>=20
> Do you think that trying to keep things like AS3 won't be paid by huge
> performances issues?
That's my hope.  Still needs to be proven.  IMO, the performance issues you
are hitting are due to the bad code in the framework, not AS3 itself.
That's why folks who do skip Flex and just write AS3 apps seem to have fewe=
r
performance complaints.
>=20

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