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
@curtclifton @owensd Platform bugs suck and are inevitable, but there are other, more resilient ways to cope than monkey patching.
-
-
- View other replies
-
@curtclifton@owensd Swift won't change the current ecosystem. The frameworks are in ObjC regardless. - View other replies
-
@curtclifton@owensd But we'd like mere mortals to be able to ship and maintain reliable libraries too. -
@jckarter I’m all for that. There’s a reason we use almost no 3rd party libraries, and have our own versions of a fair number of Apple’s.
-
-
-
@jckarter@curtclifton@owensd Such as what? - View other replies
-
@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
- Show more
-
-
Michael Tsai
JΛЯΣD
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.