4 ms·

It is hard and costly to rewrite an app, even for Apple. In this case it means learning new skills (or hiring new devs). This is huge and will probably take yea

by rloc 11y ago

It is hard and costly to rewrite an app, even for Apple. In this case it means learning new skills (or hiring new devs). This is huge and will probably take years to be adopted. They could also force it at some point by releasing new APIs with only Swift support. It's worrying for Swift. If it really adds value compared to Objective-c then why is Apple so slow on jumping on the bandwagon? They need to show the way. Other companies usually talk with their fans through dev blog posts but Apple secrecy tradition and very tightly controlled communication does not help.

Sephiroth87 11y ago
https://developer.apple.com/swift/blog/ https://developer.apple.com/swift/blog/, or any Swift developer twitter account, really... Everything surrounding Swift has been the most open Apple has been in a very long time Edit: https://swift.org/blog https://swift.org/blog (the current blog)
- rloc 11y ago
  Yes thanks. This looks more like a documentation than a blog. I meant there is nothing more personal like here is how we migrated our app x to Swift (real world examples) with: - What was challenging ? - Lessons learned - Performance measured before/after - In general what was the gain ? Why should I bother except for the hype ?
  - cellularmitosis 11y ago
    I think the gain is mostly that Swift allows you write code which more resistant to bugs than its ObjC counterpart would be. In Yaron Minsky's "Effective ML" talk, he mentions the idea of "Make illegal states unrepresentable": https://vimeo.com/14313378 https://vimeo.com/14313378 The combination of enums and non-optional variables allows you to get much closer to this ideal than you could with ObjC. A great place to start would be the Functional Swift talks from 2014 and 2015: http://2014.funswiftconf.com/ http://2014.funswiftconf.com/ http://2015.funswiftconf.com/ http://2015.funswiftconf.com/ If you want to challenge yourself, try reading through the RxSwift codebase: https://github.com/ReactiveX/RxSwift https://github.com/ReactiveX/RxSwift

by rloc 11y ago

Sephiroth87 11y ago

https://developer.apple.com/swift/blog/ https://developer.apple.com/swift/blog/, or any Swift developer twitter account, really... Everything surrounding Swift has been the most open Apple has been in a very long time Edit: https://swift.org/blog https://swift.org/blog (the current blog)

rloc 11y ago
Yes thanks. This looks more like a documentation than a blog. I meant there is nothing more personal like here is how we migrated our app x to Swift (real world examples) with: - What was challenging ? - Lessons learned - Performance measured before/after - In general what was the gain ? Why should I bother except for the hype ?
- cellularmitosis 11y ago
  I think the gain is mostly that Swift allows you write code which more resistant to bugs than its ObjC counterpart would be. In Yaron Minsky's "Effective ML" talk, he mentions the idea of "Make illegal states unrepresentable": https://vimeo.com/14313378 https://vimeo.com/14313378 The combination of enums and non-optional variables allows you to get much closer to this ideal than you could with ObjC. A great place to start would be the Functional Swift talks from 2014 and 2015: http://2014.funswiftconf.com/ http://2014.funswiftconf.com/ http://2015.funswiftconf.com/ http://2015.funswiftconf.com/ If you want to challenge yourself, try reading through the RxSwift codebase: https://github.com/ReactiveX/RxSwift https://github.com/ReactiveX/RxSwift