Dictionary and Set Improvements in Swift 4.0
1–10 of 71 posts
Re: Dictionary and Set Improvements in Swift 4.0
#2I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app is worlds ahead of Swift right now.
Re: Dictionary and Set Improvements in Swift 4.0
#3I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app is worlds ahead of Swift right now.
Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.
Re: Dictionary and Set Improvements in Swift 4.0
#4I really wish Swift could find a way to be useful on platforms other than Apple. I'd be willing to commit more to it if I could write truly portable code in it. It's got a good start on Linux, but Windows and Android would be cool too. Though Kotlin won out over Swift for Android (very similar languages but I like Swift a bit better there).
Re: Dictionary and Set Improvements in Swift 4.0
#5The language definitely feels like it has matured as the change from 3.0 to 4.0 was pretty much painless. The big issue with programming in Swift is no longer swift itself but the libraries around it. A lot of the API's you use in day to day Cocoa programming are based on Objective-C and often stringly typed and not very compile safe.
For example NSNotificationCenter, setting attributed strings, core data or fetching resources. Also the whole MVC ViewController lifecycle is full of optionals. A lot of people abandon using Storyboards just to have ViewControllers that have everything set up compile safe, don't use prepareForSegue to pass in variables and so on. But that means doing everything in code, which is inefficient for complicated one-off layouts.
Re: Dictionary and Set Improvements in Swift 4.0
#6I really wish Apple would focus more on getting Xcode up to par. It's in a truly horrid state, both performance and feature-wise. Developing an Objective-C app is worlds ahead of Swift right now.
Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.
So ... any good?
Re: Dictionary and Set Improvements in Swift 4.0
#7Earlier quoted context omitted.
Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.
So ... any good?
I haven't used it much yet myself, but I did notice that one annoyance I had was fixed, regarding zooming the font onscreen.
Re: Dictionary and Set Improvements in Swift 4.0
#8I really wish Swift could find a way to be useful on platforms other than Apple. I'd be willing to commit more to it if I could write truly portable code in it. It's got a good start on Linux, but Windows and Android would be cool too. Though Kotlin won out over Swift for Android (very similar languages but I like Swift a bit better there).
let's say android or windows adopted swift. I don't think that would eliminate the biggest learning curve of dealing with the frameworks. in my experience, learning UIKit stuff was way trickier than swift. I imagine the same experience developing for other OS'.
Re: Dictionary and Set Improvements in Swift 4.0
#9I really wish Swift could find a way to be useful on platforms other than Apple. I'd be willing to commit more to it if I could write truly portable code in it. It's got a good start on Linux, but Windows and Android would be cool too. Though Kotlin won out over Swift for Android (very similar languages but I like Swift a bit better there).
Any language that wishes first class support on Android needs to support a painless way to interoperate with Java APIs on their compiler toolchain.
Otherwise developers are going to have lots of pain manually writting JNI wrappers to 90% of Android APIs.
Likewise on Windows with COM support.
Re: Dictionary and Set Improvements in Swift 4.0
#10Earlier quoted context omitted.
Are you aware that Xcode 9 just shipped last week and is a major rewrite of much of the IDE? It's one of the largest updates in Xcode's history.
So ... any good?
The only that truly annoyed me was that CMD+click doesn't work immediately anymore but conjures some kind of intermediary menu. Haven't figured out if there's a new keystroke for it, but I'm still doing too much work in Xcode 8.
To me it was nothing but progress compared to 8 apart from that. Everything faster and better.