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
-
@jckarter@curtclifton@owensd Such as what?
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
-
@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@mjtsai@curtclifton What about when Apple writes a framework in Swift? Will it remain swizzlable, probably for use from Obj-C? -
@roopeshchander@mjtsai@curtclifton That's a call API review can make when it happens. -
@roopeshchander@mjtsai@curtclifton The goal of the resilience defaults is to avoid developers making irrevocable promises they can't keep. - Show more
-
-
-
@jckarter@curtclifton@owensd By “replacing” do you mean “reimplementing”? -
@mjtsai@curtclifton@owensd Swizzling is reimplementing too. - View other replies
-
-
JΛЯΣD
Roopesh Chander
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.