Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.238 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Mon, 1 Jul 2013 21:57:19 -0700
Subject: Re: Are we "nerd" driven or "business realistic" driven?
Thread-Topic: Are we "nerd" driven or "business realistic" driven?
Thread-Index: Ac524KIdyEA5YTpJSGO4lYyXd9lC9g==
Message-ID: <CDF7AA69.C8F1%aharui@adobe.com>
In-Reply-To: 
 <CAGEhWpGBYroowoUzFFS1fMBQAYZj8VEJ96SN9W3rRQLN7oRJyg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.4.130416
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 7/1/13 10:15 AM, "Avi Kessner" <akessner@gmail.com> wrote:

>Why can't we get rid of those 13k line base classes?
>On 1 Jul 2013 20:03, "Jonathan Campos" <jonbcampos@gmail.com> wrote:
We can, but not without breaking backward compatibility or slower
performance.  In the two attempts I made, you can break UIComponent into
some 20 sub-components but unless you break backward compatibility, many
of those sub-components have to be instantiated during the startup phase
and the extra overhead of calling in and out of the subcomponents slowed
things down. =20

That's why FlexJS isn't guaranteeing backward compatibility.  We can take
those sub-components and load them on-demand at different times.

-Alex