Patrick Smith

@jckarter @mjtsai Hopefully this will make it much easier for Apple to fix those framework bugs that are the actual source of pain

@concreteniche @mjtsai I think it'll lead to a more robust third-party framework ecosystem, whatever Apple ends up doing.

@jckarter If this is about 3rd party frameworks, the vendor can always put a breaking change in a new version. If necessary to reverse a

@jckarter bad decision. Whereas the framework client, without the ability to override, has no recourse.

@mjtsai @jckarter Hopefully though those frameworks are using value types, where they don’t get the ability to subclass/override anyway

@mjtsai @jckarter If framework authors used classes because clients are more comfortable and able to monkey patch, I think that’d be sad

@mjtsai @jckarter AFAIK protocols would allow the most of same sorts of custom extending desired, and are explicitly designed to be so

@concreteniche @jckarter Probably not as flexible. And changing classes to protocols doesn’t make the design/thinking issues go away.