Joe Groff
@mjtsai @curtclifton @owensd Replacing functionality for yourself is more modular than trying to dynamically change it in the framework.
-
@roopeshchander@mjtsai@curtclifton Being too final or too static is a mistake you can safely fix, but not the other way.
Curt Clifton
Michael Tsai
JΛЯΣD
Roopesh Chander
@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. - View other replies
-
@jckarter@mjtsai@roopeshchander@curtclifton Polymorphism is the basis of good OOP; final by default == program to concrete implementation - View other replies
-
@_danielhall@mjtsai@roopeshchander@curtclifton Polymorphism doesn't have to mean implementation subclassing. - View other replies
-
@jckarter@mjtsai@roopeshchander@curtclifton So, after devil's advocating, I now agree 100% with the proposal: http://www.danielhall.io/swifts-final-countdown … - View other replies
-
@_danielhall@jckarter@mjtsai@curtclifton I don’t think we’ll get a protocol-oriented UIKit for a few decades (because Obj-C). - Show more
-
-
-
@roopeshchander@jckarter@curtclifton Different issue, but the way the default is/was being discussed makes it seem like - Show more
-
Daniel Hall
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.