The below is an off-site archive of all tweets posted by @mjtsai ever

December 22nd, 2015

@drewcrawford How do you get system frameworks out in the open?

via Tweetbot for Mac in reply to drewcrawford

@_danielhall "don’t worry, because the new versions…will enable" Sounded to me like they specifically don't want to enable that.

via Tweetbot for Mac in reply to _danielhall

What about large numbers of smaller bugs? With a fixed schedule, it's just not possible to take care of them all before release.

via Tweetbot for Mac

@roopeshchander Yes, but only overridable within your code, right?

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander Pretty sure that’s less flexible, though I’m not super familiar with how protocols work under the hood.

via Tweetbot for Mac in reply to roopeshchander

@jckarter @roopeshchander @curtclifton Making dynamic not the default means it's effectively already taken away in many cases.

via Tweetbot for Mac in reply to jckarter

@roopeshchander Eventually they’re going to want frameworks that take advantage of Swift features that don’t work with Objective-C.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander @jckarter @curtclifton the realities of developing apps are not appreciated/understood. Old system was accidentally good.

via Tweetbot for Mac in reply to roopeshchander

@roopeshchander @jckarter @curtclifton Different issue, but the way the default is/was being discussed makes it seem like

via Tweetbot for Mac in reply to roopeshchander

@curtclifton @jckarter @roopeshchander It’s true, but I would argue that the costs of getting it initially wrong are different.

via Tweetbot for Mac in reply to curtclifton

@jckarter @jaredsinclair @curtclifton @owensd It does change new frameworks unless you’re going to explicitly mark everything as dynamic.

via Tweetbot for Mac in reply to jckarter