Is it time for Swift?

Transcript

1. About Me @sandofsky
2. that makes code faster and safer an exciting new runtime from Apple with strong developer momentum Today We’re Talking About
3. Java https://www.youtube.com/watch?v=E5dWDg6f9eo
5. Is it time for Swift?
6. Swift is taking over! http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html
7. https://medium.com/@ryanolsonk/are-the-top-apps-using-swift-42e880e7727f 89% 11% Swift in the Top 100 Apps
9. Don’t listen to the Internet.
10. Senior engineers make objective decisions balancing risk to reward.
11. It’s cool to say, “No, not yet.”
12. What is the best thing that could happen?
13. “We’ll be so much more productive!”
14. http://page.mi.fu-berlin.de/prechelt/Biblio/jccpprt_computer2000.pdf
16. Syntax doesn’t move the needle. It’s all about tradeoffs.
17. “I heard _____ rewrote their app in _____!”
18. "Most of the code has been rewritten over the past three years, but some core parts of it were still holding strong," explains Lambert. "But we would have built a different app if we’d started over." http://www.fastcompany.com/3050266/tech-forecast/lyft-goes-swift-how-and-why-it- rewrote-its-app-from-scratch-in-apples-new-lang
19. So what is there to be excited about?
20. Let’s Play Spot the Bug
21. hashOut.data = hashes + SSL_MD5_DIGEST_LEN; hashOut.length = SSL_SHA1_DIGEST_LEN; if ((err = SSLFreeBuffer(&hashCtx)) != 0) goto fail; if ((err = ReadyHash(&SSLHashSHA1, &hashCtx)) != 0) goto fail; if ((err = SSLHashSHA1.update(&hashCtx, &clientRandom)) != 0) goto fail; if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0) goto fail; if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) goto fail; goto fail; if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0) goto fail;
22. @implementation NSString (Helper) - (BOOL)containsString:(NSString *) string { NSRange range = [self rangeOfString:string options:NSCaseInsensitiveSearch]; return range.location != NSNotFound; } @end
23. #available safer switch Optionals!
24. We can write clearer, safer, faster code.
25. What is the worst thing that could happen?
26. Bundling Swift increases size 1
27. Objc Swift Thin 72k 3.1mb Full 92k 4.6mb Hello World
28. http://blog.jana.com/2015/01/26/the-data-trap/
29. New paradigms Limited support 2
30. class Post
31. struct Post
32. struct Post:NSCoding error: non-class type 'Post' cannot conform to class protocol 'NSCoding'
33. New runtime New bugs 3
34. https://bugs.swift.org/browse/SR-192
35. Swift moves fast. Really fast. 4
38. Churn makes for painful dependencies. https://www.dropboxforum.com/hc/en-us/community/posts/204715229- To-use-API-v2-in-iOS-platform-we-need-an-objective-C-version
39. Apps enter “maintenance mode.”
40. Migration has coordination costs.
41. So what’s my hot take?
42. Low coordination costs? You can burn two weeks? You can slip a few days? Go for it.
43. Already great at Objective-C? Got dependencies? Just busy shipping? Wait for Swift 3.0
44. Thanks! @sandofsky