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 jszczepankiewicz@gmail.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALorpXenA0Ku2fLx3PRaTRdLTTOJE+wJye=CBWtrQQ_bT8rhuw@mail.gmail.com>
References: 
 <CAFzDyY3SktT8xBCCgQEjjq0YgLexnWVzA8_dt-OWoSP69kfahw@mail.gmail.com>
	<CB53BF9A.3B8E5%aharui@adobe.com>
	<CAFzDyY14AwYoJ09keDOHEQAZeTJefutduyYKhWQRGO2xSL4iEQ@mail.gmail.com>
	<CALorpXenA0Ku2fLx3PRaTRdLTTOJE+wJye=CBWtrQQ_bT8rhuw@mail.gmail.com>
Date: Mon, 6 Feb 2012 08:46:29 +0100
Message-ID: 
 <CAKPa92237MAyZA+vV7yHMWPzwaNEuAOzO0A0xktVy=g+Zt=31w@mail.gmail.com>
Subject: Re: will ever adobe give the flashplayer to the opensource comunity
From: =?UTF-8?Q?Jaros=C5=82aw_Szczepankiewicz?= <jszczepankiewicz@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

it will materialize for sure (the question is when) if they want to
"invest in gaming", currently even low end machines have at least two
physical cores. But I am afraid that the api given to the user will be
not comparable to what we call worker i.e. in java. I speculate but in
order to not complicate AVM internal synchronization they probably
will use workers in form something of swfloader (from flex). Separate
swf with passed variables (by values), without access to some shared
memory (stage, display list, arrays etc.), returning some new
objects?. Something more comparable to modern languages with
multhtreading will complicate the internals of AVM, and adobe can not
afford making the AVM not backward compatible at this moment. But that
only my speculations.

2012/2/6 Nicholas Kwiatkowski <nicholas@spoon.as>:
> Multithreading (actually, it is a psudo-thread using child workers) was
> talked about publicly at MAX a few months ago. =C2=A0They have not commit=
ted to
> anything, but they did state that they have it on their current roadmap.
> =C2=A0To us, that means that we may see it in a future release of the FP
> (hopefully sooner than later), but it may never materialize.
>
> -Nick
>
> On Sun, Feb 5, 2012 at 5:04 PM, Stephane Beladaci <
> adobeflexengineer@gmail.com> wrote:
>
>> Agreed, I do not believe we need Flash Player to be opened source to do
>> great stuff with Apache Flex, as I think you mentioned before Alex the c=
ost
>> for Flex is now 0 since the community will be developing so even with th=
e
>> Flash Player as it is we should be able to keep pushing Flex further tha=
n
>> Adobe did since there is no commercial agenda anymore. Adobe will probab=
ly
>> also improved the Flash Player as part of their own agenda and use, is
>> multi threading still on the map for this year?
>>
>> > On 2/4/12 5:24 PM, "Stephane Beladaci" <adobeflexengineer@gmail.com>
>> wrote:
>> > OK, that's enough speculation for now. =C2=A0Let's move on. =C2=A0I wi=
ll probably
>> ask
>> > my management chain every year on the anniversary of Apache Flex's
>> > acceptance into the incubator if this is the year we will open source =
it.
>> > Last time I asked, the answer was not "never".
>> >
>> > But for now, this podling has to assume there won't be any improvement=
s
>> in
>> > the flash player and make the best of what we have now. =C2=A0And I am=
 still
>> > convinced that what we have now is capable of really impressive stuff.
>> >
>> > --
>> > Alex Harui
>> > Flex SDK Team
>> > Adobe Systems, Inc.
>> > http://blogs.adobe.com/aharui
>> >
>>