@stroughtonsmith Just curious about your reasoning, BTW. I totally respect your choosing whichever language works best for you.
@stroughtonsmith @wilshipley What does it mean for the transition to be complete? ABI stability? Finder rewritten in Swift? Swift-only APIs?
@parkerwightman Agreed. I only wrote it that way because if you aren’t already using it, now is the earliest you can start.
@rustyshelf @stroughtonsmith @wilshipley Yeah, Swift 2 to 3 was not that bad for me, either, though I didn’t have as much code then.
@stroughtonsmith @wilshipley I think, for most people, writing serious amounts of code with Swift 1 would have been… twitter.com/i/web/status/9…
@mcelhearn Cool. Looking forward to reading once you’ve researched more.
AIM Will Shut Down After 20 Years: mjtsai.com/blog/2017/10/0… #mjtsaiblog
Cocoa Class Clusters: mjtsai.com/blog/2017/10/0… #mjtsaiblog
Apple Granted Uber a Background Screen Recording Entitlement: mjtsai.com/blog/2017/10/0… #mjtsaiblog
Why Many Developers Still Prefer Objective-C to Swift: mjtsai.com/blog/2017/10/0… #mjtsaiblog
Type-Safe User Defaults in Swift: mjtsai.com/blog/2017/10/0… #mjtsaiblog
When JSONDecoder Meets the Real World: mjtsai.com/blog/2017/10/0… #mjtsaiblog
@mcelhearn What happened to the HEIF post?
@nickheer Broken Markdown on pxlnv.com/linklog/high-s…