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

October 6th, 2017

@stroughtonsmith Just curious about your reasoning, BTW. I totally respect your choosing whichever language works best for you.

via Tweetbot for Mac in reply to stroughtonsmith

@stroughtonsmith @wilshipley What does it mean for the transition to be complete? ABI stability? Finder rewritten in Swift? Swift-only APIs?

via Twitter Web Client in reply to stroughtonsmith

@parkerwightman Agreed. I only wrote it that way because if you aren’t already using it, now is the earliest you can start.

via Twitter Web Client in reply to parkerwightman

@rustyshelf @stroughtonsmith @wilshipley Yeah, Swift 2 to 3 was not that bad for me, either, though I didn’t have as much code then.

via Tweetbot for Mac in reply to rustyshelf

@stroughtonsmith @wilshipley I think, for most people, writing serious amounts of code with Swift 1 would have been… https://t.co/Jy2SRf9QNb

via Tweetbot for Mac

@mcelhearn Cool. Looking forward to reading once you’ve researched more.

via Tweetbot for Mac in reply to mcelhearn

AIM Will Shut Down After 20 Years: https://t.co/2WTLV5Lypp #mjtsaiblog

via IFTTT

Apple Granted Uber a Background Screen Recording Entitlement: https://t.co/z8UjPiyata #mjtsaiblog

via IFTTT

Why Many Developers Still Prefer Objective-C to Swift: https://t.co/tyUpy0cCg5 #mjtsaiblog

via IFTTT

Type-Safe User Defaults in Swift: https://t.co/VRSe8PxUBv #mjtsaiblog

via IFTTT

When JSONDecoder Meets the Real World: https://t.co/0JmlD68Ows #mjtsaiblog

via IFTTT

@mcelhearn What happened to the HEIF post?

via Tweetbot for Mac