Michael TsaiVerified account

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

@roopeshchander @jckarter @curtclifton Or the thinking behind it was forgotten.

@mjtsai @roopeshchander @curtclifton We won't take subclassing or dynamic away. Stronger guarantees allow for new design choices.

@jckarter @mjtsai @roopeshchander @curtclifton Polymorphism is the basis of good OOP; final by default == program to concrete implementation