Regarding my tweets yesterday about Swift not being dynamic, as long as Obj-C sticks around I don't see that being an issue
-
-
@pilky I do. The problem is when I want to interoperate with others’ code. If they thought “this doesn’t need to be dynamic”, it’s harder.0 replies 0 retweets 1 like -
@amyruthworrall But I'd wager that 90+% of the Obj-C code you've ever written isn't inherently dynamic code0 replies 0 retweets 0 likes -
@pilky Most of my apps have a classFromString, or a class_addMethod, or a resolveInstanceMethod. It’s a style I like.0 replies 0 retweets 0 likes -
@amyruthworrall And is there something that would prevent those particular parts of your app being written in Obj-C?0 replies 0 retweets 0 likes -
@pilky@amyruthworrall If you're trying to do dynamic stuff with other people's compiled code, it's easier if they didn't use Swift.0 replies 0 retweets 0 likes -
@mjtsai@amyruthworrall True, but technically you should only be doing that for either debugging or as an absolute last resort0 replies 0 retweets 0 likes
@pilky @amyruthworrall Yes, but practically speaking frameworks have bugs, and apps are missing features that users want. Dynamism can help.
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.
Martin Pilkington
Amy Worrall
Michael Tsai