I'm not really sure but I presume concurrency is important for various gaming uses cases. As you know, Adobe's new focus for Flash Player is on gaming and high-end video and if a new feature doesn't further this new strategy, it is less likely to happen.
- Gordon -----Original Message----- From: Joan Llenas Masó [mailto:joan.llenas.m...@gmail.com] Sent: Monday, February 06, 2012 10:47 AM To: flex-dev@incubator.apache.org Subject: Re: will ever adobe give the flashplayer to the opensource comunity Hi Gordon, From my ignorance in this field... I'm cuorious about what use cases will this concurrency model be solving. Number crunching is one of them for sure, as there's no need to share memory, but do you have anything more "Flash Player oriented" in mind? Cheers! -- Joan Llenas Masó http://joan.garnet.io @joangarnet (es) @joanllenas (en) On Mon, Feb 6, 2012 at 19:31, Gordon Smith <gosm...@adobe.com> wrote: > Yes, concurrency is coming ASAP. > > Gordon Smith, Adobe > > -----Original Message----- > From: Jarosław Szczepankiewicz [mailto:jszczepankiew...@gmail.com] > Sent: Sunday, February 05, 2012 11:46 PM > To: flex-dev@incubator.apache.org > Subject: Re: will ever adobe give the flashplayer to the opensource > comunity > > 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 <nicho...@spoon.as>: > > Multithreading (actually, it is a psudo-thread using child workers) > > was talked about publicly at MAX a few months ago. They have not > > committed to anything, but they did state that they have it on their > current roadmap. > > To 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 < > > adobeflexengin...@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 cost for Flex is now 0 since the community will be > >> developing so even with the Flash Player as it is we should be able > >> to keep pushing Flex further than Adobe did since there is no > >> commercial agenda anymore. Adobe will probably 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" > >> > <adobeflexengin...@gmail.com> > >> wrote: > >> > OK, that's enough speculation for now. Let's move on. I will > >> > 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 > >> > improvements > >> in > >> > the flash player and make the best of what we have now. And 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 > >> > > >> >
