Daniel Jalkut
"Not all classes make sense to subclass." It's absurd to imagine you can predict all valid subclassing patterns. http://mjtsai.com/blog/2016/07/17/swift-classes-to-be-non-publicly-subclassable-by-default/ …
Apple, nor any framework provider, can provide functionality sufficient to cover the breadth of innovation. Clever hacks built the industry.
-
-
@danielpunkass lol at subclassing being the only/best medium for said innovation -
@tomburns Not the only or best, but sometimes the only or best. -
@danielpunkass it's never the only/best if it exposes bugs that the developers didn't anticipate. authorial intent is valuable here -
@danielpunkass "this almost does what I want" != "I should subclass this and make it do the thing that I want" -
@tomburns Well your attitude is totally different from the one that has gotten me through almost all of my life software pursuits :) -
@danielpunkass I sincerely doubt that one of us has to be wrong for the other to be right, but try subclassing UITabBarController sometime
- View other replies
- Show more
-
-
-
@danielpunkass@mjtsai Same issue with Apple’s removal of Xcode plug-ins – https://github.com/alcatraz/Alcatraz/issues/475 … – it prevents unanticipated innovation - View other replies
-
@fzwob@danielpunkass@mjtsai truly. Real innovation *can’t be* anticipated
-
-
@danielpunkass you can't always predict which classes should or shouldn't be subclassed.
tomb urns
Friedrich Markgraf
Nate Heagy
iGeneralist
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.