JΛЯΣD
@jckarter @mjtsai @curtclifton @owensd Consider UITextView in iOS 7. Unusably broken for *a year* w/out subclass workarounds.
-
@roopeshchander@jckarter@curtclifton Or the thinking behind it was forgotten.
Joe Groff
Roopesh Chander
Michael Tsai
@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 - 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 "don’t worry, because the new versions…will enable" Sounded to me like they specifically don't want to enable that. -
@mjtsai I got the impression that customization / extension points will be more decoupled than inheritance, not that they won't exist.
-
-
@jckarter@roopeshchander@curtclifton Making dynamic not the default means it's effectively already taken away in many cases. -
@jckarter@mjtsai@roopeshchander@curtclifton Except that now, devs can "not worry" about polymorphism by default. Even more dangerous, IMO -
@jckarter@mjtsai@roopeshchander@curtclifton Not sure that opt-in to polymorphism creates any strong guarantee. Same problems will exist. -
@jckarter@mjtsai@roopeshchander@curtclifton Protocol-oriented approaches mitigate this greatly, but class polymorphism is important too
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.