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
David Owens II
Joe Groff
Michael Tsai
@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. -
@mjtsai@jckarter@jaredsinclair@curtclifton@owensd I suspect that’ll happen coz the Swift-written framework should be usable from Obj-C. -
@roopeshchander Eventually they’re going to want frameworks that take advantage of Swift features that don’t work with Objective-C. -
@mjtsai Agreed. That may be a few decades in the future, but it’s better it’s discussed about now. -
@mjtsai OTOH, a Swift framework to be used only from Swift written decades later would most likely use POP => we can override the protocol - Show more
-
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.