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.37 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 30 Aug 2012 14:09:14 -0700
Subject: Re: Cross-compiling Flex to HTML5/Javascript (Was : Update on
 Falcon donation)
Thread-Topic: Cross-compiling Flex to HTML5/Javascript (Was : Update on
 Falcon donation)
Thread-Index: Ac2G70xqhxfgkM78QgKFYdIcmUYBuQABGjab
Message-ID: <CC65248A.457C4%aharui@adobe.com>
In-Reply-To: 
 <CANcBHED+xBEytbr8=ZA+9PeFm8ZO7fvQwtrw+QevLiWYDA72qg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 8/30/12 1:36 PM, "jude" <flexcapacitor@gmail.com> wrote:

> To *guarantee* we get the same results across browsers we need to use
> something like the drawing canvas or SVG (or drawing commands) such as
> Flash uses itself REGARDLESS of performance. If we depend on browser
> manufacturers for different feature sets or API's we will be waiting a lo=
ng
> time. Architecture IMHO is more important than speed because in time CPU
> and GPU performance will increase, in time bandwidth will increase and
> software performance will increase.
That's an interesting point:  I would say targeting HTML(5) can be
successful without guaranteeing same results across browsers.  It might be =
a
formidable amount of work to try to guarantee results given that the browse=
r
manufacturers themselves don't care and have successfully pushed that task
on the developers.
>=20
> Remember when iOS 5 came out a year or so ago? The HTML5 performance in
> that browser was 2FPS. After that update it was 35-40FPS. A 2000% increas=
e.
> [1]
Yes, things get faster, but I would say that performance has been an issue
for Flex for its entire lifetime, and faster devices have not alleviated th=
e
problem.  If Flex 1.0 had gone for a cleaner architecture, it isn't clear i=
t
would have been successful enough to end up here in Apache.
>=20
--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui