3 ms·

Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.

by pavlov 6y ago

myko 6y ago
It wasn't until Swift came out that autocomplete for ObjC in Xcode finally started to function at a useful level. Autocomplete in Swift is still broken but I don't think it's an issue with the language itself (autocomplete is probably easier to implement in Swift given the nature of the language).
- spideymans 6y ago
  The autocomplete and syntax highlighting feature completely stops working sometimes. It’s beyond frustrating
  - jondwillis 6y ago
    Simply: CMD+, Locations Derived Data CMD+Q Xcode Delete!!! Derived Data Restart Xcode Why not Clean Build Folder CMD+B success!!
    - saagarjha 6y ago
      I have a source editor extension that has no job but to clean this clean this ;)
    - ninkendo 6y ago
      I have a shell alias for mv ~/Library/Developer/Xcode/DerivedData ~ && rm -rf ~/DerivedData & And I use it constantly. This approach is fast because it does the actual rm in the background so I can relaunch Xcode right away.
akkawwakka 6y ago
Manipulating the source code leads to invoking the Swift compiler to generate the information required to drive the rich editing experience. I have found SourceKit’s performance in complex projects, especially those where there are a lot of third-party libraries or frameworks you’re linking against, to be pretty disappointing. Especially when you’re working with many ObjC dependencies. Like many of Apple’s developer tools, if you stick to the happy path, performance is great. Practically that means compiling your source into a single Swift module and keeping the number of modules low. If you are a “basic” iOS or macOS app with just a couple of 3p libraries things work great. Real world projects are drastically more messy...

3 ms·

Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.

by pavlov 6y ago

Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.

myko 6y ago
It wasn't until Swift came out that autocomplete for ObjC in Xcode finally started to function at a useful level. Autocomplete in Swift is still broken but I don't think it's an issue with the language itself (autocomplete is probably easier to implement in Swift given the nature of the language).
- spideymans 6y ago
  The autocomplete and syntax highlighting feature completely stops working sometimes. It’s beyond frustrating
  - jondwillis 6y ago
    Simply: CMD+, Locations Derived Data CMD+Q Xcode Delete!!! Derived Data Restart Xcode Why not Clean Build Folder CMD+B success!!
    - saagarjha 6y ago
      I have a source editor extension that has no job but to clean this clean this ;)
    - ninkendo 6y ago
      I have a shell alias for mv ~/Library/Developer/Xcode/DerivedData ~ && rm -rf ~/DerivedData & And I use it constantly. This approach is fast because it does the actual rm in the background so I can relaunch Xcode right away.
akkawwakka 6y ago
Manipulating the source code leads to invoking the Swift compiler to generate the information required to drive the rich editing experience. I have found SourceKit’s performance in complex projects, especially those where there are a lot of third-party libraries or frameworks you’re linking against, to be pretty disappointing. Especially when you’re working with many ObjC dependencies. Like many of Apple’s developer tools, if you stick to the happy path, performance is great. Practically that means compiling your source into a single Swift module and keeping the number of modules low. If you are a “basic” iOS or macOS app with just a couple of 3p libraries things work great. Real world projects are drastically more messy...