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 B64F1DF3D for ; Fri, 16 Nov 2012 17:31:25 +0000 (UTC) Received: (qmail 17830 invoked by uid 500); 16 Nov 2012 17:31:24 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 17763 invoked by uid 500); 16 Nov 2012 17:31:24 -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 17754 invoked by uid 99); 16 Nov 2012 17:31:24 -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 17:31:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Nov 2012 17:31:16 +0000 Received: by mail-bk0-f47.google.com with SMTP id jk7so1253421bkc.6 for ; Fri, 16 Nov 2012 09:30:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=kwzjS+oHmkTJKIKgjXELT6PvSiCFCj8GcP5pyuOgfn4=; b=gnQYgnBOpKv+pFRt+w+Xzp64xhaJJFWrqP8VjulXfosSbsH4A5R7zHdzZ2b9fkzLzQ 6vVfovnRsi1PdDLn5Z84aLEuCzH1gp794ZOndF0UkeXwA6DGZPqlQnKLhDTYaE1mouSf FMluEh5E2W/HY1GkR2TjoDrIIhciBdES0KgS6Qr+kgzYzJCH6MRy48XqKFeLCInIAW/n fbIAzeG36lfSrpfEXdisry0B1LeEmD5HgK+XVLwbF7cnE+aq+i8X6JBw++R9mAxCfyJk 9+MammoG0IGhBy7begtakNPH5AB5P26Sdmlou7I1bdWC7zOD4AC/zakuslF0o0fSjuQl f31g== MIME-Version: 1.0 Received: by 10.204.147.5 with SMTP id j5mr905015bkv.49.1353087055429; Fri, 16 Nov 2012 09:30:55 -0800 (PST) Received: by 10.204.66.136 with HTTP; Fri, 16 Nov 2012 09:30:55 -0800 (PST) X-Originating-IP: [173.10.39.57] In-Reply-To: <2AF11B3E-2586-4973-9030-A225C35F0879@classsoftware.com> References: <813661353067194@web29g.yandex.ru> <2AF11B3E-2586-4973-9030-A225C35F0879@classsoftware.com> Date: Fri, 16 Nov 2012 12:30:55 -0500 Message-ID: Subject: Re: Flex 5 in haxe From: Nicholas Kwiatkowski To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0015174bde0449ffd804cea021c3 X-Gm-Message-State: ALoCoQlrX1l/t3y+ymTYlnrOcHew8GoQIXSd35sSyiCdoWd5gjPEpr1PCrbp89Ttuhi2G20QRh6F X-Virus-Checked: Checked by ClamAV on apache.org --0015174bde0449ffd804cea021c3 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 16, 2012 at 8:17 AM, Justin Mclean wrote: > > I only know a little about Haxe. Could you comment on what would be > required (in terms of skills and effort) to port Flex to Haxe? I know it's > ActionScript like but is missing a few features that Flex may be using? > Other than compiling to multiple targets does it have any other significant > advantages? Any idea if there are likely to be major performance issues due > to the fact that Flex is reasonably complex and designed for the Flash VM? > Haxe is a C++ "like" language. It is not ActionScript, JavaScript, etc. It would be a complete re-write of everything we currently already know and use. Haxe is unique in that that single C++ like language then can output to navtive apps, SWF, Silverlight, HTML/JS, etc. It's not very good at any of them, and the biggest problem with the language is that it limits itself to the least common detonator of all the platforms it supports. > Currently I see no compelling reason to move to the new VM when it comes > out. Once we know more about it that may change but it sounds like it wont > be compatible with AS3. The existing one for the moment works and is likely > to be around for many many years. > > AS2 is still well supported (and, surprisingly used) in most outputs. No reason to move and essentially invalidate all the work done up to this point in time. If we change technologies (HaXe or AS4) we throw out EVERYTHING the community has built up to now. Sure, we will have a shiney new product, but nothing will stand on it. --0015174bde0449ffd804cea021c3--