You can tell Swift is fundamentally static because otherwise there couldn’t even be talk about the compiler optimizing the dynamic parts.
-
-
@mjtsai It's as dynamic or static as your program needs to be.0 replies 0 retweets 0 likes -
@jckarter Not when my program is linking to code that already has the dynamism compiled out.0 replies 0 retweets 1 like -
@mjtsai You can link to public classes and protocols and get the dynamism you expect.0 replies 0 retweets 0 likes -
@jckarter I don't think I could do something like this with a hypothetical Swift AppKit. Dispatch, but no msg send. http://furbo.org/2014/04/18/get-ready-for-june-2nd/ …0 replies 0 retweets 1 like -
@mjtsai You can't do that today, either. Any change to NSFont's impl could break hacks like this.0 replies 0 retweets 0 likes -
@jckarter It’s not future proof, but it works great for debugging or temporarily working around a framework bug.0 replies 0 retweets 1 like -
@mjtsai Sure, but then those workarounds end up in production builds, and Foundation grows more scar tissue to work around the workaround.0 replies 0 retweets 0 likes
@mjtsai Longer term I think everyone's happier when components respect each other's boundaries.
-
@jckarter Just used swizzling to work around a CorePDF crash. I’m not a fan of scar tissue, but it’s better than crashing.0 replies 0 retweets 0 likes
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.
Michael Tsai
Joe Groff