Joe Groff
@colincornaby OTOH, components that interface with protocols have *more* flexibility for mocking and hotfixing than subclassing.
Dr. Sneed
Michael Tsai
Peter Steinberger
Friedrich Markgraf
-
-
@jckarter I don’t understand why you have to support bugs (rather than the promised contract) forever. Why not warn like with deprecation? -
@mjtsai If subclassing is part of that contract, you have a lot more compatibility surface area to ensure subclassers don't break. -
@jckarter I mean in general—undocumented/unpromised subclassing details and non-subclassing-related bugs. - View other replies
-
@mjtsai That's more important than technically-correct framework bug fixes or refactorings in a lot of cases. -
-
- View other replies
-
@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 - Show more
-
-
-
-
@drumnkyle@fzwob@mjtsai Developers writing their own ad-hoc countermeasures like@steipete did doesn't seem at all easier to me. -
@jckarter@drumnkyle@mjtsai@steipete frameworks are used more than they’re written.
-
-
-
Patrick Smith
Kyle Sherman
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.