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.33 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Wed, 29 Aug 2012 08:05:08 -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: Ac2F6pCpVGIIpXwCSq6b0zDp0YXNqgADRz37
Message-ID: <CC637DB4.455AA%aharui@adobe.com>
In-Reply-To: 
 <CAMFKFRiNbT4n0Kb34Ux6Pe3G6zkho+zCwO1L1OD9j5ZQrojH+w@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/29/12 6:30 AM, "Carlos Rovira" <carlos.rovira@codeoscopic.com> wrote:


>=20
> One thing I never understood was Adobe not helping to open source
> Flash Player=20
My understanding is that one major factor is that key aspects of the player
depend on 3rd party works.

> or transforming it to help to be the industry standard.
IMO, an initial step in that was the Open Screen Project.  The problems wit=
h
Chrome show how hard allowing third parties to develop aspects of the playe=
r
are.  However, we could try to have Apache become an OSP partner.  Not sure
if that would work though.
> They they managed it is pushing the player to some uncertain future.
> Take a look to the recent problems with Chrome that make
> LocalConnection to break functionality.
>=20
> Sometimes I think why web technologies are such problematic and why we
> don't have today some robust ecosystem free of flame and company
> wars...
In some ways, that's what keeps us employed :-)

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