@drewcrawford How do you get system frameworks out in the open?
@_danielhall "don’t worry, because the new versions…will enable" Sounded to me like they specifically don't want to enable that.
What about large numbers of smaller bugs? With a fixed schedule, it's just not possible to take care of them all before release.
@roopeshchander Yes, but only overridable within your code, right?
@roopeshchander Pretty sure that’s less flexible, though I’m not super familiar with how protocols work under the hood.
@jckarter @roopeshchander @curtclifton Making dynamic not the default means it's effectively already taken away in many cases.
@roopeshchander Eventually they’re going to want frameworks that take advantage of Swift features that don’t work with Objective-C.
@roopeshchander @jckarter @curtclifton Or the thinking behind it was forgotten.
@roopeshchander @jckarter @curtclifton the realities of developing apps are not appreciated/understood. Old system was accidentally good.
@roopeshchander @jckarter @curtclifton Different issue, but the way the default is/was being discussed makes it seem like
@curtclifton @jckarter @roopeshchander It’s true, but I would argue that the costs of getting it initially wrong are different.
@jckarter @jaredsinclair @curtclifton @owensd It does change new frameworks unless you’re going to explicitly mark everything as dynamic.