October 6th, 2017

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

7:23 PM, Oct 6th, 2017 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?

7:22 PM, Oct 6th, 2017 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.

7:15 PM, Oct 6th, 2017 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.

7:12 PM, Oct 6th, 2017 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

7:07 PM, Oct 6th, 2017 via Tweetbot for Mac

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

4:42 PM, Oct 6th, 2017 via Tweetbot for Mac in reply to mcelhearn

@mcelhearn What happened to the HEIF post?

4:32 PM, Oct 6th, 2017 via Tweetbot for Mac

@nickheer Broken Markdown on https://t.co/milhGOSVYd

2:50 PM, Oct 6th, 2017 via Tweetbot for Mac