-
-
@curtclifton@jckarter@owensd I don’t see how it advances the platform to have everyone relying on middleware instead of the frameworks.0 replies 0 retweets 1 like -
@mjtsai@curtclifton@owensd Well defined modular components make everyone's life easier. Today's frameworks aren't there, sure.0 replies 0 retweets 1 like -
@jckarter@mjtsai@curtclifton@owensd Consider UITextView in iOS 7. Unusably broken for *a year* w/out subclass workarounds.0 replies 1 retweet 4 likes -
@jaredsinclair@mjtsai@curtclifton@owensd Like I said, Swift's defaults won't change how ObjC works or even the policy of new frameworks.0 replies 0 retweets 2 likes -
@jckarter@mjtsai@curtclifton What about when Apple writes a framework in Swift? Will it remain swizzlable, probably for use from Obj-C?0 replies 0 retweets 0 likes -
@roopeshchander@mjtsai@curtclifton That's a call API review can make when it happens.0 replies 0 retweets 1 like -
@roopeshchander@mjtsai@curtclifton The goal of the resilience defaults is to avoid developers making irrevocable promises they can't keep.0 replies 0 retweets 0 likes -
@roopeshchander@mjtsai@curtclifton Being too final or too static is a mistake you can safely fix, but not the other way.0 replies 3 retweets 2 likes -
@jckarter@mjtsai@curtclifton I see your point. A default final is a different issue from future Apple frameworks being un-overrideable.0 replies 0 retweets 2 likes
@roopeshchander @jckarter @curtclifton Different issue, but the way the default is/was being discussed makes it seem like
-
@mjtsai@roopeshchander@curtclifton It's easy for all of us to get defensive. Not hard to read "final default" and jump to "final only".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.
Curt Clifton
Michael Tsai
Joe Groff
JΛЯΣD
Roopesh Chander