Curt Clifton
A recent thread on the swift-evolution mailing list has me very concerned. http://curtclifton.net/app-developers-on-swift-evolution … /cc @dwaite @wilshipley @dgregor79
-
@curtclifton@owensd Platform bugs suck and are inevitable, but there are other, more resilient ways to cope than monkey patching.
David Owens II
Joe Groff
Michael Tsai
-
-
@mjtsai@curtclifton@owensd Replacing functionality for yourself is more modular than trying to dynamically change it in the framework. - View other replies
-
- View other replies
-
@curtclifton@jckarter@owensd I don’t see how it advances the platform to have everyone relying on middleware instead of the frameworks. -
@mjtsai@curtclifton@owensd Well defined modular components make everyone's life easier. Today's frameworks aren't there, sure. -
@jckarter@mjtsai@curtclifton@owensd Consider UITextView in iOS 7. Unusably broken for *a year* w/out subclass workarounds. - View other replies
-
@jaredsinclair@mjtsai@curtclifton@owensd Like I said, Swift's defaults won't change how ObjC works or even the policy of new frameworks. - View other replies
-
@jckarter@jaredsinclair@curtclifton@owensd It does change new frameworks unless you’re going to explicitly mark everything as dynamic. - Show more
-
-
@mjtsai@jckarter I like@andy_matuschak’s expression of it: treat {App,UI}Kit as a library rather than a framework. But it’s really hard.
JΛЯΣD
Rob Rix
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.