Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9630DA63 for ; Fri, 16 Nov 2012 20:58:50 +0000 (UTC) Received: (qmail 2669 invoked by uid 500); 16 Nov 2012 20:58:50 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 2617 invoked by uid 500); 16 Nov 2012 20:58:50 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 2606 invoked by uid 99); 16 Nov 2012 20:58:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 20:58:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gosmith@adobe.com designates 64.18.1.234 as permitted sender) Received: from [64.18.1.234] (HELO exprod6og119.obsmtp.com) (64.18.1.234) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 20:58:39 +0000 Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob119.postini.com ([64.18.5.12]) with SMTP ID DSNKUKao6SHI2KArZVIT4+AFGIP/tekK6avF@postini.com; Fri, 16 Nov 2012 12:58:18 PST Received: from inner-relay-4.eur.adobe.com (inner-relay-4.adobe.com [193.104.215.14]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id qAGKtS1v004395 for ; Fri, 16 Nov 2012 12:55:29 -0800 (PST) Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id qAGKwFXL005291 for ; Fri, 16 Nov 2012 12:58:15 -0800 (PST) Received: from nambx05.corp.adobe.com ([10.8.189.124]) by nacas01.corp.adobe.com ([10.8.189.99]) with mapi; Fri, 16 Nov 2012 12:58:14 -0800 From: Gordon Smith To: "flex-dev@incubator.apache.org" Date: Fri, 16 Nov 2012 12:58:13 -0800 Subject: RE: Flex 5 in haxe Thread-Topic: Flex 5 in haxe Thread-Index: Ac3EONdaGHfKIRnVTs6p2/bXk2LR/gAA+Mew Message-ID: <149F8129B58B2D418508E63117D9C5419B5B35FF4C@nambx05.corp.adobe.com> References: <813661353067194@web29g.yandex.ru> <2AF11B3E-2586-4973-9030-A225C35F0879@classsoftware.com> <149F8129B58B2D418508E63117D9C5419B5B35FEFD@nambx05.corp.adobe.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org > From what I previously read, I don't think we were getting an updated Fal= con compiler that will generate AVM3 code. > They were not planning on open-sourcing that (but correct me if I'm wrong= in that aspect). That's correct. Adobe has no plans to open-source its new AS4-for-V12 compi= ler. - Gordon -----Original Message----- From: Nicholas Kwiatkowski [mailto:nicholas@spoon.as]=20 Sent: Friday, November 16, 2012 12:27 PM To: flex-dev@incubator.apache.org Subject: Re: Flex 5 in haxe On Fri, Nov 16, 2012 at 3:08 PM, Stefan Horochovec < stefan.horochovec@gmai= l.com> wrote: [snip] > The development of the new VM and AS4 specification is not reported or=20 > discussed with Apache Flex, knowing that we depend exclusively of=20 > Flash Player and AIR to execute applications. This in my opinion is terri= ble. > > Again we will have to wait for an update from Falcon to generate code=20 > for the V12, this delay the progress of the Flex when we are expecting=20 > more and more code from Adobe. > > I'm not saying that we should use haxe, or some other compiler, just=20 > think the time is an even broader discussion. The Flex should continue=20 > only with Flash Player / Adobe AIR runtime? > This is, and has been par for the course. When Adobe doesn't want to hear us whine and moan, they close off development. It happened before (and in many more products than just Flex/Flash), and I'm sure it will happen often= in the future. They feel they can surround themselves with "stakeholders" (a small, select subset of customers that their marketing team found them) to make major changes to platforms, products, etc. At least this time, they were pretty clear in saying we wouldn't have a seat in the table for t= he future. Previous times they gave us the illusion that we did. >From what I previously read, I don't think we were getting an updated Falco= n compiler that will generate AVM3 code. They were not planning on open-so= urcing that (but correct me if I'm wrong in that aspect). I'm pretty sure the community as a whole over the last 11 months have deter= mined to break our dependency of the Flash Player. We've had a LOT of prop= osals on how to do it -- none of them executed yet. The silliest of the bu= nch in my opinion is porting to HaXe or starting from scratch. Our power i= s leveraged from Adobe's initial 200,000 hours of labor over the last many = years. We got an awesome code-base that while, it needs some major tweaks,= is is really good shape. Dumping out the baby with the bath-water is not = the way to go on a platform that is mature and used by MANY large enterprises. That being said -- this is now in the Apache world and I can't stop anybody from doing that, but I won't also be helping= redo Flex from scratch. -Nick