Nolan O'Brien
Mark Townsend
@NolanOBrien yes but you can’t symbolicate crash logs with app thinning./bitcode turned on. 
Twitter app sizes: w/ Swift 1.2 = 65MB w/ Swift 2.0 = 125 MB Thinned w/ Swift 2 = 77 MB Epiphany: App thinning counters Swift 2.0 bloat
-
-
- View other replies
-
@markltownsend app thinning is an attempt to reduce bloat from Swift. Mktng it as a benefit for devs neglects the reality... -
@markltownsend ... Most notably that apps won't get smaller and worse (as you pointed out) they'll actually get bigger for some. -
@markltownsend though, if I'm trying to be optimistic, one can hope swift libs will no longer needed and app thinning will stop brking syms
-
-
-
@NolanOBrien The 65 MB size is the zip compressed IPA. 6.35.1 uncompressed .app was 124.7 MB. - View other replies
-
@TannerOakes App Store shows 85mb for 6.36.1 (vs 65 of 6.36) - View other replies
-
@TannerOakes maybe that's just an upper bound? -
@NolanOBrien Upper bound makes sense. Or maybe the App Store knows what device the request is coming from and how big that slice will be. -
@TannerOakes yeah, that could be. But it seems odd that 85 mb compressed would decompress to 77 mb
-
-
-
@NolanOBrien How much of that is from the Swift libraries vs. your compiled code? -
@mjtsai all swift libs
-
-
-
@NolanOBrien is already 100% Swift 2.0? -
@angrauel nope...not even 5%
-
-
@NolanOBrien@robertsammons you're gonna give Taylor self confidence issues. -
-
@nolanobrien@neonacho Why such an incredibly large increase in size with Swift 2? - View other replies
-
@steipete@NolanOBrien don't know — but the increase is also visible in libswiftCore.dylib itself — 3.0MB vs. 4.8MB -
@NeoNacho@NolanOBrien still surprisingly small. -
@steipete@NolanOBrien looks like they added armv7s slices, which explains at least a part of the increase of the dylibs -
@NeoNacho@NolanOBrien what? armv7s is still a thing? -
@steipete@NolanOBrien it’s weird — maybe carOS has to run on A6 devices? ;)
-
Non-modular header
Michael Tsai
Andreas
Darren Grimes
Peter Steinberger
Yo, tu sabes? Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.