3 ms·

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 vers

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.