11–20 of 115 posts
Man I wish Xcode was a decent IDE
I remember around when Swift came out, Xcode was so bad that I couldn't even use it because typing was ~1 character/second and it would crash every few minutes. It's definitely recovered from that and I can actually type without lag now.
Man I wish Xcode was a decent IDE
Man I wish Xcode was a decent IDE
I used Xcode recently and it's gotten a lot better. It's still not as good as IntelliJ or AppCode but it's usable. I remember around when Swift came out, Xcode was so bad that I couldn't even use it because typing was ~1 character/second and it would crash every few minutes. It's definitely recovered from that and I can actually type without lag now.
Earlier quoted context omitted.
I used Xcode recently and it's gotten a lot better. It's still not as good as IntelliJ or AppCode but it's usable. I remember around when Swift came out, Xcode was so bad that I couldn't even use it because typing was ~1 character/second and it would crash every few minutes. It's definitely recovered from that and I can actually type without lag now.
Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.
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).
Man I wish Xcode was a decent IDE
You're hardly the only one, 3.3/5 star rating on the Mac App Store and the #1 downloaded developer tool. Can't live with it, can't live without it.
This guide would’ve saved me countless hours had it been available in the summer.
Earlier quoted context omitted.
Xcode had no such problems with Objective-C though... Maybe Swift's design deserves some blame here for years of subpar developer experience.
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).
Why learn SwiftUI? If you want a declarative UI framework wouldn’t you be better served for your time to learn something like React Native or Flutter? I’m not trying to knock SwiftUI, I am genuinely curious what the value proposition is for anyone considering it...
There’s something to say about a first-class library, meaning one that is being used exactly as designed. I mean, why do people use Javascript? Because it’s the native language of the browser.