r/iOSProgramming • • Apr 29 '25

Discussion XCode rant, sorry

XCode is PATHETIC. Have they never used IntelliJ or VSCode?

It's like when iPhone is stuck without features that have been in Android since time immemorial and boasts about it in a new reLeAsE except WHEN IS THE XCODE RELEASE

Of other things, why is it SO hard to show callers of a function?
Why does autocomplete sort by most irrelevant first?
Why aren't errors shown immediately, why do I need to CtrlB to update them?
And this is unforgivable - WHY DO YOU WANT ME TO PRESS ENTER WHEN I SEARCH? Jeez it's 2025, add a debounce and dynamically show me the results for fks sake 😭

260 Upvotes

172 comments sorted by

View all comments

112

u/chriswaco Apr 29 '25

I used to rant about Xcode until I had to use Android Studio.

19

u/TheAngryApologist Apr 29 '25

WTF? Android Studio (IntelliJ) is crazy better.

→ More replies (1)

26

u/AwkwardShake Apr 29 '25 edited Apr 29 '25

Man, you've probably never used Android studio professionally. That thing is fucking insane. Xcode is absolutely dogshit. I used both these IDE's, for equal amount of time (3-4 years each), and I can tell you Xcode absolutely shits its pants in front of android studio.

Like what the fuck is "compiler is unable to type check this expression???????". Dont give me bs about "breaking down view". I can literally write a much much bigger compose view and android studio will never break.

Then there's random recommendations that xcode gives you. Want .frame(maxWidth)? naaah, here's kCGImagePropertyIPTCExtMaxAvailWidth because it has "maxWidth" in it somewhere as well. Like what bullshit?

What about the git gui?? You cant tell me that the git gui on xcode is usable. I personally use Android studio's git gui (yes even on xcode projects by opening the project) because its just miles miles better than xcode. And then there's bunch of issues like when you switch or play around with git?? Like Tim bro, just get one thing right atleast.

There's bunch of other issues i can point out, but man please use android studio properly next time as a professional before talking shit about that absolutely beautiful tool.

I start loving my life once again after i go back to coding using android studio after working with dogshit xcode.

9

u/CourtAffectionate224 Apr 29 '25

compiler is unable to type check this expression

This is not Xcode’s fault technically but rather an unfortunate consequence of Swift’s language design

→ More replies (4)

44

u/dabluck Apr 29 '25

Genuinely don't get these comments. There's almost nothing Xcode is better at. Android studio works and is a modern IDE. XCode can barely even rename a variable. 

5

u/iOSCaleb Objective-C / Swift Apr 29 '25

XCode can barely even rename a variable.

I literally renamed a bunch of functions and variables in Xcode 16 30 minutes ago and had zero problems. It shows you every change that it’s about to make and you can disable any of them if you want. I’m not sure how it could be better.

36

u/bunz4u Apr 29 '25

That's when it works. When it works it's great. But many times, at least for me, the rename attempt fails before it even gets to the editor portion.

6

u/Holatej Apr 29 '25

I once had a rename attempt do only half the renames it said it would. Crazy work.

→ More replies (1)

9

u/Inevitable-Hat-1576 Apr 29 '25

As others have said. It’s definitely spotty - often it works, but sometimes it errors and it’s baffling

4

u/Peroovian Apr 29 '25

I work on a big iOS app at my job and it struggles at basically everything, unless I'm working on a swift package or a side project; on those it works perfectly.

4

u/dabluck Apr 29 '25

Well it could be better if they remove that stupid animation where it folds up and then takes forever to load each instance into the list. It's also very bad at finding objective C calls if you're renaming a swift variable. Try refactoring in intellij, you will see how it could be better

4

u/xezrunner Apr 29 '25

Despite Apple being great with animations visually, they very often block the UI while animating and it often takes a bit until you regain control.

This is most annoying on iOS and its sliding confirmation alerts.

2

u/soviyet Apr 30 '25

Good for you, I'm genuinely happy for you.

Right now, XCode 16.3 will not let me refactor anything and flat out refuses to let me see compilation errors on the issues navigator for more than a half a second before they disappear for... a reason, and I have to go to the report navigator to see why the project didn't build in that teeny tiny font.

And this is for a project I just started a week ago with no external dependencies yet. No good reason whatsoever for XCode to be choking on it.

2

u/Passey Apr 30 '25

Fix for the issues disappearing is to switch off “Show Live Issues” in Xcode Settings. While this does prevent issues from popping up automatically, they do come every build and stay instead of disappearing. I used Xcode like this for a year without live issues. Then I switched it back on, and somehow the issue had resolved. Go figure.

→ More replies (1)

1

u/TumbleweedOther1039 Apr 29 '25

Have you tried renaming in Android studio? It works way better. It’ll rename the file too and parameter names too

→ More replies (2)

1

u/save_jeff2 Apr 30 '25

It frequently doesn't work and it's unacceptable

→ More replies (4)

8

u/drabred Apr 29 '25

You have to be baiting here...

38

u/[deleted] Apr 29 '25

[removed] — view removed comment

→ More replies (6)

39

u/[deleted] Apr 29 '25

[removed] — view removed comment

15

u/turboravenwolflord Apr 29 '25

How can you say that? Monster.

2

u/aspenajax264 Apr 30 '25

Android Studio was created off the backbone of JetBrains IDEs which are all fantastic. It is too bad that a 2 Trillion dollar company(AAPL) cannot produce a better IDE.

→ More replies (1)

10

u/nhaarman Apr 29 '25

If you're not familiar with a tool of course it doesn't work for you

→ More replies (1)

2

u/john0201 Apr 29 '25

Android Studio is better, but “yeah but other stuff sucks too” being one of the top comments- Xcode sucks.

→ More replies (1)
→ More replies (3)