Michael TsaiVerified account

@jaredsinclair @mjtsai @curtclifton @owensd Like I said, Swift's defaults won't change how ObjC works or even the policy of new frameworks.

@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.

@roopeshchander @mjtsai @curtclifton Being too final or too static is a mistake you can safely fix, but not the other way.

@jckarter @mjtsai @curtclifton I see your point. A default final is a different issue from future Apple frameworks being un-overrideable.

@jckarter @mjtsai @curtclifton Coz, it’s not like Apple can’t add final to all public API even if it’s not a language default. :)

@roopeshchander @jckarter @curtclifton the realities of developing apps are not appreciated/understood. Old system was accidentally good.