mikeash
Adam R. Maxwell
@mikeash That put me over the edge last night, as sole commenter on that post. Still upset to find last week they broke inline refcounts.
This "claimed bugs" language makes me uncomfortable. http://mjtsai.com/blog/2016/07/17/swift-classes-to-be-non-publicly-subclassable-by-default/ …
-
-
-
@maxwellarm What did they break exactly? -
@mikeash Seems NSNotificationCenter has an alternate code path for zeroing weak vs. retain/release objects. Latter seems to overrelease. - View other replies
-
@maxwellarm I'm reminded of NSPathControlItem, which for a while had its object teardown code in release instead of dealloc, causing havoc. -
@mikeash Ha! I've been worried that guys designing languages/frameworks don't maintain GUI apps using them, or they'd know there are bugs. -
@maxwellarm Yeah, that one was a clear case where whoever wrote it never actually tried it aside from possibly a quick smoke test.
-
-
@mikeash Strawman argument = easy to knock down, using “because not swizzling” = weak/counterproductive argument. -
@mikeash I’m bothered by it too. :( -
@mikeash putting limits on subclasses to force authors to think sounds like strict constructionism to force Congress to read their bills. -
@mikeash Hybris, shortsightedness, lack of empathy. And a very dangerous path to tread for us all, ultimately Apple too.
Frederic Barthelemy
Jay Tamboli
Friedrich Markgraf
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.