Xcode

Developers frequently encounter inexplicable build failures requiring manual nuking of `.build`, SwiftPM caches, or Xcode derived data. Packages mysteriously disappear in Xcode and builds trigger more than expected, affecting both macOS and Linux.

Accidental misconfigurations in build settings (e.g., duplicate HEADER_SEARCH_PATHS) don't prevent compilation but cause SourceKit to crash on every text edit. Debugging requires manual inspection of SOURCEKIT_LOGGING output.

SwiftUI's preview system and dependency-heavy build graph often double or triple compile times compared to other frameworks. Large Swift packages sometimes require clean builds, significantly slowing iteration and delaying feature releases.

The Preview feature in SwiftUI requires building the entire project and fails with compatibility errors when UIKit is present in the codebase. This prevents developers from using Previews to speed up development in mixed UIKit/SwiftUI projects.

Due to frequent Swift updates, it is difficult to find appropriate tooling for specific tasks. Xcode lacks proper support for Swift with widespread issues in syntax highlighting, autocomplete, refactoring tools, and compilation.

Xcode's vim mode implementation is incomplete, missing essential features like the '.' command. The community-provided vim extension supports vim perfectly including macros, but Xcode lacks a safe plugin API for the community to provide these features.