Investigate re-ordering build file

[dcherman]

By changing the order that the various .js files are included, you can change the eventual gzipped output.

This is due to the way duplicate string elimination works on 32KB boundaries - since the minified source of jQuery will be greater than that, re-ordering them can change the results.

​http://en.wikipedia.org/wiki/DEFLATE#Duplicate_string_elimination

There's an existing pull request that reduces size by 140 gzipped bytes, however the re-ordering may be too drastic. That said, you can still improve the results by a lesser degree by moving a couple of them around.

​https://github.com/jquery/jquery/pull/595

[jzaefferer]

-1, 140bytes is the upper bound? Sounds like a waste of time.

[jaubourg]

+0, I'd like to see big gains here.

[dmethvin]

-1, Probably not worth the work, but I suspect we'll do a lot of reorg to the build process when Closure Compiler mods arrive.

[mikesherov]

+1, this would require a centralized spot where we define the build order. currently, it's sprinkled around in several locations: the makefile, the unit tests, and soon in the JSHint checker. If the centralization occurs, I see no reason NOT to do this. To put this in context, I spent about 2 hours the other day golfing 40 bytes out of a pull request. 140 bytes is a big win IMO.

[timmywil]

+0, I'm fine with experimenting.

[Rick Waldron]

+0