5 ms·
Having worked with it since it was still known as Project Builder I think it’s fine too. The only part that’s really bad is the XIB/storyboard editor, which was
by jwells89 2y ago
Having worked with it since it was still known as Project Builder I think it’s fine too. The only part that’s really bad is the XIB/storyboard editor, which was actually pretty good when it was its own independent program (Interface Builder) but has been awful ever since it got merged into Xcode. That’s easy enough to avoid though, with UIKit being pleasant and practical to write in pure code, as I’ve been doing for the past several years.
Beyond that, there are some things that can make SourceKit (provider of syntax coloration, autocomplete, etc) grumpy, but those are almost all code smells that should be avoided anyway like pyramids of doom built of closures or way-too-long optional chains.
- danpalmer 2y agoThe GUI building was always pretty bad, true. I managed to skip most of that and either did UIKit mostly via code, or more recently SwiftUI (which is mostly pretty good) and server-side stuff. I think SourceKit was the source of many crashes a few years ago, more recently it seems to have transitioned to fewer crashes and more cases where it just gets "grumpy" as you said, and in the last few years I've even found most of those cases have ceased.
- jwells89 2y agoYeah things have been pretty smooth in recent years, especially after being able to drop CocoaPods in favor of Swift Package Manager. On average I find myself “fighting” the IntelliJ-based Android Studio more frequently than I do Xcode.