3 ms·
My wish for where Swift goes next: polishing rough edges. 1. Get experts to improve the tutorials and classes. -- This year I especially want to thank Ray Wen
by jph 11y ago
My wish for where Swift goes next: polishing rough edges.
1. Get experts to improve the tutorials and classes.
-- This year I especially want to thank Ray Wenderlich (http://www.raywenderlich.com http://www.raywenderlich.com) for his clear tutorials and Rob Rix (https://github.com/robrix https://github.com/robrix) for his focused classes.
2. Do spring cleaning on incompatibilities in Swift vs. Obj-C vs. Foundation, such as incompatible types that require casting, or bridging, or different semantics.
-- For most iOS code that I personally write, I value readable Swift syntax even more than fast toll-free bridging to Obj-C and CF. For examples, look at ints and strings.
3. Create some kind of dependency manager, to make it easier to have a Swift code that uses other Swift codebase.
-- The current approaches are Xcode project embedding, Carthage, and Cocoapods; this past year all of them have had struggles.
- marvel_boy 11y agoMy wish: open source Swift on Monday.
- k-mcgrady 11y ago+1 point 2. Most of my Swift code is within Objective-C projects and most of my time wasted is dealing with incompatibilities between Objc types and Swift types.
- melling 11y agoI catalogued over 1000 blog entries in the first year and I'm sure I missed some: http://www.h4labs.com/dev/ios/swift.html http://www.h4labs.com/dev/ios/swift.html I expect to add a couple thousand in the second year. I'm sure the quality varies but a lot of great stuff has already been written. Also, consider that there were 36,000 questions on StackOverflow for Swift. That's almost as many as Scala, for example. I also hope Swift keeps improving but for the first year, I'd say it was much better than I expected.
- avinassh 11y ago> Rob Rix (https://github.com/robrix https://github.com/robrix) for his focused classes. Link?