5 ms·

I'm surprised the Swift is not higher on the Stackoverflow side, seeing how utterly confusing this thing is with Swift version 1/2/3/4... I'm learning Swift at

by keyle 8y ago

I'm surprised the Swift is not higher on the Stackoverflow side, seeing how utterly confusing this thing is with Swift version 1/2/3/4... I'm learning Swift at the moment and I'm running out of eyebrows, due to the sheer quantity of unforced facepalms I give myself.

saagarjha 8y ago
Why, what's wrong with it? You should be writing Swift 4.2 unless you have a specific reason to deal with earlier versions of Swift…
- melling 8y ago
  Swift is a pretty nice language. I’ve got about 30 iOS examples on Github: https://github.com/melling/ios_topics https://github.com/melling/ios_topics
- iainmerrick 8y ago
  The official docs are good but not comprehensive, and hard to navigate. Once you start googling around you get a random mix of third-party docs for various versions. It’s not at all obvious what’s outdated and what isn’t. As an example, I had to write a little code to connect some Swift and Obj-C code the other day. (I don’t use either one regularly.) It was very hard to find good up-to-date docs on how Swift/Obj-C bridging works.
  - mpweiher 8y ago
    Over the last two years whenever I downloaded sample code from Apple for newish macOS/iOS features (Touch Bar, for example) it no longer compiled.
    - saagarjha 8y ago
      This is more an issue with the Swift overlay for AppKit than Swift itself.
      - mpweiher 8y ago
        While my experience doesn’t match up with that, if it were true the fact that these “overlays” are both required and fragile is most definitely an issue with the design of Swift.
  - theshrike79 8y ago
    This is exactly my experience. I tried to create a simple tool to retrieve a JSON reply from an API and display the results. Piece of cake, right? Took me a day of debugging and hitting my head on several objects before I figured out that none of the half dozen tutorials I found were made for Swift 4.x.
- chetanbhasin 8y ago
  I think the most of the problems comes from the fact that some of us are trying to learn Swift now after it has gained some popularity. Searching Stackoverflow keeps coming up with answers that are now obsolete and while it is usually not very hard to port old StackOverflow answer code to new Swift, it's still annoying to keep running into that problem again and again.

by keyle 8y ago

saagarjha 8y ago

Why, what's wrong with it? You should be writing Swift 4.2 unless you have a specific reason to deal with earlier versions of Swift…

melling 8y ago
Swift is a pretty nice language. I’ve got about 30 iOS examples on Github: https://github.com/melling/ios_topics https://github.com/melling/ios_topics
iainmerrick 8y ago
The official docs are good but not comprehensive, and hard to navigate. Once you start googling around you get a random mix of third-party docs for various versions. It’s not at all obvious what’s outdated and what isn’t. As an example, I had to write a little code to connect some Swift and Obj-C code the other day. (I don’t use either one regularly.) It was very hard to find good up-to-date docs on how Swift/Obj-C bridging works.
- mpweiher 8y ago
  Over the last two years whenever I downloaded sample code from Apple for newish macOS/iOS features (Touch Bar, for example) it no longer compiled.
  - saagarjha 8y ago
    This is more an issue with the Swift overlay for AppKit than Swift itself.
    - mpweiher 8y ago
      While my experience doesn’t match up with that, if it were true the fact that these “overlays” are both required and fragile is most definitely an issue with the design of Swift.
- theshrike79 8y ago
  This is exactly my experience. I tried to create a simple tool to retrieve a JSON reply from an API and display the results. Piece of cake, right? Took me a day of debugging and hitting my head on several objects before I figured out that none of the half dozen tutorials I found were made for Swift 4.x.
chetanbhasin 8y ago
I think the most of the problems comes from the fact that some of us are trying to learn Swift now after it has gained some popularity. Searching Stackoverflow keeps coming up with answers that are now obsolete and while it is usually not very hard to port old StackOverflow answer code to new Swift, it's still annoying to keep running into that problem again and again.