On 4/25/13 1:55 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> Om,
>
>> Erik, to be fair, you said that you are not interested in debating over a
>> 6k difference. I dont think Alex is raising this issue as a 'lead', rather
>> a justified technical question. As a comparison, the dojo and jquery
>> frameworks are 41KB and 32KB (minified) In these terms, 6KB of minified JS
>> seems like a big enough percentage to merit a technical discussion. Dont
>> you agree?
>
> Nope, I don't. The 6k addition is just about the entire contribution
> that the use of the Google Closure Library will add to the size of the
> deliverable, which puts us way ahead of any of the other libs.
Are you claiming that after using goog.events we can use other packages from
Google Closure and there won't be any additional size increase?
> The
> images - or SVG files - for the button states alone will contribute
> such an increase in the size of the final deliverable that the size
> increase caused by the addition of 6k of highly optimised JS is
> negligible.
>
The button states are optional. Goog.event's 6K is not.
Om, Justin, please read the following. If it does not change your mind
about taking Erik's change then we will take it since I will have then been
outvoted.
1. You only get once chance to make a first impression. Even if the app
starts fast when your JS or RSL is cached, the fact is that there are times
when it isn't cached. In early 2011, a vendor of a very popular consumer
desktop app was looking to port their app to Flex. They could not because
of the startup time for first time users. A couple of banks reported the
same issue trying to build consumer facing apps. I think that helped seal
Flex's fate. We were never able to use Flex to deliver a popular app that
everyone had to have.
2. At home, I get about 80K/sec download speed. This 6K I won't feel, but
if we keep adding 6K just because we think it will have fewer bugs, it won't
take long before I feel it.
3. I would like to do a poll to see if we need to support IE6 and/or IE7,
but will it change your opinion if we don't need to support these old
browsers? If not, then the votes have been cast.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
