Strings are usually the first or second data type we learn to work with as programmers. Despite appearing deceptively simple, misunderstanding and misuse of strings abound in the code we write every day. From performance problems to unicode correctness issues to complex APIs and the challenges of displaying strings on screen (and storing them on disk), we’ll look at ways to wrangle our favorite data type. Swift forced many of us to question how strings really worked for the first time, so we’ll use Swift’s String interface to understand what makes strings so slow and difficult, and explore some ways to make working with them fast and easy.
Right now, Samuel is a second-year student in The College at the University of Chicago, where he's double-majoring in Mathematics and Economics. In his spare time, he works on the core teams of CocoaPods, bundler, jazzy, and RestKit. Though he's now living on the windy shores of Lake Michigan, he's a New Yorker at heart, having done a detour through San Fransisco.
Abizer Nasir is a freelance iOS / OS X developer who has been working full-time in Swift for over a year. He has spoken on a variety of subjects related to Objective-C and Swift development at iOSCon, NSLondon, Swift London, Swift Summit and AltConf.
He organises NSCoder Night London.
By night, Catja is an experienced Filemaker developer who has been using Swift since June 2014; working mainly on a WorldBuilder-inspired game engine for macOS.
Software developer and data scientist.