Peter Steinberger
Rob Napier
@steipete @heathborders I continue to be at a loss as to why dynamic (vs. static) frameworks are the answer to modules in Swift.
Super interesting thread about dynamic frameworks and load time.https://github.com/artsy/eigen/issues/586 …
-
-
- View other replies
-
@steipete@heathborders Why would anyone think that single-consumer (one app) "shared" libraries make sense? What possible benefit? - View other replies
-
@cocoaphony@steipete In the thread,@Dirk_Gently says@CocoaPods dynamic frameworks a list, not a tree. I don't know what that means. -
@heathborders@steipete@Dirk_Gently I'm pretty sure@CocoaPods (correctly) flattens all your deps & sub-deps into a single list. -
@cocoaphony@steipete@Dirk_Gently So in OSX, if App A needs Framework F, and F needs G, G would be inside of F inside of A? - View other replies
-
@heathborders@steipete@Dirk_Gently If done correctly, F and G should both be inside A. Frameworks should be in other frameworks. - View other replies
-
@cocoaphony@heathborders yes but G shouldn’t be linked on A, which was what I was pushing to have looked into. -
@Dirk_Gently@cocoaphony Thanks. Is there a good place to read about this? - Show more
-
Heath Borders
Demi-lich 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.